There's a reason the San Lorenzo River runs through Santa Cruz the way it does. Not because anyone designed it. Not because of a single storm. Because water, left alone long enough, finds the easiest path and keeps taking it until the rock gives way.
Your team does the same thing.
They are not waking up trying to wreck your process. When your official workflow is slow or unclear, they route around it. When the approval chain has five people in it, they shortcut through Slack. When the CRM is a pain, they keep the real client list in a notebook on their desk.
That is not defiance. That is physics. Work flows toward the path of least resistance whether you designed one or not.
The real question for your business
Most of the change efforts I see in small businesses fail because they ignore this. The owner reads a book, runs a training, writes a new SOP, and then wonders why things snap back within a month. They have not changed the terrain. They just asked the water to flow uphill.
When I run a friction audit for a Santa Cruz business, I am not really looking at the org chart. I am looking for where the water is actually going. Where decisions really get made. Where information really lives. Which workarounds the team has built because the official way is too slow.
Those informal paths tell you everything. They are the map of where your real operation exists, as opposed to the one you hope exists.
Good flow looks like this
When your channels are designed well, work moves. Information reaches the person who needs it without someone manually routing it. Decisions happen at the right level without getting kicked upstairs. Processes are written down, so a new hire does not need to shadow someone for a month to learn them. Feedback loops are short enough that problems surface before they compound.
That is intentional flow. It takes effort to build. But once it is there, it sustains itself, like an irrigation canal that delivers water season after season without anyone pushing it.
Bad flow looks like this
And here is the other side. When flow has no channel, it goes everywhere and erodes everything.
Information spreads through side conversations instead of documented updates. Decisions get made in Slack DMs, leaving half the team out of the loop. Work bypasses the official process because "it is faster this way." Problems do not surface until a client complains. People do whatever feels easiest in the moment, which creates chaos two steps downstream.
Here is the pattern. A formal approval process is too slow, so the team invents a "quick Slack approval" shortcut. It works until someone approves the wrong thing. Then another. Eventually a client gets the wrong deliverable. The workaround carved a new path, but the path had no guardrails, no documentation, no way to audit what happened. The short-term relief created long-term damage.
The workaround is not the problem. The workaround is the symptom. The real problem is an approval process slower than the work it is gating.
Why canyons beat bulldozers
Here is the thing about canyons. They were not carved by a single flood. They were carved by a small amount of water, moving in the same direction, every day, for a long time.
Organizational change works the same way. One big training session will not fix culture. One all-hands meeting will not clarify strategy. One process overhaul will not eliminate friction. What actually works is small, consistent changes in the same direction, repeated long enough that the new way becomes the easy way.
In practice:
A 20-minute weekly team check-in beats a quarterly offsite for alignment. The offsite gives you one moment of clarity. The weekly check-in gives you a reliable channel for information, blockers, and priorities. Over six months, the weekly wins by a mile.
A habit of spending 15 minutes after each project writing down what worked and what did not beats a 200-page operations manual. The manual will not get read. The living notes will get referenced every week.
Fixing one broken process and giving it four weeks to settle beats blowing up three at once. This is basic Kaizen, the Toyota-derived idea that small continuous improvements compound in ways that big reorgs never do. The Andon cord that lets any worker stop the line when something is wrong is not a dramatic intervention. It is a quiet, repeated signal. That is what reshapes the terrain.
Design channels. Do not fight gravity.
The mistake I see most often is leaders trying to force behavior uphill. "People should follow the process." "They should use the project management tool." "They should escalate issues instead of solving them themselves." All of this might be true. And all of it fights human nature, which is why it fails.
A better move is to look at what your team is actually doing and ask whether the official channel is the path of least resistance or the path of most resistance.
If the team is not using the project management tool, it is probably because it is too complicated for what you actually need. Simplify it. Or accept that a shared doc and a Slack channel is the real workflow, and treat that as the system.
If decisions are slow because they need five approvals, the problem is not that people are impatient. The problem is that you have not defined decision rights. A simple RACI matrix, who is responsible, accountable, consulted, informed, removes most of the "can you just check this with me" bottleneck.
If important updates are spreading through hallway conversations instead of your weekly email, the update format is probably wrong. Make it a three-bullet Slack post instead of a meeting, and the hallway channel becomes less useful.
You are not fighting gravity. You are building aqueducts.
The two questions to ask about your business
Look at your business this week and sit with two questions.
Where is the current actually going? Not where your org chart says it goes. Not where the SOP says it goes. Where is it really going. Where do decisions get made. Where does information live. What workarounds has your team built because the official way is too slow.
And then, are you channeling that current or is it eroding you? If it flows through documented, intentional channels, you are fine. That is life-giving flow. If it is carving its own unpredictable paths, you are losing knowledge every time someone leaves, and quality is sliding in ways you cannot see yet.
The fix is not to build a dam. The fix is to design a better channel.
Start with one
You do not need to redesign your whole operation this quarter. Pick one force that is currently eroding instead of nourishing. Decision-making in side channels. Knowledge trapped in one person's head. Work that skips the documented process.
Pick one. Build an intentional channel for that one. Make the new way actually easier than the old way, not just officially preferred. Then watch how fast the current shifts to follow it.
That is not theory. That is the same principle that carved the Grand Canyon. Small, consistent, directional movement. Rock becomes canyon. Chaos becomes flow.
If you want an outside eye on where the current is actually going in your business, a Flow Check is the simplest way to start. Two weeks, a clear map of where things are getting stuck, and a plan for the first channel to build.