The Complete Product Design Process for SaaS
A SaaS product design process moves from a business problem to a measured change in user behaviour. Each stage has a clear output, a decision owner and a gate that says whether the work moves on. Without gates, the process becomes a series of screen reviews that never reach a decision.
Stage 1: Discovery
Discovery answers what problem is worth solving and for whom. Inputs include customer interviews, sales and support notes, analytics and competitor reviews. The output is a short problem statement, a list of user types and the questions that remain open.
Gate: the team agrees on the primary user and the problem they will work on.
Stage 2: Journey mapping
Map the current journey for the primary user, including workarounds outside the product. Mark the moments of friction and the moments of delight. Identify the points where data or permissions are needed, because these often drive the complexity of the solution.
Output: a journey map with evidence attached to each stage.
Stage 3: Solution framing
Generate options for the biggest friction points. Compare them against effort, risk and expected impact. Choose a small set for prototyping. Keep the rejected options with reasons, so the team does not revisit them in two months.
Gate: the team agrees on what the first release will and will not include.
Stage 4: Prototype and test
Build a clickable prototype of the chosen flow. Test it with at least five people from the target group. Record where they stop, guess or ask for help. Change the flow and test again until the core task completes without assistance.
Stage 5: Interface and systems
Design the production screens, states and components. Use the shared system wherever possible. Document rules for spacing, content, errors and accessibility, so the next designer does not invent new patterns.
Gate: design review against the agreed states, including empty, loading, error, permission denied and edge cases.
Stage 6: Handoff and build
Hand over specifications, component references and a list of decisions made during design. Attend the first build review. Catch mismatches early, when fixing them is cheap.
Stage 7: Measure and learn
Define the measure before launch. Track the core path, the drop-off points and the support tickets related to the feature. Review the results after a fixed period and decide whether to iterate, extend or retire the change.
What the process is not
The process is not a waterfall. Teams loop between stages, especially between prototype and journey mapping. The discipline lies in the gates, not in the order. A team can skip a stage for a small change, but it should never skip the measurement stage.
A starting checklist
- Primary user named and interviewed
- Current journey mapped with evidence
- First release scope written down, with exclusions
- Prototype tested with five target users
- States designed and reviewed
- Handoff documented and build reviewed
- Measure and review date set
A process that fits on one page and that the team actually follows will beat a detailed framework that nobody reads.
Next step
Get help improving conversion
Send me the page or flow that loses people. I will tell you where the friction is and what to change first.
Open the conversion page