How I Work
No two projects start from the same place, so I don't force one process onto all of them. What stays constant is this: reduce uncertainty early, test before committing, and keep the team grounded in evidence rather than opinion.
Understand
Talk to users and stakeholders, look at existing data, define the real problem — not just the one in the brief. Agree on constraints and success criteria before sketching anything.
Explore
Sketches, flows, rough prototypes. Make ideas tangible fast so we can compare directions and kill weak ones early, before they're expensive to kill.
Sketches, flows, rough prototypes. Make ideas tangible fast so we can compare directions and kill weak ones early, before they're expensive to kill.
Test and Iterate
Test the riskiest assumption first, not the easiest one. Usability testing, accessibility review, real user feedback — throughout, not as a checkbox at the end.
Test the riskiest assumption first, not the easiest one. Usability testing, accessibility review, real user feedback — throughout, not as a checkbox at the end.
Design and Deliver
Once testing says a direction holds, I build the UI closely with developers and product owners — using existing design systems, or contributing to one where it's missing. I stay through implementation. Handing off a file isn't the job; shipping something usable is.
Once testing says a direction holds, I build the UI closely with developers and product owners — using existing design systems, or contributing to one where it's missing. I stay through implementation. Handing off a file isn't the job; shipping something usable is.
Measure and Learn
Define success metrics before launch. After launch, check them — analytics, support data, follow-up research — and use what's true to shape what's next.
Define success metrics before launch. After launch, check them — analytics, support data, follow-up research — and use what's true to shape what's next.
Areas of Expertise
Accessibility — CPACC-certified. [X years] designing accessible public-sector services in Sweden, including [named project + outcome, e.g. "WCAG 2.1 AA redesign of [X], reducing support tickets by X%"]. Built in from the start, not bolted on at the end.
Design Systems — Built and maintained reusable component libraries across [X products/teams]. A design system is a shared tool for speed and consistency — not just a UI kit.
Research and Facilitation — Run interviews, usability studies, and workshops that produce a direction the whole team can act on, not just a pile of notes.
Product and Service Design — Connect individual screens to the wider service, from early discovery through implementation.
Cross-Functional Collaboration — Work daily with users, business stakeholders, developers, and product owners. Alignment across a team is often as much of the job as the design itself.