Free product template
Process map: as-is and to-be
A swimlane map with lanes per team, decisions with labelled outcomes and a validator; the today and the proposed process side by side.
It opens with this template loaded and runs in your browser. You don't need an account to use it; a free account saves your work and exports it.
The job it does
When a process spans teams and keeps failing at the handovers: map it as it is, then the change, before you write requirements. It comes with its own checks, so after you change it you can see at a glance that it still does the job.
What's inside
This is the template exactly as the Product & BA Lab opens it, read-only. Open it to run it, change it and export it.
- 1 document
- Exports as Markdown and CSV
A swimlane map of how the work runs today and how it should run: who does each step, where decisions are made, and where it can go wrong. Rename the lanes for your teams and redraw the steps.
- Every diagram passes the validator (no errors)
- “To-be” has the lanes “Customer”, “Mangrove app”, “Store staff”, each with a named task
As-is
Pools and lanes: Mangrove Market (Customer, Mangrove app, Store staff).
| # | Pool / lane | Type | Step | Next |
|---|---|---|---|---|
| 1 | Mangrove Market / Customer | Start | Order placed | step 2 |
| 2 | Mangrove Market / Mangrove app | Task | Send the order to the store | step 3 |
| 3 | Mangrove Market / Store staff | Task | Pick the items | step 4 |
| 4 | Mangrove Market / Store staff | Decision | All items in stock? | Yes: step 6; No: step 5 |
| 5 | Mangrove Market / Store staff | Task | Call the customer about a substitute | step 6 |
| 6 | Mangrove Market / Store staff | Task | Pack and label the order | step 7 |
| 7 | Mangrove Market / Mangrove app | Task | Send the “ready” message | step 8 |
| 8 | Mangrove Market / Customer | Task | Show the collection code | step 9 |
| 9 | Mangrove Market / Customer | End | Collected | finish |
To-be
Pools and lanes: Mangrove Market (Customer, Mangrove app, Store staff).
| # | Pool / lane | Type | Step | Next |
|---|---|---|---|---|
| 1 | Mangrove Market / Customer | Start | Order placed | step 2 |
| 2 | Mangrove Market / Mangrove app | Task | Send the order to the store | step 3 |
| 3 | Mangrove Market / Store staff | Task | Pick the items | step 4 |
| 4 | Mangrove Market / Store staff | Decision | All items in stock? | Yes: step 6; No: step 5 |
| 5 | Mangrove Market / Mangrove app | Task | Offer a substitute in the app | step 6 |
| 6 | Mangrove Market / Store staff | Task | Pack and label the order | step 7 |
| 7 | Mangrove Market / Mangrove app | Task | Send the “ready” message | step 8 |
| 8 | Mangrove Market / Customer | Task | Show the collection code | step 9 |
| 9 | Mangrove Market / Customer | End | Collected | finish |
The lesson behind it
Learn why it works, with a podcast and a quiz for each lesson.
More product templates
Backlog prioritisation (RICE and MoSCoW)
Reach, impact, confidence and effort for every item, a MoSCoW board, and why for every number.
Requirements traceability matrix
Requirements, user stories and test cases, linked, with every coverage gap highlighted.
PRD for a new feature
Problem with numbers, users, goals and non-goals, measurable metrics with a guardrail, user stories with acceptance criteria, scope, risks and launch.