People hear "audit" and they tense up. It sounds like something where someone in a suit comes in, judges everything you're doing wrong, and hands you a 90-page report full of jargon.
That's not what this is.
A friction audit is more like having a mechanic ride along while you drive. They're not telling you you're a bad driver. They're listening for the rattle, feeling for the pull to one side, noticing the hesitation when you accelerate. Then they tell you what's causing it and what it would take to fix.
What we're actually looking at
When I do a friction audit, I'm looking at how work moves through your business. Not in theory. In practice. There's usually a meaningful gap between those two things.
The process starts with conversation. I talk to you about what's working and what isn't. Where do you feel the drag? What takes longer than it should? Where do things fall through cracks? You know more than you think you do about where the problems are. You just haven't had a reason to articulate it all in one sitting.
Then I talk to your team. Individually, not in a group setting. People say different things when the boss isn't in the room. Not because they're hiding things, but because the friction they experience is different from the friction you experience. They see the parts of the system that you don't touch daily.
Then I watch. I look at how a project moves from start to finish. I follow the trail. Where does information live? How do handoffs happen? Where do things stall, and why?
What patterns usually emerge
Every business is different, but certain patterns show up with remarkable consistency.
The invisible queue. Work is waiting somewhere, and nobody realizes how long it waits. An approval that sits for two days. A piece of information that needs to be gathered from three different places before the next step can start. The work isn't hard. It's just stuck.
The oral tradition. Critical knowledge exists only in someone's head. How to handle a specific type of customer request. What the process is for onboarding a new vendor. The login credentials for the system nobody uses often but everyone needs occasionally. Nothing is written down, so every time someone new needs to learn it, it requires a live human to teach them.
The workaround that became the process. Someone figured out a clever way around a broken system three years ago, and now everyone does it that way, and nobody remembers that it started as a temporary fix. These workarounds work, technically. But they add steps, create confusion for new people, and often introduce their own new friction.
The meeting that compensates for something. A recurring meeting exists because information doesn't flow naturally. Take away the meeting and people feel lost, but the meeting itself is just patching over a structural gap. The fix isn't a better meeting. It's better information flow.
The bottleneck nobody names. There's a person or a step that everything depends on, and it's slowing everything down, but nobody talks about it because it feels too sensitive or too fundamental to change. Sometimes that person is the owner. Sometimes it's a team lead. Sometimes it's a specific piece of software.
What the deliverable looks like
At the end of a friction audit, you get something you can actually use. Not a generic report. A document that maps your specific friction points, explains why they exist, and recommends concrete changes.
It typically includes a current-state flow map showing how work actually moves today. Not how you think it moves or how you wish it moved. How it actually moves, based on what I observed and what your team described.
It includes a prioritized list of friction points, ranked by impact. Some friction is annoying but minor. Some friction is costing you real time, money, or quality. Knowing which is which matters because you can't fix everything at once, and you shouldn't try.
And it includes recommended changes for each friction point, with a rough sense of effort and timeline. Quick wins that you could implement this week. Medium-term changes that require some redesign. Longer-term structural shifts that need planning.
What it doesn't include
I'm not going to pretend a friction audit gives you everything. It doesn't.
It doesn't give you a detailed implementation plan. That's a separate step, and it requires more depth than an audit provides. If you want to see what implementation looks like, the post on 90-day improvement plans covers that.
It doesn't give you specific tool recommendations, usually. Tools matter, but they matter a lot less than process. I've seen businesses with perfect tools and terrible flow, and businesses with a shared Google Sheet that runs like clockwork.
And it doesn't fix anything on its own. It's a diagnostic, not a treatment. The value is in seeing clearly. What you do with that clarity is up to you.
Why an outside perspective helps
You might be wondering why you can't just do this yourself. And honestly, you could do some of it. The five friction points post gives you a starting point for self-assessment.
But there's a reason mechanics don't work on their own cars. Well, they do, but you know what I mean. When you're inside the system, you can't see the system. Your workarounds feel normal. Your bottlenecks feel inevitable. Your blind spots are, by definition, things you can't see.
An outside observer asks the dumb questions. "Why does this step exist?" "What happens if you skip this?" "Who decided it had to work this way?" Those questions feel obvious once someone asks them, but they're surprisingly hard to ask yourself.
Is this right for you
A friction audit makes sense when you feel like things could be working better but you're not sure where to start. When you've tried to fix things piecemeal and it hasn't stuck. When you want clarity before you commit to a bigger engagement.
If you're curious whether this would be useful for your business, the Flow Check is a free, no-pressure conversation where we figure that out together. Sometimes the answer is "yes, let's do an audit." Sometimes the answer is "here's one thing you can try on your own first." Either way, you'll leave with something useful.