App or product design
Flows, screens, platforms and the fidelity ladder — from wireframe to handoff.
4 sections · 17 questionsflows/screens → deliverables
The questions
Linear sections, no branching.01
Who uses this product, and what problem are they trying to solve with it?
02
Does this product exist today, or are we designing the first version?
03
What is the one metric this design has to move?
04
Where do users get stuck today, and how do you know?
05
How many core user flows are in scope?maps to deliverable count
06
Roughly how many screens per flow?maps to deliverable count
07
Which platforms? (iOS, Android, web)
08
Does each platform need its own screens, or does one responsive set do it?maps to deliverable count
09
Are onboarding, empty and error states in scope for every flow?maps to deliverable count
10
Where does this stop: wireframes, high fidelity, or a clickable prototype?maps to deliverable count
11
Does the engineering team need a design system handoff?maps to deliverable count
12
Is there an existing design system or component library to work inside?maps to deliverable count
13
Do you need production-ready assets and icons exported?maps to deliverable count
14
How many usability review rounds are included?maps to included revisions
15
Will we test with real users, and can you recruit them?maps to deliverable count
16
Who decides when the people involved disagree?
17
Which engineering sprint is waiting on these designs?maps to deadline
Free to copy — the hosted version carries your branding.Use it in Tave