Compare lightweight concepts before coding
Choose one concept for deeper investment while preserving its evidence, assumptions, and rejected alternatives.
- Preparation
- A focused concept preparation and review session.
- Steps
- 3
- Difficulty
- Moderate
- Task
- Choose a concept to invest in
Requires: Bring the agreed problem, audience, research evidence, decision owner, and capacity available for the next test. Choose a representation that can expose the assumption without pretending to be a finished product.
Uses: Figma
Back to the Task: Choose a concept to invest inBefore you start
Prepare
- Bring the agreed problem, audience, research evidence, decision owner, and capacity available for the next test.
- Choose a representation that can expose the assumption without pretending to be a finished product.
Steps
Work through the method
Use the listed inputs and tools. Check the evidence when you need to verify a step.
Set the comparison decision
Write the problem, target user, evidence already collected, decision owner, available investment, and unresolved assumption. Exclude concepts that address a different problem.
Step details and sources
Why it matters: A shared decision boundary stops visual polish from replacing evidence.
- Input
- The approved research finding, product constraint, and available investment.
- Output
- A one-page comparison brief with fixed evidence fields.
Tools in this stepFigmaEvidence for this step
Productboard’s founders used lightweight prototypes before coded versions and abandoned a sophisticated concept without a repeat-use case.
First Round Review: A barrage of experiments; The first prototype to really resonateA retrospective founder account supports staged fidelity. It does not provide a universal selection threshold.
Represent each concept at comparable fidelity
Create one separate Figma flow for each digital concept. Show only the path needed to expose the unresolved assumption, and link the same research evidence beside every flow.
Step details and sources
Why it matters: Comparable, lightweight representations reduce avoidable coded investment while keeping the evidence visible.
- Input
- The comparison brief and competing concept outlines.
- Output
- Separate prototype links with evidence and assumption notes.
Tools in this stepFigmaEvidence for this step
Productboard’s founders used lightweight prototypes before coded versions and abandoned a sophisticated concept without a repeat-use case.
First Round Review: A barrage of experiments; The first prototype to really resonateA retrospective founder account supports staged fidelity. It does not provide a universal selection threshold.Figma can create separate prototype flows, define starting points, connect frames, and share a link to a flow.
Figma: Flows and starting points; Create connectionsThe operations represent digital interaction concepts. They do not compare evidence or choose a concept.
Record the investment decision
Review each concept against the fixed fields. Record one advance, revise, or stop decision, the evidence used, the unresolved assumption, and the next test. Keep rejected concepts traceable.
Step details and sources
Why it matters: The decision needs a reviewable basis and must preserve uncertainty.
- Input
- The concept flows, linked evidence, and reviewer notes.
- Output
- A dated product investment decision and next-test brief.
Tools in this stepFigmaEvidence for this step
Productboard’s founders used lightweight prototypes before coded versions and abandoned a sophisticated concept without a repeat-use case.
First Round Review: A barrage of experiments; The first prototype to really resonateA retrospective founder account supports staged fidelity. It does not provide a universal selection threshold.
Success checks
Check the result
- One concept has a named next test and investment boundary.
- Every concept links to the same problem evidence and records its unresolved assumption.
- The decision does not claim demand, adoption, or commercial viability from prototype reaction.
Failure modes
What could go wrong
- Stop when the concepts answer different problems or audiences.
- Return to Customer Research when the underlying problem evidence is missing.
- Use a different representation when a digital flow cannot expose the important assumption.
Tools
Choose tools
Figma
A design workspace for keeping several lightweight digital concepts in separate, shareable prototype flows.
Check fit, limits and pricingSources
Check the sources
Check what each source supports and where the advice has limits.
- First Round Review: Productboard's Path to Product-Market FitEdited founder interview · Publication date unavailable
- GOV.UK Service Manual: How the alpha phase worksPublic-service method guidance · Publication date unavailable
- Figma: Guide to prototyping in FigmaOfficial product documentation · Publication date unavailable