
Last updated: November 3, 2026
Business process mapping (BPM) is the practice of drawing how work actually moves through your business, step by step. A good map shows you where things stall, who owns what, and what to fix first. Below: the main map types (BPMN included), a worked purchase-request map, the tools that draw them, and how to act on what you find.
A customer order comes in. Sales logs it, then waits on finance to approve credit, then the warehouse waits on sales to confirm, and somewhere in there nobody's quite sure who tells the customer it shipped. Two days vanish. Nobody designed it to work that way.
It just grew.
That's the thing about business processes. Most of them were never designed at all. They accreted, one workaround at a time, until the people running them couldn't draw you the steps if you asked. Business process mapping (BPM) is how you get them back on paper, where you can actually see them.
This guide covers what a process map shows you, the main types worth knowing, a worked example you can copy, the tools that draw them, and how to turn a finished map into a change your team actually feels. No notation degree required.
Business process mapping is the practice of drawing a business process as a step-by-step diagram that shows each task, who owns it, and every hand-off between people or teams. Once the work is on one page, the delays and gaps stop hiding.
The finished map is a flowchart of the process as it actually runs. Managers use it to find bottlenecks, train new hires faster, and decide what to fix first.
Business process mapping: drawing out how work really moves through an organization, step by step, including the detours, the handoffs, and the approval step everyone forgets. The map records the process as it runs rather than as the policy document describes it, which is what makes the wasted days visible.
Each box is a task. Each arrow is a handoff. Line them up and the gaps show themselves: the step where work sits in an inbox for a day, the decision nobody owns, the rework loop where things bounce between two teams.
You can draw one for almost anything. Onboarding a new hire. Closing the monthly books. Getting a blog post from draft to published. The diagram isn't the point. The point is that once it's on paper, you can argue about it with facts instead of vibes.
The tool matters less than one rule: the map has to be clear enough that someone outside the process can follow it.
You'll also see it called business mapping, process mapping, or BPM process mapping. Same practice, different labels.
Here's the honest answer. Most of the time, nobody actually knows how the work works. Ask three people on the same team to describe the same process and you'll get three versions, all of them a little bit wrong.
Mapping fixes that. It gives everyone one shared picture, which turns out to be useful in more ways than "we made a flowchart." A few of the payoffs:
Every bottleneck a map clears hands time back to the people inside the process. To make that time count, our guide to being more productive at work without longer hours covers the daily habits that keep it from leaking away again.
None of this needs a transformation initiative or a consultant with a deck. It needs one map and the willingness to look at it honestly.
Read more on why team leaders should embrace asynchronous collaboration for their distributed teams.
There's no single "right" map. Different shapes answer different questions, and picking the wrong one is how you end up with a diagram nobody opens twice. Here's a quick comparison before we get into each.
| Map type | What it shows | Best for |
|---|---|---|
| Workflow diagram | The tasks and activities in a process, manual and automated | A first, plain-language picture of how something gets done |
| Data flow diagram | How information moves between systems and people | Spotting duplicated data, errors, and broken handoffs |
| Process flow diagram | The steps plus the dependencies between them | Complex processes with many moving parts |
| Swimlane diagram | Who owns each step, sorted by role or department | Cross-team work where "whose job is this?" keeps coming up |
| Event-driven process chain | How triggers and events kick off each next step | Processes that wait on outside input or decisions |
| Business process model | A process's structure and how it leans on other processes | The big-picture view across connected workflows |
| BPMN diagram | Any of the above drawn in the standard BPMN shape set | Maps that analysts, IT and operations must all read the same way |
Workflow diagrams show the tasks that make up a process, both the manual ones and the automated ones. They're the friendliest place to start because anyone can read them without training. If you only ever make one kind of map, make this one.
Data flow diagrams follow the information, not the tasks. They trace how data moves between systems, teams, and steps, which makes them the fastest way to catch the same number being typed into three different tools. If your problem smells like "the report doesn't match the dashboard," start here.
Process flow diagrams show the steps and the dependencies between them. They shine on complicated work with lots of branches, where one delayed step quietly holds up four others. This is the map you reach for when a process feels slow but nobody can say exactly where.
Swimlane diagrams sort every step into a lane by role or department, so ownership stops being a mystery. They're the cure for the handoff that falls through the crack between two teams, each assuming the other had it.
Read more on how to use Kanban swimlanes for better project management.
Event-driven process chains map how a trigger sets off the next run of tasks. They're built for processes that pause and wait, like a vendor reply or a manager's sign-off, and they make those waiting points easy to spot.
Business process models zoom out. They show a process's structure and how it depends on the other processes and systems around it, which is what you want when you're redesigning more than one workflow at once.
BPMN process mapping is drawing a process in Business Process Model and Notation, the industry-standard shape set for business processes. It was developed by the Business Process Management Initiative and is now maintained by the Object Management Group.
The core vocabulary is small:
Reach for BPMN when the map has to travel, say from operations to an IT team that will automate part of it. Everyone trained in the notation reads the same diagram the same way, which is the whole point of a standard.
The business process mapping methodology most teams need is five steps long, and none of them requires special software.
Take a process almost every company runs and almost nobody designed: buying something. A designer needs a new drawing tablet. Here's how that request moves today, mapped as it actually runs.
| Step | Who | What happens | How the work moves on |
|---|---|---|---|
| 1. Request | Designer | Emails the manager with the tablet, the price, and a vendor link | Email to the manager |
| 2. Approve | Manager | Reads the request and replies "approved" | The reply goes back to the designer only |
| 3. Forward | Designer | Forwards the approval to finance, once they notice it | A forwarded email, whenever it happens |
| 4. Budget check | Finance | Confirms the cost fits the team's budget line | Email to the office manager |
| 5. Order | Office manager | Places the order with the vendor | Email to the designer with a delivery date |
| 6. Receive | Designer | Confirms the tablet arrived | A chat message that closes the loop |
Read the last column top to bottom and step 3 jumps out. The manager's yes travels back to the designer, who then has to remember to pass it along to finance. Nobody owns that hand-off, so the request waits in an inbox until someone chases it.
Nobody did anything wrong here. The arrow from the manager to finance was simply never drawn, because nobody ever drew the process at all.
The redesign is one change. The manager's approval goes straight to finance, and the designer only reappears at the end to confirm delivery. Same people, same steps, minus one detour through an inbox.
A hand-off is the moment one person's work becomes someone else's. The five stages of a collaborative process show how to give each stage an owner and a clear finish, which is the same fix this purchase map needed.
A redesigned map only helps if the next request actually follows it. In Quire, the purchase becomes one parent task, "Purchase: drawing tablet," assigned to the designer and due the day they need it. Each step on the map becomes a subtask with one owner and a due date.
Finance doesn't wait for a forwarded email anymore. The budget check is already in their My Tasks list with their name on it, linked to the approval it depends on.
If someone drags a date so the budget check starts before the approval is due, the dependency line in Timeline turns red. You see the clash and adjust the dates yourself.
A project admin can also switch on a project setting that stops anyone from checking off a step whose predecessor is unfinished. Nobody orders the tablet before finance has signed off.
To see every stuck request at once, add the Blocked Tasks widget to a Dashboard. It shows each task waiting on a predecessor, plus who owns that predecessor. That's step 3 of the old map, now with a name next to it.
Task dependencies, Timeline view and Dashboard View are available on Professional plans and higher, and the Approval feature on Premium and Enterprise. Full details are on our pricing page.
Got a map of your own on paper? Start a free Quire project, add the process as one task, and give its first step an owner and a date before lunch.
A business process mapping tool is any app that turns your steps into a diagram people can read and share. Diagramming apps such as Lucidchart, Microsoft Visio, Miro and the free draw.io draw the map, and a project management tool such as Quire runs the redesigned process as owned, dated tasks.
The best tool is the one your team opens twice. What matters most is whether the map stays connected to the work it describes. If you're shortlisting a new platform for this, how to evaluate a PM tool without a 6-month trial covers how to test that before committing budget.
Here's how the popular options compare.
| Tool | Best at | How the map meets the work |
|---|---|---|
| Lucidchart, Microsoft Visio, Miro | Detailed diagrams, BPMN shapes included | The map is a shareable diagram you link from your task tool |
| draw.io (diagrams.net), bpmn.io | Free, browser-based BPMN drawing | The map is a diagram file you save and share |
| Asana, ClickUp, Monday.com | Running tasks and projects, with built-in automation | Mapped steps become tasks and automation rules |
| Notion | Flexible docs and databases | Process docs and embedded diagrams share a page with the team's notes |
| Jira | Engineering and issue workflows | Its workflow editor maps the statuses an issue moves through |
| Quire | Breaking work into a nested task tree | Each mapped step becomes an owned, dated subtask, with dependencies for the hand-offs |
A diagramming app is still the right call for a formal BPMN spec. But for everyday process work, the fewer places your map and tasks live, the longer it stays true. A few categories worth knowing:
On a budget, draw.io (also known as diagrams.net) and bpmn.io are free, browser-based tools that support BPMN notation without a license. Microsoft Visio handles simpler diagrams fine if your company already has it.
For a very first map, a whiteboard and a stack of sticky notes work too. Move it into software once the steps stop changing every time someone new joins the conversation.
Workflow notation is a lighter system for mapping workflows, created by the Workflow Management Coalition. It's common in workflow management systems and easier to pick up than full BPMN, a gentler on-ramp for teams new to mapping.
Tools like Lucidchart and Microsoft Visio are built for exactly this: drag a box, connect an arrow, done. They handle process and data flows equally well, and most people already half-know how to use them.
Here's where mapping stops being a poster on the wall (and yes, this is the part where the project management tool shows up).
When your process map lives in the same place as the actual tasks, the steps you mapped turn into work you can assign, schedule, and track. The diagram and the doing stay in sync, instead of the map going stale the day after you drew it.
That's where Quire fits. As the purchase example above shows, each mapped step becomes an owned, dated subtask and each hand-off a dependency, so the map your team drew is the list it works from.
If you're comparing platforms side by side, our project management software comparisons cover the main options. The shortlist keeps shifting too, and project management tools that speak MCP covers which ones now connect to AI assistants.
Read more on how task management software helps teams reach higher productivity.
A map you don't act on is just wall art. The good news is the path from finished diagram to better process is short, and it's the same six steps every time.
That last step is the one everyone skips, and it's the one that separates a real improvement from a temporary one.
Testing a change on a few real cases before rolling it out is a habit agile teams practice every sprint. See how remote teams put agile project management into practice.
Mapping looks simple, which is exactly why it goes sideways. Here are the mistakes that turn a useful map into a wasted afternoon.
That last one is the whole difference between a process you mapped and a process you improved.
Business process mapping isn't a corporate ritual. It's the act of getting your real workflow onto paper so you can see it, question it, and fix it.
When the map lives in the same place as the work, it stays honest. That's the case for running yours in Quire, where every step has an owner, a due date, and a visible hand-off to the next person.
It's drawing how a business actually operates, step by step, so managers and teams can see workflows, find bottlenecks, and improve them.
It gives everyone one shared, accurate picture of how work runs, which makes onboarding, decisions, and process fixes far easier.
Workflow diagrams, data flow diagrams, process flow diagrams, swimlane diagrams, event-driven process chains, and business process models. Each answers a different question.
Drawing a process in Business Process Model and Notation, the standard shape set for events, tasks, gateways and flows, so every team reads the map the same way.
BPMN and workflow notation, flowcharting tools like Visio and Lucidchart, and project management software like Quire that ties the map to real tasks.
Make each mapped step a subtask with one owner and a due date, then link the hand-offs with Finish-to-Start task dependencies so the next owner's step is tied to the one before it.
Define the problem, find the steps causing it, change the process, test it, roll it out, then keep monitoring so the fix holds.
A first draft of one well-scoped process usually comes together in a single sitting with the people who run it. Most of the effort is the conversation about how work really happens, then a few passes to catch missed steps.