Every team accumulates friction it has stopped noticing — the report that takes a day because it's stitched from four systems, the approval that waits because one person is the only one who can give it. Mapping the work is how you make that friction visible again.
Why teams go blind to their own friction
Habituation. A workaround invented in a crisis becomes the process; the process becomes "how we do it"; and after a year no one remembers it was ever a workaround. The friction stops feeling like a problem. It starts feeling like the job — which is exactly why no one proposes fixing it.
Draw it, don't describe it
Get the people who actually do the work to draw the steps — every handoff, every wait, every "then I email Karen and hope she's in." On paper, the friction is obvious in a way it never is in conversation: the loops, the duplicate entry, the three approvals that could be one. Talking about a process flatters it; drawing it tells the truth.
Look especially for four things:
- Waiting — work sitting in someone's inbox is the most common and most invisible cost of all.
- Rework — anything done twice because it wasn't right, or wasn't clear, the first time.
- Handoffs — every transfer between people is a place where work stalls and context is lost.
- Hero dependencies — steps only one person can do, which become bottlenecks the moment they take a holiday.
Most teams don't have a productivity problem. They have a friction problem they've stopped being able to see.
Fix the waiting first
The instinct is to speed up the slow steps. Usually the bigger win is removing the waits between them. Work that takes two hours of effort can take two weeks of calendar time because of what happens in the gaps — the queue, the approval, the "I'll get to it tomorrow." Compress the gaps and the whole thing moves, often without anyone working a minute faster.
Make it a habit, not a project
Map one process a quarter — the one that generates the most complaints. You won't fix everything, and you shouldn't try. Fix the one wait, the one duplicate, the one hero dependency that costs the most, then move on to the next process next quarter. A standing habit beats a one-time transformation that no one maintains.
The goal isn't a perfect process. It's a team that can see its own friction again — because friction you can see is friction you can choose to remove.