Product design and UX/UI
I turn complicated products into experiences people understand and use. I cover research, information architecture, flows, prototypes, visual interface and the design system for web and mobile. I validate the important decisions before development so the team can build with more clarity and spend less time rebuilding.
Product design and UX/UI
The problem
The product has the right features, but people can't find them, don't understand them or give up along the way. The development team receives incomplete screens, and every new page looks different from the last.
What you get
- shorter flows for the actions that matter (sign-up, purchase, booking);
- a consistent interface that is easy to extend;
- a design system that speeds up the development of future screens;
- decisions backed by testing, not opinions.
How I work
Discovery: stakeholder workshops, user interviews, competitive analysis.
Strategy: redefined UX goals, design brief.
Design and prototyping: flows, wireframes, design system, interface.
Validation: usability testing, A/B testing, surveys, iterations.
Delivery: annotated Figma files, documentation, QA check-ins with developers.
Deliverables
- flow maps and journey maps
- wireframes and an interactive Figma prototype
- final interface for every breakpoint
- design system (tokens, components, patterns)
- design and development documentation
- test results
Who it's for
Startups building or rebuilding an MVP; product teams in fintech, SaaS and analytics; companies with an ageing app and usability complaints.
From my projects
Peace Nest: design system, iOS & Android app and web app.
Bold Rewards
Bold Rewards: design system, white label and Admin CRM, for over 1,000,000 fans.
Frequently asked questions
What is the first step in a project?
Tell me briefly what you want to build or improve. I read your brief and follow up with questions; we can arrange a call if needed. You then receive a proposal with the scope, stages and price. You don’t need a technical plan ready.
What is a design system and when do I need one?
A design system is a library of components, visual rules and interaction patterns that designers and developers use the same way. You need one when the product has many screens, several platforms or several teams, so the interface stays consistent and new screens are built faster.
Does every project need user research?
Not every project needs a large study. I choose the method around risk and what is already known: interviews, analytics, support tickets, prototype testing or a rapid review. The important point is that critical decisions are not based only on internal preference.
How do you make sure the design is implemented correctly?
I organise components, states and responsive rules into a coherent system, document important cases and review the product with developers. When I also cover implementation, I use the same rules directly in code, reducing the gap between prototype and released product.