# AS A DESIGNER
I've been interested in people for much longer than I've been interested in design. Why people behave the way they do, what influences their decisions, and why we sometimes act against our own intentions have fascinated me since I was a kid.
Product design became a practical outlet for that curiosity. Today, I'm most interested in where human behavior, business, technology and data meet.
Look beyond the obvious answer
Behind every click, purchase, abandoned flow and metric is still a person. That's why behavioral science and psychology influence how I think about products.
I also try not to confuse an observation with its explanation.
A million visits doesn't automatically mean success. Nobody using a feature doesn't automatically make it useless. People saying they want something doesn't mean they'll actually use it.
Data gives us signals. The interesting part is figuring out what could explain them — and how confident we should be in that explanation.
Sometimes I build because I don't know
When something is cheap to build and easy to reverse, a working product can sometimes answer a question better than asking people to imagine using it.
I don't build because I assume an idea is good. Sometimes I build precisely because I don't know if it is.
That doesn't make usage data the truth either. Low adoption could mean low value, but it could also be discoverability, UX, implementation, context or simply insufficient evidence.
Different questions need different methods. Interviews, research, usability testing, analytics and working experiments are tools for learning — not rituals I need to perform in a particular order.
Design includes the business
A product has to create value for the people using it and for the business sustaining it.
I care about conversion, retention, growth and revenue, but also about what we're optimizing and what behavior those decisions encourage. The highest-converting solution isn't automatically the best long-term product decision.
The interesting problems are often the ones where user and business incentives can be made to point in the same direction.
Process should have a reason
I've worked in teams and understand why shared planning, documentation and coordination matter.
But a team of twenty, a team of three and a team of one don't need the same machinery.
I scale process with the people, risk and complexity involved. The same applies to tools: I move between design, code, AI, research and data based on what helps me answer the question.
Tools change. The goal doesn't: understand the problem well enough to make a better decision.
— Petteri
Petteri Helttula — Portfolio
Spotify
