Description
Choose a prototype's breadth and depth for the question at hand, link wireframes into a wireflow of navigation states, and raise fidelity in planned stages.
Wireflow prototyping is about planning a prototype rather than just drawing one. Scope comes first: horizontal prototypes are broad and shallow (many features, little depth), vertical ones narrow and deep, T prototypes combine both, and local prototypes isolate one detail so users can settle a design deadlock. Wireflows are directed graphs of wireframes derived from state diagrams of task sequences, showing each screen state and the transitions between them. Fidelity is raised in planned levels, from sketched wireframe decks to click-through and visually high-fidelity prototypes, often from a template library. For empirical tests, Hartson and Pyla add plausible decoy objects and a 'not implemented' message, so that tasks are not unrealistically easy along a happy-path-only prototype.
Attributes
- Discipline
- Design & Product Practice
- Loss type
- Active
- Stage
- Design
- Data
- Analytical / expert
- Effort
- Days
Steps
- Decide what the prototype must answer and choose its scope: horizontal, vertical, T or local.
- Draw state diagrams of the main navigation from task sequence models.
- Create a wireframe for each state and link them into a wireflow showing transitions.
- Raise fidelity in planned levels (sketch, wireframe, click-through, visual), reusing a template library.
- Before user testing, add plausible decoy objects and a 'not implemented' message for unbuilt paths.
- Refine through evaluation and repeat at the next fidelity level.
Sources
- The UX Book (Hartson & Pyla, 2019)
- Handbook of Usability Testing (Rubin & Chisnell, 2008)
- Usability Engineering (Nielsen, 1993)
Also known as
- Wireflow prototype
- Horizontal, vertical, T and local prototypes
- Graduated fidelity prototyping
- Decoy interface objects
Categories
- Design
- Design & Product Practice