Purpose
To ensure UX flows are end-to-end, logical, and robust — covering all tasks, decisions, and states before wireframe execution.
Flow Completeness Checklist
| Item | Check | Status (☑/✗) | Notes |
| Flow Boundaries | Start and end points are clearly defined | ||
| Task Coverage | All tasks/sub-tasks from Task Scenario Breakdown are included | ||
| Decision Points | Each decision has ≥ 2 branches (Yes/No, Success/Fail) | ||
| Happy Path | Core flow is clearly documented | ||
| Error Paths | All error/exception paths included (timeouts, invalid inputs, API fails) | ||
| Empty States | Empty states mapped for data-driven screens | ||
| Loading States | Loading indicators defined | ||
| Permission States | Role-based access restrictions included where relevant | ||
| System Responses | Each step has a defined system reaction (confirmation, error, redirect) | ||
| Consistency | Naming conventions, IDs (F1, F2…) consistent across flow | ||
| Clarity | No ambiguous steps (e.g., “user does something”) | ||
| Annotations | Notes for dev/PM included where needed | ||
| Business Alignment | Flow supports stated business & success goals | ||
| User Alignment | Flow resolves core user goals & pain points | ||
| Review Done | Peer review completed | ||
| Sign-Off | Design Lead approved |
Usage Notes
- Fill this checklist during peer review of UX flows.
- A flow cannot move to wireframes until all boxes are ☑.
- Keep checklist stored alongside final flow diagram for audit.
Outcome: Guarantees that every UX flow is complete, logical, and resilient, preventing redesigns during wireframes or dev.