4.3Prototyping quickly (low-fi)
The essentials in 30 seconds
- Make tangible: the prototype materializes the idea (sketch, paper mock-up, scenario) to make it testable, far from the finished product.
- Low-fi to learn: fast, simple, cheap — the goal is to learn fast, not to look good.
- Fail fast and cheap: easy to throw away and redo with no regret, it invites frank feedback before any heavy investment.
Running case — Sara and her one-hour paper mock-up
Sara wants to redesign the sign-up flow. First reflex: ask for three weeks of development of the real form. She switches to low-fi: a paper mock-up of the screens in one hour, shown the same day. Problems jump out before a line of code. She fixes on paper, only then has it developed.
Sequel to cases 4.1-4.2 — Sara moves from priority to tangible with no investment.
1. Making the idea tangible
An idea, while it stays abstract, does not tell you if it works. Prototyping materializes it to make it tangible and testable. The key principle, especially at the start: the low-fi prototype — a fast, simple, cheap version.
A sketch, a paper mock-up, a played scenario or a simulation are enough to give body to the idea. Far from a finished product, Sara materializes in one hour what she had discussed for weeks.
2. Simple and fast, to learn
The prototype's goal is not to be beautiful, but to learn: test, show, gather reactions, detect problems — as early and cheaply as possible.
Advantages: it is done in minutes/hours, costs almost nothing, and above all does not attach you emotionally — you throw away and redo a sketch with no regret. Fail fast and cheap to learn and iterate.
3. Against early perfectionism
It is the opposite of the perfectionist reflex — finalizing everything before showing — which wastes time and money on unvalidated ideas.
Making an idea tangible, even roughly, teaches more than an hour of abstract discussion. Done beats perfect, especially at the prototype stage. You polish later, once the idea is validated.
🔎 Concrete example — The sketch beats the finished product
Testing a new sign-up flow.
Perfectionist: 3 weeks coding the real form → testers reject it.
Low-fi: paper mock-up of screens in 1 hour → problems detected the same day, fixed before coding.Result: you detect problems before investing.
Reflex: a rough prototype invites franker feedback.
Section vocabulary
- Prototype
- A materialized version of an idea to make it tangible and testable.
Simple example: Sara's paper mock-up for the sign-up flow.
What it is not: an abstract discussion with nothing to show or touch.
Reflex: always show something, even rough.
- Low-fi (low fidelity)
- A fast, simple, cheap prototype (sketch, paper mock-up, scenario), far from a finished product.
Simple example: the screens Sara sketches in one hour.
What it is not: the form coded in three weeks before any test.
Reflex: aim for minutes/hours, not weeks.
- Rapid prototyping
- Materializing an idea fast and cheap to learn and iterate early.
Simple example: Sara tests the same day instead of waiting for development.
What it is not: finalizing in a corner before showing anything.
Reflex: show early, even imperfect.
- Fail fast and cheap
- The principle of testing early at low cost to detect problems before investing heavily.
Simple example: Sara bins a failed sketch with no regret instead of a month of code.
What it is not: discovering failure after a big unrecoverable investment.
Reflex: test small before investing big.
- Emotional detachment
- Advantage of the simple prototype: you throw away and redo with no regret, unlike a polished product.
Simple example: Sara remakes a paper screen in ten minutes, unattached.
What it is not: defending a costly prototype because you invested too much in it.
Reflex: if binning hurts, it was too polished.
In practice — Prototyping quickly (low-fi)
- Materialize your idea in a simple, fast form (sketch, paper/cardboard mock-up, played scenario, simulation).
- Aim for speed and low cost, not beauty: the goal is to learn, not produce a finished object.
- Use the prototype to test, show and gather reactions as early as possible.
- Accept throwing away and redoing with no regret: fail fast and cheap to iterate quickly.
Ready-to-say script — proposing low-fi (30 s)
Before coding or printing, we make a paper mock-up in one hour and show it to three people today. If it blocks, we fix on paper — we will only develop what passes the test.
To say to stop early perfectionism and impose testing before investment.
Copy-paste template — low-fi prototype sheet
IDEA TO MATERIALIZE: _______________
LOW-FI FORM (sketch / mock-up / scenario): _______________
DONE IN (duration + cost): _______________
SHOWN TO (3 people): _______________
DETECTED PROBLEMS: _______________
TO BIN / TO REDO: _______________Small business / tight budget
With no means: paper, markers and a phone to film are enough — a tested sketch beats a beautiful file never shown.
SME in Algeria
Accessible field and customers: test the paper mock-up directly at the counter or workshop, with no logistics.
Service / process
No object to mock up: play the scenario in pairs, draw the step storyboard, simulate small-scale.
Digital interface
Paper screens then a simple clickable mock-up: you test the flow before a line of final code.
✓ Best practices
- Keep it simple and fast: minutes/hours, not weeks.
- Prototype services and processes too (played scenario, storyboard).
- A deliberately rough prototype invites richer criticism.
✗ Common pitfalls
- Early perfectionism: finalizing everything before showing.
- Getting attached to a long-polished prototype (you no longer dare bin it).
- Believing you cannot prototype a service or a process.
Key takeaways
- Prototyping materializes an idea to make it tangible and testable.
- Prefer low-fi (sketch, paper mock-up): fast, simple and cheap.
- The goal is not to be beautiful but to learn: detect problems early and cheaply.
- Advantages: fast, cheap, binned and redone with no regret; fail fast and cheap.
48h challenge — apply tomorrow
Materialize 1 idea as low-fi (sketch or mock-up) in under one hour with the sheet above, and show it to 3 people to gather reactions.
- I can cite 3 low-fi prototype forms.
- I know why rough invites more feedback than polished.
- I showed 1 fast prototype to 3 people.
Frequently asked questions
Why a rough prototype rather than a polished one?
Because the goal is to learn fast, not to be beautiful. A sketch is done in minutes for nothing, a polished version takes weeks. You bin a sketch without hesitation, you cling to polished work. And a rough prototype invites criticism better: facing finished work you do not dare criticize, facing provisional work you propose.
Can you prototype a service or a process?
Yes. For a service: play a scenario, a storyboard, a light simulation. For a process: schematize it, simulate it small-scale. For an interface: paper or clickable mock-ups. The question is not is it prototypable but what fast form would make this idea tangible.
Sara wants to test her flow before coding. What does she do in one hour?