The engineer has finished the visit. The office manager is chasing the job sheet. Accounts has an invoice ready to raise, provided someone can explain which materials were used. Everyone has done something. The job is still waiting.
I'd put that journey on a swim lane diagram before discussing another app. Take a recent job, draw a lane for each role and follow the work across the page. Include the chasing, the missing information and the point where someone assumed their part was finished.
My starting question is simple: who has the next action, and how do they know?
What a swim lane diagram shows
A swim lane diagram puts the steps of a process into lanes representing the people or teams responsible. Arrows connect the steps. When an arrow crosses into another lane, you can see the transfer of responsibility. Microsoft's cross-functional flowchart guidance describes this relationship between process steps and the departments or positions carrying them out.
For a maintenance contractor, useful lanes might be customer, office, engineer, service manager and accounts. I'd label them by role so the discussion survives a change of staff. Where somebody covers several roles, mark that beside the lane heading.
Keep the first drawing plain. I'd use a box for an action, an arrow for the route and a diamond for a question with different routes for the answers. Microsoft's basic flowchart guidance explains process steps, decision outcomes and arrow directions. Agree the meaning of your shapes with the team.
You can start with paper and sticky notes. I'd save the choice of drawing software until the team agrees what actually happens. The useful output is a shared explanation of the job's journey, including the awkward bits.
Choose a journey with a clear finish
I would resist mapping the whole business in the first session. Choose a piece of work whose beginning and end everyone can recognise: an enquiry becoming an agreed quotation, a completed visit becoming an invoice, or a delivery note being matched to a purchase order.
For the example here, let's use an illustrative maintenance contractor. The scope starts when an engineer finishes a visit and ends when accounts has raised the invoice against the correct job. These are fictional roles and actions to show the method; they describe no Mise client or measured result.
Bring together the engineer, the office colleague who receives the record and the person who raises the invoice. Include the service manager if they approve extra work or resolve queries. Ask them to bring a recent job they can discuss internally, with its actual records.
Write the start and finish above the page. Keep a separate list for related problems outside that boundary. If the quotation process needs attention, capture it for another session rather than extending today's map back through every earlier conversation.
This is the kind of practical investigation I'd use in Assess: establish what is happening and where an improvement would be worth making.
Draw what happened, including the return journeys
Start with the engineer's final action on site. Ask what they recorded, where they recorded it and who received it. Follow the answer into the next lane. Use verbs on the boxes: “send job sheet”, “check materials”, “query missing reference”, “raise invoice”.
For our illustrative contractor, the initial route might read:
- Engineer records the work on a paper job sheet and sends photographs through WhatsApp.
- Office manager collects the sheet and finds the corresponding job record.
- Service manager checks whether the extra work was agreed.
- Office manager passes the checked details to accounts.
- Accounts raises the invoice in Xero.
Those steps are a starting sketch. I'd then ask the team to walk through the troublesome job. Perhaps the office receives the photographs before the sheet. Perhaps the materials description is unclear. Perhaps the manager sends a query back to the engineer, who is already at another site.
Draw those return arrows. Add a question where the route divides, such as “Are the details complete?” Show where an incomplete record goes and who picks it up again. Keep uncertainties visible with a question mark until somebody checks the record.
North London NHS Foundation Trust's process-mapping guidance recommends agreeing boundaries, involving the people concerned, drawing the current process and identifying improvements before mapping a future version. Its setting is healthcare; the exercise here applies that general method to a contractor's administrative handover.
Look closely at the arrows between roles
Once the team recognises the map, I'd examine each handover. Ask what the receiving person needs to continue, where they look for it and what tells them it has arrived.
In the fictional example, “send job details” is too vague for me. I'd want the team to agree the expected job reference, description of work, materials record and any unresolved question. Accounts should be able to explain which missing details prevent the next action.
Annotate each troublesome arrow with what happened on the job you traced. “Office chased engineer for materials description” gives you something to investigate. “Communication issue” leaves too much open to interpretation.
I'd also distinguish active work from waiting. Checking a record and waiting for somebody to notice it belong separately on the drawing. If you want to understand the delay, look at the job's actual timestamps and record any gaps in the evidence. Leave a duration unknown when nobody can establish it.
Be careful about blame. Ask what the process required the person to notice or remember. If the handover depends on an office manager checking several places, make that expectation explicit. Then decide whether it is a sensible way to run the work.
A useful map should let someone point to the exact place where progress stopped and explain what was needed to restart it.
Agree the smallest change worth testing
For the illustrative contractor, I'd begin with a proposal: put the visit record in an agreed place, give the office responsibility for checking completeness and define how missing information returns to the engineer. The service manager would retain a clear route for queries about extra work.
That is a suggested design to test. Your team may need a different route, particularly where the same person handles scheduling, checking and invoicing.
Draw the proposed process beside the current version. For each change, name the owner and the condition for passing work onwards. “Ready for accounts” should mean something the office and accounts can both check.
Then consider the technology. An existing job-management form might already capture what you need. You might need to adjust a status or agree a consistent reference. If you propose an integration, describe exactly which record it moves and who handles a failed transfer.
I'd leave AI out of this example unless a specific task earns it a place. The immediate design question is whether everyone can find the required information and recognise the next action. Our guide to business process automation takes that discussion further when a repeatable task is ready to automate.
Use the map to change a real handover
This week, pick a recently delayed job and put its journey on paper with the people who handled it. Ask them to correct the drawing. Choose a troublesome handover and agree a small trial, including who will check the outcome.
For that trial, I'd record when the visit record reaches the office, whether accounts receives it complete and what chasing is still required. Compare those observations with the original job, while being honest about differences between the jobs. Keep a note of exceptions so a smooth example cannot hide an unresolved route.
Return to the map after the trial. Update it to reflect what worked, what needed intervention and who now owns the ongoing check. A drawing that nobody revisits has limited value.
My test of a useful swim lane diagram is whether the team can use it to make the next job easier to finish. Give the handover an owner, make the required information clear and check that the work actually moves.
If you'd like help tracing a difficult handover in your business, we can talk it through.