Services Product design
Prototyping
Clickable prototypes that let you test an idea with real people before it is built.
At a glance
- Includes
- Low-fidelity flows, interactive prototypes, test sessions and notes on what changed
- Works with
- Your idea, research and any early designs
- Delivered as
- Prototypes and a short write-up after each round
- Starts with
- A conversation about the idea and what you want to find out
Fit
Is this right for you?
Usually the right call when one of these sounds familiar.
An idea not yet tested
You want a reaction before spending on a build.
Stakeholders cannot picture it
A description in words is not enough.
Unsure which flow is best
Two or three ways to do the same thing.
Testing planned with users
You need something real enough for people to try.
Not the right service? Still unsure what people need: UX research. Final screens for development: UI design.
Scope
Scope and what you get
Each piece of work has a matching thing you receive.
- What we do
Flow sketches
Quick, low-fidelity flows to compare ideas early.
What you receiveOptions to compare
Simple flows you can react to before anything is polished.
- What we do
Interactive prototypes
Clickable screens that behave like the product for the paths being tested.
What you receiveSomething to try
A prototype people can click through on a phone or computer.
- What we do
Test sessions
Sessions where people attempt tasks while we observe.
What you receiveWhat people did
Observations from each session, with what worked and what did not.
- What we do
Round notes
A short write-up after each round of testing.
What you receiveWhat to change next
Notes on what changed after each round and why.
Use cases
Relevant use cases
Practical situations where this service is put to work. Open a card to see how it applies.
Testing an idea before building
A prototype of the main flow, tried with users before any development begins.
- A clickable version of the key flow
- Sessions with people from your audience
- A clear view on whether to proceed
Comparing two ways to do it
Two or three versions of a flow, tested against each other.
- Variants built quickly
- The same tasks given in each
- A recommendation with reasons
Showing stakeholders the plan
A prototype that helps decision makers see what they would be funding.
- The main journey made clickable
- Walk-through for the decision makers
- Questions and answers recorded
Sample use cases, drafted as placeholders. The Plethora team confirms the final list.
Process
How it works
Each stage is agreed with you as we go. Each shows what we do and what we need from you.
Frame
We doWe agree the idea, the question to answer and the flows to test.
You doYou tell us what you need to know and who should test it.
Sketch
We doWe draw low-fidelity flows and compare options.
You doYou choose which flows to take forward.
Build
We doWe turn the chosen flows into a clickable prototype.
You doYou try it and tell us what is missing.
Test
We doWe run the sessions, note what happened and update the prototype.
You doYou attend if you wish and decide what to change next.
Quality
Quality and handover
How the work is checked, accepted and passed to you.
Built to answer a question
Each prototype exists to test something specific.
Real people
Sessions use people who match your audience.
Changes recorded
Each round is written up, including what changed and why.
Prototype is yours
Files are delivered to you at the end.
Tools
Tools and technology
Tools we use in delivery. We choose them to suit your team, and the list does not imply any partnership. Logos belong to their owners.
- Figma
- Miro
Engagement
Engagement and cost factors
Ways to work with us
A scoped project
A defined prototype and test rounds, with notes.
Alongside your team
Our designers join your team for a period.
Regular testing
A rhythm of prototype tests as ideas come up.
What shapes scope, timing and cost
- Number of flows to prototype
- How realistic the prototype needs to be
- Number of test rounds
- Number and type of participants
- Whether the prototype runs on phone, desktop or both
- How much reporting your team needs
Scope and cost are confirmed with you in writing before work starts.
FAQ
Frequently asked questions
No. A prototype is for learning. If you proceed, the findings feed the designs and the build.
As realistic as the question needs. Early rounds can be simple sketches, later ones more detailed.
Yes. We can use your customers or help find people who match them.
It depends on what you want to find out. We propose a number before we start and adjust it with you as we learn.
Test the idea before you build it. Start with a conversation.
Tell us what you want to build and we will come back with next steps.
Talk to usRelated