What a good flow includes
A useful flow covers much more than the ideal path:
| Element | What it captures |
|---|
| Entry points | Every way a user arrives at the task - navigation, email link, notification, search |
|---|
| Happy path | The shortest successful route |
|---|
| Decision points | Where the user or system chooses between branches |
|---|
| System steps | Validation, automated checks, integrations and their timings |
|---|
| Error and recovery paths | What can go wrong at each step and how the user gets back on track |
|---|
| Waiting states | Where the task pauses, for how long and what the user sees meanwhile |
|---|
| Handoffs | Where work passes to another role, and how both sides know |
|---|
| Exit points | Saving and returning, cancelling, and what's preserved |
|---|
Status: the part of flows most products get wrong
Any flow that pauses or involves more than one person needs a status model - a defined set of states, what each one means, the next step and who owns it. Without one, status becomes a collection of labels added feature by feature, and users stop trusting them.
On a healthcare credentialing platform, status clarity was central: states such as "Active" and "Verified" were defined once and communicated the same way across the product and beyond. The approach is covered in UX design for credentialing workflows. The same model applies to approvals, orders, applications, onboarding and support requests.
| State | Must answer |
|---|
| Every non-final state | What is happening now? What happens next? Who needs to act? By when? |
|---|
| Every error state | What went wrong? What can the user do? Is anything lost? |
|---|
| Every final state | Is this complete? What changed? Where can I see the record? |
|---|
Multi-role and multi-persona flows
Many B2B and healthcare tasks involve more than one person - a provider and a coordinator, a requester and an approver, a buyer and a sales engineer. Mapping each role's steps side by side (a swimlane view) exposes where work waits and where information is lost between them.
Different users also need different routes through the same task. On a B2B hospitality platform, three buyer types needed three different flows: a fast path for a decisive buyer, a guided path for a newcomer and a detail-first path for someone comparing specifications. See persona-led UX for B2B buyers.
