More insights.
Subscribe to our newsletter.
Deep dives into design thinking, creative process, and the intersection of business and aesthetics.
If three people explain it differently, you have a problem
Ask three employees how a task gets completed, and there’s a good chance you’ll hear three slightly different versions of the same process. One person explains how it’s supposed to work. Another explains how it actually works. The third introduces a spreadsheet nobody else mentioned. None of them are necessarily wrong, which is precisely the problem.
Before businesses can improve a process, automate it, or scale it, they need to understand it. That’s where process mapping comes in. A process map provides a visual representation of how work moves through an organization, helping teams identify bottlenecks, duplicate effort, unnecessary approvals, and opportunities for improvement.
Step 1: Define the process
Before you start drawing boxes and arrows, decide exactly what you’re mapping. Be specific. “Customer onboarding” is a process. “Running the business” is not.
It’s also important to define the objective. What is the process supposed to achieve? What triggers it to begin? What outcome signals that it’s complete? Establishing clear boundaries will make the rest of the exercise much easier.
Step 2: Identify the start and end points
Every process has a beginning and an end. For example, a customer onboarding process might begin when a signed agreement is received and end when the customer is fully set up and ready to use your service.
This step sounds simple, but it often reveals misunderstandings. Team members may have different assumptions about where responsibilities begin and end. Clarifying these points helps everyone work from the same understanding.
Step 3: List every step
Now it’s time to document what actually happens. Resist the temptation to document the ideal process. Instead, capture reality.
Walk through the process step by step and involve the people who perform the work every day. They’re often the ones who know about the workarounds, exceptions, and unofficial steps that never appear in formal documentation. The goal isn’t perfection. The goal is accuracy.
Step 4: Identify decision points
Most business processes include decisions. Does the request require approval? Is additional information needed? Does the customer meet certain criteria?
These decision points are often where delays occur. Mapping them clearly helps businesses understand how work flows under different circumstances and where bottlenecks may exist.
Step 5: Assign responsibilities
A process becomes much easier to manage when everyone knows who owns each step.
As you build your process map, identify the person, team, or department responsible for every activity. This helps eliminate confusion, improve accountability, and reduce situations where tasks sit idle because nobody realizes they’re responsible.
Step 6: Look for bottlenecks
Once the process is visible, patterns start to emerge. Certain steps take longer than expected. Approvals create delays. Information gets entered multiple times. Employees spend time waiting instead of working.
This is often where the real value of process mapping appears. Many businesses discover inefficiencies they didn’t know existed simply because they’ve become part of the daily routine.
Step 7: Create the flowchart
Now that you understand the process, create a visual representation using a flowchart. It doesn’t need to be complicated. The goal is clarity, not artistic excellence.
If your flowchart looks like a conspiracy theory board from a detective movie, it may be time to simplify the process.
Step 8: Validate with the team
Before finalizing the map, review it with the people involved in the process. They’ll often identify missing steps, exceptions, or inaccuracies.
This review also creates alignment. Everyone leaves with the same understanding of how the process works, which is often valuable in itself.
Start simple
Many businesses delay process mapping because they believe it needs to be perfect. It doesn’t. A simple process map is far more valuable than a perfect process map that never gets created. Start with one important workflow, document it clearly, and improve it over time. Because once you can see how work actually gets done, improving it becomes much easier.
If three people explain it differently, you have a problem
Ask three employees how a task gets completed, and there’s a good chance you’ll hear three slightly different versions of the same process. One person explains how it’s supposed to work. Another explains how it actually works. The third introduces a spreadsheet nobody else mentioned. None of them are necessarily wrong, which is precisely the problem.
Before businesses can improve a process, automate it, or scale it, they need to understand it. That’s where process mapping comes in. A process map provides a visual representation of how work moves through an organization, helping teams identify bottlenecks, duplicate effort, unnecessary approvals, and opportunities for improvement.
Step 1: Define the process
Before you start drawing boxes and arrows, decide exactly what you’re mapping. Be specific. “Customer onboarding” is a process. “Running the business” is not.
It’s also important to define the objective. What is the process supposed to achieve? What triggers it to begin? What outcome signals that it’s complete? Establishing clear boundaries will make the rest of the exercise much easier.
Step 2: Identify the start and end points
Every process has a beginning and an end. For example, a customer onboarding process might begin when a signed agreement is received and end when the customer is fully set up and ready to use your service.
This step sounds simple, but it often reveals misunderstandings. Team members may have different assumptions about where responsibilities begin and end. Clarifying these points helps everyone work from the same understanding.
Step 3: List every step
Now it’s time to document what actually happens. Resist the temptation to document the ideal process. Instead, capture reality.
Walk through the process step by step and involve the people who perform the work every day. They’re often the ones who know about the workarounds, exceptions, and unofficial steps that never appear in formal documentation. The goal isn’t perfection. The goal is accuracy.
Step 4: Identify decision points
Most business processes include decisions. Does the request require approval? Is additional information needed? Does the customer meet certain criteria?
These decision points are often where delays occur. Mapping them clearly helps businesses understand how work flows under different circumstances and where bottlenecks may exist.
Step 5: Assign responsibilities
A process becomes much easier to manage when everyone knows who owns each step.
As you build your process map, identify the person, team, or department responsible for every activity. This helps eliminate confusion, improve accountability, and reduce situations where tasks sit idle because nobody realizes they’re responsible.
Step 6: Look for bottlenecks
Once the process is visible, patterns start to emerge. Certain steps take longer than expected. Approvals create delays. Information gets entered multiple times. Employees spend time waiting instead of working.
This is often where the real value of process mapping appears. Many businesses discover inefficiencies they didn’t know existed simply because they’ve become part of the daily routine.
Step 7: Create the flowchart
Now that you understand the process, create a visual representation using a flowchart. It doesn’t need to be complicated. The goal is clarity, not artistic excellence.
If your flowchart looks like a conspiracy theory board from a detective movie, it may be time to simplify the process.
Step 8: Validate with the team
Before finalizing the map, review it with the people involved in the process. They’ll often identify missing steps, exceptions, or inaccuracies.
This review also creates alignment. Everyone leaves with the same understanding of how the process works, which is often valuable in itself.
Start simple
Many businesses delay process mapping because they believe it needs to be perfect. It doesn’t. A simple process map is far more valuable than a perfect process map that never gets created. Start with one important workflow, document it clearly, and improve it over time. Because once you can see how work actually gets done, improving it becomes much easier.