What’s included
(05)Teams spend weeks debating a design in meetings, then find out after launch that users wanted something else.
-
Clickable flows
The key tasks built as a prototype people can tap through on their own phone or laptop, close enough to the real thing that they forget it is not.
-
Real content
Your actual words, products and numbers in the prototype, so people react to what they will really see.
-
Tests with real people
Short sessions with people who have never seen the product, asked to do a task while we watch where they hesitate.
-
Comparing options
Where the team is split, we prototype both routes and let users settle it.
-
Findings you can act on
What worked, what confused people and what to change, written plainly and tied to the screen where it happened.
When you need it
- Your team cannot agree on a design and the meetings keep going
- You want to test an idea before paying to build it
- You need to show investors or stakeholders how the product will work
- A key flow, like sign-up or checkout, is losing people
How it runs
(04)You get a written scope, a fixed price and a start date before anyone begins.
-
Pick the question
The one or two things you most need to learn, and the tasks that will show them.
-
Build
A clickable prototype of those tasks, with real content, on the devices your users have.
-
Test
Sessions with people who match your users. We watch, ask few questions and take notes.
-
Report
What we saw, what it means and what to change, with the prototype updated where the answer is clear.
What you leave with
- A clickable prototype of the key flows
- Test sessions with people who match your users
- A plain findings report, screen by screen
- An updated prototype with the fixes in
- A clear answer on which option to build
Also in Design
Start your project with us
FAQ
Answered questions.
A prototype looks and clicks like the product but has nothing real behind it, so it is quick to make and change. An MVP is a small working product. We use prototypes to decide what the MVP should be. If you need working code fast, see rapid prototyping.
Enough to see the pattern. A handful of sessions usually shows the main problems, and we stop adding people when they stop telling us anything new.
Yes. A prototype that people can click through on a phone explains a product faster than a deck, and you keep the file.
Yes. If your team has a prototype, we can plan and run the sessions and report what we find.
