Service 02
From research to pixel-precise prototypes. Context first.
I started as a designer before I learned to code. That sequence matters. I understand what it costs to design something that can't be built, and I've stopped designing those things.
Context always comes first. A dashboard for emergency dispatch coordinators is not the same problem as a dashboard for energy traders, even if they look similar in a wireframe. I do the research to understand the difference — who the user actually is, what environment they're working in, what they're afraid of getting wrong.
I design systems, not screens. Screens are a side effect of good design thinking. The deliverable I'm most proud of is never the final mockup — it's the shared vocabulary between the design and engineering team that makes building it feel obvious.
Deliverables
How I work
User interviews, stakeholder sessions, competitive analysis. I don't start in Figma. I start with questions. What does success look like? What does failure look like? Who gets blamed when it goes wrong?
Information architecture, user flows, content hierarchy. The structural decisions that determine whether a product is learnable or not. Easy to skip. Impossible to retrofit.
Low-fidelity first to validate structure, then high-fidelity to validate execution. I test with real users before the design is final, not after development starts.
Design tokens, component specs, interaction notes. I hand off to engineers, not at engineers. If something is ambiguous in the spec, it will be ambiguous in the product.
Tools & tech
Related work
FAQ
Ready to start?
Based in Poland, open to remote work across Europe and beyond. My inbox is genuinely friendly.