Organizational Flow · In context
Everyday friction
— the grit in the machinery
Organizational friction rarely looks like a crisis. It looks like an ordinary Tuesday: a question that waits, a meeting that coordinates, a form that tidies the queue without shortening it. None of these moments is dramatic on its own, and that is exactly why they survive. Here are the ones I meet most often, each with the mechanism behind it in Organizational Flow.
Read the list with one ordinary week in mind, and count how many of these you met in it.
The decision that waits for the next meeting
A small question needs a yes from a forum that meets once a month. The work waits nine days for a five-minute answer, and nobody thinks of it as waiting, because the meeting is in the calendar.
Decision latency · The Long Way to a Yes · Leading Without Deciding
The meeting that exists to coordinate
An hour a week where seven people check what everyone else is doing, so the work does not collide. It feels responsible. But the coordination is only needed because the boundaries between the teams sit in the wrong places. Where ownership and interfaces are clear, nobody has to check in, and the work can go on without asking.
Handoff loss · The Meter Was Always Running · The Team That Has to Ask
“Who owns this?”
Asked in a meeting, answered with a pause, then three different names. Nobody is being evasive. The thing was never given an owner, so people compensate around it, and the compensation becomes permanent.
Ownership clarity · A Meeting Grew Here · What a Capability Is, and Is Not
Information in the wrong place
The information we depend on is, in practice, owned by whichever team happens to run the system it is stored in. They do not know what it means to us, and yet they are both its source and its distributor. Every question about what a field means, and every change we need, goes through a team with no reason to understand it. The information has a keeper, but no owner.
Ownership clarity · Agreeing on What Things Mean · What a Capability Is, and Is Not
You have to know a guy
The way into an API, a function or a capability is a person rather than a door. There is no self-service. And once you have found it, the questions remain: how is it used, and what does what comes out of it actually mean? The answers usually take knowing one more person. All of it works well for whoever has the right numbers, and quietly stops working for everyone who joined after those people did.
Handoff loss · You Have to Know a Guy
Everyone left agreeing
The meeting ended well. A week later it turns out everyone left with a slightly different picture of what was agreed, and the same word meant three different things in three different rooms.
Handoff loss · Everyone Left Agreeing · Agreeing on What Things Mean
The detective work before anything starts
Every new initiative spends its first weeks finding out how things actually work today: which system holds what, who decides, why it is built the way it is. The findings are never kept, so the next initiative starts the investigation again.
Learning cycle time · The Detective Work at the Front of Everything
The rule that belongs to someone else
A requirement that exists for one part of the organization ends up applying to all of it. The access request that takes two weeks, the approval step on something that carries no risk, the template nobody in this team needs.
Decision latency · Everyone Carries the Strictest Requirement
The form that made the waiting tidier
Somebody noticed the queue and introduced a process for it. The queue is now numbered, tracked and reported on, and exactly as long as before.
Decision latency · An Interface Nobody Can Find · A Tollbooth on a Road With a Bypass
Everything was green
Every report on time, every status green. The team closed 52 tasks this sprint, and nobody can say what they did for a customer. Green is often simply the safest thing to report, because saying that something is not working costs more than letting it pass. But what nobody dares to say, nobody can learn from. A year later a great deal has been done, and nothing the organization can do is any better.
Learning cycle time · Everything Was Green · Nobody Writes Down the Cost of Not Trusting · We Have Solved This Before
“Let’s go back to what we usually do”
Something new is tried. It gets a little worse first, as it nearly always does when an old workaround is taken away, and someone says it seems like hard work. So everyone goes back. What the attempt taught goes with it, and the next time someone suggests the same thing there is already an answer: we tried that.
Learning cycle time · Tending What Grew · What Goes Wrong
“These things take time”
The sentence people say when they have stopped expecting anything to move faster. Friction shows up in how people sound long before it shows up in a number.
All four · It Shows Up in People First · The Wait Nobody Logged
The pattern behind the moments
Each of these is small enough to shrug off, which is why they are rarely fixed one by one. Together they are the four indicators the paper uses: whether people can name who owns a thing, how much context is lost at each handoff, how long decisions wait, and how long it takes before an outcome reaches whoever chose the work. Observing Organizations describes how to read them, and Reducing Friction describes the order in which to work on them.
The grit is not the problem itself. It is a symptom of what was never made clear: who owns a thing, who may decide, and what the words mean.