About
I’m Harri Halonen — an experience and product designer based in Tampere, Finland. I work where business goals meet technical reality, turning ambiguous requirements into clear workflows, reusable patterns, and design that’s ready to build.
Most of my work lives in complex B2B and product systems — the kind with real edge cases, long-lived data, and users who can’t afford a confusing screen. I’m just as comfortable slowing down for trust-sensitive and health-adjacent contexts, where the right move is to design quietly and carefully.
My background runs through HCI, service design, and enough field research to know that what people say they want and what they actually need are usually two different conversations.
What I’m focused on right now:
- Complex product systems — workflows, states, and edge cases that hold up over time
- Design systems — reusable patterns a team can actually build on
- Discovery — research-led framing before anyone touches pixels
- AI and data workflows — making dense information legible and actionable
- Implementation quality — staying close to the build so the design survives it
How I lead
I lead through craft and facilitation, not a title. I haven’t held formal line management, so what I offer sits elsewhere: raising a team’s design quality from inside the work — running critique, mentoring designers earlier in their path, and holding a quality bar that survives handoff.
Most of it is enablement. I turn one-off calls into shared standards, keep cross-functional conversations aligned on the same picture, and make the design system something a team leans on instead of relearns. When designers and engineers pull in different directions, I facilitate toward a decision rather than dig in.
A lightweight operating model I bring to design quality:
- Critique — regular, structured sessions that pressure-test work before it ships
- Accessibility review — checking contrast, focus, and semantics early, not as a final gate
- Implementation notes — writing down the intent behind a design so the build keeps it
- Decision logs — recording what we chose and why, so nobody relitigates it later
- Post-release quality review — looking at what actually shipped and feeding it back into the system
These rituals earn their place through what they prevent. Decision logs stop teams relitigating settled calls; early accessibility review keeps rework out of the final week; implementation notes keep the build honest to the intent. What comes out the other side is clearer decisions, fewer clarification rounds, and interfaces that stay consistent as they scale — leadership measured by the work, quietly and in practice.
How I approach the work
A few principles that shape most of what I design — the judgment underneath the case studies.
Map the business process before the UI
I diagram how the work really moves — who hands off to whom, where it stalls — before I draw a single screen.
Design for experts without punishing beginners
The fast path stays fast for daily users, while a first-timer still gets clear labels, safe defaults, and a way back.
Use systems to pay down decision debt
I settle a repeated choice once as a pattern, so the tenth screen doesn't relitigate what the first one already answered.
Treat implementation as part of the design
I stay in the codebase through the build, because a design only really exists once it survives real data and a real deadline.
Use AI to support judgment, not replace it
AI can draft, rank, and summarize; the person keeps the decision, the override, and the accountability for it.
Name states, permissions, and errors early
Empty, loading, denied, and failed get designed with the happy path — not bolted on after QA finds the gaps.
Measure quality by outcomes, not output
I judge a screen by the tasks people finish and the tickets that stop arriving, not by how it looked in the review.
In 2021 I wrote my master’s thesis on interaction design for industrial XR at Tampere University. Off the clock: film photography and basketball.
If your team is thinking about any of this — product design roles, complex product systems, design systems, or AI and data workflows — I’m glad to compare notes. The easiest way is to reach me on LinkedIn, or by email — my first name, here at this domain.