Map it before you design it
See every path through your app before anyone designs a screen
We map how each type of user moves through your product, from first sign-up to the thing they come back for, including what happens when something goes wrong. You get flow diagrams and written step-by-step paths that a designer and a developer can both work from.
What you get
What’s included
User types
The different people using the product, such as member, coach, admin or front desk, and what each one is trying to get done.
End-to-end paths
Each user's route from first contact to repeat use, written out step by step.
Flow maps
Diagrams of the screens, decisions and branches in the core flows, such as sign-up, booking, payment and check-in.
Unhappy paths
Failed payments, expired memberships, no-shows, forgotten passwords and the other cases plans often skip until support tickets arrive.
Staff-side flows
What coaches, admins or front-desk staff need to do behind each user action.
Decisions for you
Places where a flow depends on a business rule you haven't set yet, flagged before design starts.
A good fit if
- Founders about to hire a designer who want to brief them properly
- Gyms and studios planning member apps with bookings, payments and cancellations
- Coaching and wellness platforms with more than one type of user, like coach and client
- Teams whose live app has drop-off nobody can explain
Not included
- Wireframes, visual design or clickable prototypes
- Usability testing with real users
- Feature prioritisation or a release roadmap
How it runs
From kickoff to handover
- Step 1
Users and goals
We agree who uses the product and what each type of user is there to do.
- Step 2
Draft the paths
We write each path end to end and diagram the core flows, branches included.
- Step 3
Break them
We go back through every flow looking for what could fail, and add the unhappy paths and staff-side steps.
- Step 4
Review and handover
You answer the open business questions, we finalise the maps and hand them over.
Questions
Questions about User journeys & flow maps
Are flow maps the same as wireframes?
No. Flow maps show steps, decisions and branches. Wireframes show layout. With the logic settled first, your designer can spend their time on the screens instead of working out what happens when a payment fails.
Why spend time on unhappy paths?
Because they're where support load and refunds come from. A booking app that handles a full class, a late cancellation and an expired card from day one avoids a lot of manual fixes by staff later.
Can you map an app that's already live?
Yes. Mapping what's live shows where flows dead-end or confuse people, which is useful before a redesign, a rescue or a new feature.
Who from my side should be involved?
Whoever deals with customers day to day: front desk, coaches or support. They know the edge cases that never show up in a founder's description of the product.
More from Product Strategy
Keep exploring
Often paired with this
Work with us
Ready to start User journeys & flow maps?
Tell us about your business. We'll confirm the scope and send you a start date.