For the longest time I treated friction like a bug. Something to find and remove. A team meeting that felt slow, a marriage conversation that kept circling, a schedule that didn’t quite fit, a part of my own head that wouldn’t agree with another part of my head. The reflex is so deep I didn’t notice I was doing it. You see something stuck, you try to unstick it. That’s just being a competent person, right?
It took me a while to notice that the things I was “fixing” were the things keeping the whole arrangement upright.
Two forces, both load-bearing.
Healthy systems run on opposed forces. Speed pulls against quality. Autonomy pulls against accountability. Exploration pulls against exploitation. Simplicity pulls against completeness. Pick any well-functioning operation and you’ll find a pair of forces tugging against each other, and the mistake is to assume one of them is the problem.
If your team feels slow under governance, the governance is doing its job. If your governance feels rushed by your team, the team is doing its job. The pull is the point. The minute you let either side win completely, the whole thing falls over. All-quality-no-speed is bureaucracy. All-speed-no-quality is chaos. You don’t want either of those.
I have watched founders try to “resolve” the tension between sales and product. They never resolve. The tension is the company. Same thing with parents trying to resolve the tension between structure and freedom with their kids. Same answer. The tension is the parenting.
The signal is in the discomfort.
Here’s the part that took me the longest to learn. When two important things are pulling against each other, the discomfort is signal, not noise. A team that’s never frustrated with governance has probably defanged the governance. A founder who’s never frustrated with their CFO has probably hired a yes-CFO. A marriage where one of you never feels mildly inconvenienced by the other has probably collapsed the tension into one person’s preferences. (Guess whose.)
The discomfort is the proof that both forces are still active. If it disappears, check which side won, because one of them did.
What changes when you see this.
A few things shift once you stop trying to remove friction by reflex. You stop apologizing for the parts of your system that produce healthy slowdown. You stop asking your COO to “get out of the way.” You stop trying to make every meeting feel productive (some of them are productive precisely because they don’t). You also stop blaming people for surfacing the tension. The person who keeps raising the quality concern when everyone else wants to ship faster is not the problem. They’re the system, talking.
The new question isn’t how do I remove the friction. It’s am I tuning the balance or collapsing it. Tuning is a thousand small adjustments forever. Collapsing is one big simplification that feels like progress for about a quarter, and then the bill arrives.
A note for anyone running anything.
If you’re in charge of a team, a venture, a household, a board, anything: count the productive tensions in it. Make a list. There are probably four or five. For each one, ask which side has been winning lately. Not which side is right. Which side has been winning. If one side has been winning for six months, the tension is collapsing, and the bill is on its way.
The work isn’t to pick the right side. The work is to keep both sides in the game. That’s the whole job, most days.