What it is
The practice of explicitly designing all the states an interface can take, empty, loading, error, partial, success, permission-denied, so the experience holds up beyond the happy path.
When to use it
During Prototype, before handoff, to ensure edge and error states are designed, not improvised.
Why (value)
Prevents the common failure of shipping only the ideal state; users constantly hit empty, loading, and error conditions.
How to run it
- Enumerate the states each key screen can be in.
- Design each state: empty, loading, error, partial, success.
- Include content for zero and error cases.
- Review for coverage and consistency.
- Specify for engineering.
Inputs and outputs
- Inputs: Screen designs and knowledge of possible states.
- Outputs: A complete set of designed UI states.
Time and effort
Low. Incremental with design work.
Evidence and limitations
A design-completeness artifact, not evidence; still validate that state messaging is understood. See Evidence and limitations.
Tips and pitfalls
- Never ship only the happy path.
- Write real empty/error copy, not lorem ipsum.
- Cover permission and offline states too.
Variations
State inventories, edge-case matrices.
Related methods
Need help choosing and applying a method?
Gumshoe helps teams connect research, collaborative workshops and service design to the decisions they need to make.
Sources and further reading
- UX Tigers, “100 UX methods.”
Explore related methods
- Wireframing — Lay out structure and content priority without visual design to focus on function.
- Microinteraction design — Design the small, single-purpose moments, toggles, feedback, that make an interface feel right.
- Use cases — Specify the steps of an interaction between a user and system, including alternate and error paths.
