M360 Compass · Management insights
Process mapping for small teams with busy handoffs

Process mapping means following one real request from start to finish so you can see where work changes hands, waits or loops back. To improve a workflow in a small team, pick one handoff and agree on what the receiving person needs before they can act.
Choose a recent request that made someone say, “I thought we had already sent that.” Ask two people who worked on it to walk through the file with you. A completed request gives you timestamps, messages and actions you can examine together. It is a useful starting point when different teams rely on different tools or habits.
Where should a small team start with process mapping?
Set a start and finish everyone can describe. In a service company, the map might start when a customer asks for a visit and end when the customer receives a confirmed time slot. The visit itself belongs to another workflow. That boundary lets you focus on the people who collect the details, check availability and confirm the date.
Use a verb and a role for each step you observed. At each transfer, record what the next person receives and what they can do with it. Add a simple question where the work can take two paths. For instance, do we have enough information about the address to offer a time slot? Map both answers and show who acts next. The Institute for Healthcare Improvement uses flowcharts to show how work currently takes place and to find delays and loops. Its tool comes from healthcare improvement. The practice of mapping one real request transfers to a small service business. Institute for Healthcare Improvement, Flowchart
What needs to travel with the request?
The table follows a fictional service request. Use its three columns to identify what each person should receive and what they can do once it arrives.
| Handoff | What travels | Next action |
|---|---|---|
| Intake → dispatch | Address and preferred time | Check availability |
| Dispatch → intake | Available time slot | Contact the customer |
| Intake → customer | Confirmed visit | Arrange access |
Ask both sides of a handoff to read the map. The sender explains what they pass along. The receiver checks whether that gives them enough to act. Invite the people who do the work to point out missing steps and describe what they actually receive. The Canadian Digital Service describes service design as a collaborative practice that represents related actions in sequence. Canadian Digital Service, Service design at CDS
If the map raises a question about who makes a decision, use a RACI matrix to work out who owns it and who contributes. The process map can stay focused on the path of the request. RACI matrix guide for small businesses
Agree on how the receiver will acknowledge the handoff. In a shared inbox, several people may see a request while each assumes someone else will handle it. Ask dispatch to show who is looking at the request and when intake can expect a reply. If the file already has a status that does this, check that both teams interpret it the same way and know when it should change.
Where does the work wait?
Add two timestamps at the handoff you are investigating. Record when the work reached the next person and when they could begin. A delay might reflect a queue, a missing detail or an approval with an uncertain turnaround. Ask what information would distinguish those causes. A timestamped note in a file may be enough to show that someone sent the work back for a missing detail.
Fictional example. A property maintenance business gets a request on Monday morning. Intake sends it to dispatch at 10 a.m. At 11 a.m., the dispatcher returns the request because the property has two entrances and the file does not say which one the technician should use. Intake gets the detail on Tuesday morning. The map shows a return trip that never appeared in the appointment calendar. The team checks two more recent requests to see whether the same question came up.
One example gives the team a place to investigate. Ask each person what they knew at the time and when they could act. That conversation helps the group see whether the delay starts at intake, at a later step or at a handoff that works differently depending on the request.
How can the team test one change?
Try a rule on the next small batch of requests. In the example, intake asks the customer which entrance to use before passing along a request for a building with more than one entrance. If the customer needs time to find out, intake records the open question and arranges a call back. The team agrees on who will make the call and where the answer belongs.
Pick a signal before the trial. Count how many requests for buildings with multiple entrances are sent back for address details. Also examine a case where the new question makes the first call longer. The count and the observation capture different effects of the change. With a small batch, use those facts to decide whether to continue the trial for another week. Guide to choosing useful HR metrics
How do you keep the roles and the trial visible?
Record which role receives the request and what that role owns. M360 RoleAlign documents roles and responsibilities and helps teams identify areas that need clarification. The map can show the steps and loops while the role record gives someone taking over the work a place to check what they own. M360 RoleAlign
M360 Momentum lets the team record an issue, the decision to run a trial, the person responsible and the due date. Put the review on a shared agenda and bring requests that show what happened when the rule changed. Bring a real handoff if you would like to see how the platform connects these parts of the work. M360 Momentum · Request a M360 Compass demo
Frequently asked questions about process maps
How many steps should the first map show?
Start with the steps needed to follow a request from beginning to end. Add detail at the point where a choice, delay or return changes what happens next.
Do we need dedicated mapping software?
Paper or a few cards will work for the first request. Keep the agreed map somewhere the people involved can find it and choose a date to check whether it still reflects their work.
How should we show exceptions?
Add a branch when an exception recurs or stops the work from moving. Show what triggers the branch, who acts and where the request returns to the main path.
Who should keep the map up to date?
Ask the person coordinating the workflow to keep it current. When a handoff changes, have the sender and receiver confirm the new path with that person.
