Discovery
I get clear on the user, the business goal and the success metric. We need to agree on what the problem is before deciding what gets designed.
Design · Service
UI-UX design and user experience
User experience design isn't making a screen prettier; it's lining up the question in someone's head with the answer on the screen. I make your product testable before it is built.
- Category
- Design
- Typical timeline
- 2-5 weeks
- How I work
- Design + development from one person
What you get
What do you have
when this is done?
The list below isn't a marketing promise, it's the delivery list. It goes in the contract too.
- 01
A clickable prototype you can test before a line of code is written
- 02
A design file a developer can implement without guessing
- 03
A component system that keeps new screens consistent
- 04
Interfaces that meet accessibility and contrast standards
Scope
How the process
moves, step by step.
At every step I share plainly what has been completed and what comes next.
Information architecture and flows
I map the steps a user takes to reach their goal, remove the unnecessary ones and make the flow visible.
Wireframes and prototype
I test the structure quickly with low-fidelity screens, then try it on real users with a clickable prototype.
Interface design
I build the typography, colour, spacing and component system, and complete every screen in desktop and mobile form.
Design system and handover
I make components reusable, define states (empty, loading, error) and run the handover to developers.
Deliverables
Everything handed
over to you.
On a one-off project, the source code, design files and accounts are yours once it's complete, and you're under no obligation to keep working with me. If you continue with a monthly arrangement, the working copy stays with me so the code stays current, and you receive it in its latest state when the arrangement ends.
- Figma file: flows, wireframes, final screens
- Clickable prototype
- Component library and design tokens
- Definitions for empty, loading and error states
- Developer handover document
Frequently asked
The questions
on your mind.
I moved the most common proposal-stage questions here; neither of us enjoys email ping-pong.
Can we take just the design and have our own team build it?
Yes, that's a common arrangement. I deliver the design at a quality a developer can pick up: component system, states and tokens all defined. If you want, I can also provide design oversight during development as a separate engagement.
Do you run user testing?
I run moderated tests on the prototype. Five to eight users is enough to surface most of the serious problems. Participant recruitment and incentive budget are a separate line item.
Can you improve the design of our existing product?
Yes. In that case I start by reviewing the current product and any analytics data to find where you're losing people, then recommend prioritised improvements rather than a redesign from scratch.
We don't have a brand identity — should we do that first?
Not essential, but it helps. Without one I'll establish a consistent visual language inside the product; if you want a separate brand identity project, I do that too.
Related services
You might also
be interested in.
Most projects aren't one service, but a combination of several.
Next step
Let's talk about your project.
Write down what you want to build and we'll settle the scope, a realistic budget and the next step together. The first call is free.