What it is
Simplified wireframes, sketches, or clickable mockups outlining core workflows without visual detail, to communicate and test flows quickly.
Why use it
Low-fidelity prototypes allow cheap, rapid iteration. Testing flows before visual design reduces the risk of rework and focuses feedback on structure.
Use this when
- You need to test or communicate basic flows or navigation
- Several structural approaches are worth exploring
- Stakeholders or developers need to see the intended workflow
You may not need this when
- The workflow is established; only visual refinement remains
- A high-fidelity prototype from an earlier cycle exists
- Building directly is faster for a simple change
Dependencies — what you need
- A validated problem statement and finalized use cases
- Clarity on technical constraints
- Fast feedback loops with Product and stakeholders
People involved
- Design
- Product
- Engineering (feasibility input)
Typical outputs
- Wireframes or paper prototypes of key flows
- Annotated flow diagrams
- A clickable prototype for testing
- Open design questions
Template
Lo-Fi Prototyping template
A fill-in structure for running this method: what to prepare, what to do, what to record, and how to read the result.
How AI can help
AI as augmentation — not replacement
- Generate realistic labels, placeholder data, and error states
- Suggest alternative interaction patterns
- Identify edge cases not yet represented
- Draft annotations explaining decisions
AI prompt
A prompt for any AI assistant. It works only from material you paste in, keeps assumptions apart from findings, and leaves the decisions to you.