Guide
How to Map a Workflow (Step by Step, No Software Needed)
Short answer
Pick one process, then write every step from the moment it starts to the moment it’s done, in order, on sticky notes or a list. Next to each step, note who does it and where the information lives. Then circle every hand-off, copy and wait. That’s your workflow map, and the circles are exactly what to fix or automate. It takes 30 to 60 minutes and no software.
What you need
Sticky notes and a wall, a whiteboard, or a blank page. If you’d rather draw it on a screen, the free tool draw.io works well. Most importantly, you need the person who actually does the work in the room.
The steps
- Pick one process. Choose something that repeats and annoys you: new customer inquiries, class registration, invoicing. One at a time.
- Name the trigger and the finish line. What starts it (“a customer requests a quote”) and what “done” means (“the deposit is paid and the job is on the calendar”).
- Walk it with the person who does it. Map how it really happens, not how you think it happens. The gaps between those two are often the whole story.
- Write each step as a verb and a thing. “Check email,” “copy details to spreadsheet,” “text customer a price.” One step per note.
- Add who and where. Mark who does each step and where the information lives: paper, email, a spreadsheet, someone’s head.
- Mark the decisions. Wherever the path splits (“is the job over 50 miles away?”), draw a diamond with the two answers.
- Circle the friction. Every time information is copied by hand, passed to another person, or waits on someone, circle it.
- Put a number on it. Estimate minutes per step and how often it runs. The paperwork cost calculator turns that into hours and dollars a year.
- Draw the better version. Redraw the map with the circles removed or automated. That’s your plan.
An example: a quote request
Here’s a real-world shape I see all the time at local service businesses:
| Step | Who | Where | Friction |
|---|---|---|---|
| Customer fills out the website form | Customer | Website | |
| Owner sees the email that evening | Owner | Wait: hours | |
| Owner copies details into a spreadsheet | Owner | Spreadsheet | Copy by hand |
| Owner texts the customer to set a visit | Owner | Phone | Back and forth |
| Owner adds the visit to the calendar | Owner | Calendar | Copy by hand |
Three circles. The better version: the form saves the lead automatically, the customer gets an instant text with a booking link, and the booking lands on the calendar. The owner’s only job is the visit.
Flowchart symbols, if you want them
- Oval: start or end.
- Rectangle: a step.
- Diamond: a decision with yes and no paths.
- Arrow: what happens next.
A swimlane map puts each person or department in its own row, so you can see every hand-off as an arrow crossing between rows. It’s worth it once three or more people touch the process.
My take
Map the information, not just the people. In GIS work the first thing I draw is where the data starts, every place it gets copied, and where it ends up. Business processes are the same. Every arrow where data is retyped is a chance for a typo and a few lost minutes, and those are the arrows automation removes.
Once your map is done, read what to automate first to decide which circle to tackle.
Questions, answered
How do you map a workflow?
Choose one process, list every step from trigger to finish in order, note who does each step and where the information lives, then circle the hand-offs, manual copying and waiting. The circles are what to improve.
What is a swimlane diagram?
A workflow map where each person or department gets its own row, so every hand-off shows up as an arrow crossing from one row to another.
What software can I use to map a workflow?
Sticky notes or a whiteboard work fine. For a digital version, free tools like draw.io handle flowcharts and swimlanes.
What do the flowchart shapes mean?
Ovals mark the start and end, rectangles are steps, diamonds are decisions with yes and no paths, and arrows show what happens next.