Friction

Definition #

[Friction] is the forces acting on your operation that keep any activity in it from being realized fully.

Not the shortfall. The shortfall is what the forces produce, and it is how you find them. Friction is what is doing the work: everything in you and around you resisting the activity while it is being performed.

It is the parent of a family. Every domain of the business carries its own set of these forces, with its own resistance and its own response, and each one that earns an entry sits under this term as [X Friction].

The resistance is always indirect. These forces act on your operation’s ability to perform, never on what is available to it. Any use of the word that turns a condition into a ceiling is not this term.

Mechanism #

Three things stand between an operation and what it could deliver, and only one of them is workable. There is what is possible at all, which nobody controls. There is capability, which develops slowly and deliberately. And there are the forces resisting the operation as it performs, holding it short of the capability it already has. That last set can be worked on tomorrow, which is why it is worth naming separately from the other two.

The shortfall is the instrument, not the thing. You cannot see a force directly. You see an activity coming out under what the operation is capable of, and you work backward to what was acting on it. That is why every diagnostic in this entry starts by measuring the shortfall and none of them stops there. An operator who names the shortfall and calls it the problem has described the symptom and left every force in place.

Every domain has its own. The read has friction. The design has friction. Marketing has friction. The cast has friction. What gets collected off a turn has friction. In each case the shape is the same and the specifics are different, which is why the family runs as separate entries rather than one general observation that there is drag everywhere.

Two kinds, in every domain. Friction you can feel is cost you have declined to pay. It leaves a mark you can find later, because you remember the question you did not ask or the build you decided against. Friction you cannot feel is a filter, and nobody experiences a filter from the inside. It returns a result that seems complete, so you stop, satisfied, well under what you were capable of. The second kind is the more expensive one everywhere it appears, and it responds to different work.

In you and around you. Some of the drag is yours: what it costs you in standing, capital, or being wrong in front of people who work for you, plus the fixed ideas you cannot see operating. Some of it is in the conditions: the volume of production leaving no attention, numbers arriving pre-interpreted, the trade vocabulary that pre-loads the question, turnover, advisors with an interest in you not asking, peers who confirm. All of it is drag and all of it is reducible. None of it is a limit on what is available to you.

Indirect, and why the whole family depends on it. The area, the rent, the labor market, the operation across the street do not make anything unavailable. They make the work harder. The moment friction is allowed to cap instead of drag, every excuse my work has spent years removing walks back in wearing this term, and the term becomes the most useful thing in the industry for an operator who does not want to look at himself.

It accumulates and it hardens. Filters form legitimately and then keep running after the conditions under them move. Costs that were once worth declining stay declined out of habit. Friction is a standing condition, so the work against it is recurring and never a one-time clearing.

Both Roads carry it, and the response is opposite. Road 1 capability is throughput, speed, cost, and conversion. That capability is method capability, method transfers, and so Road 1 friction is genuinely reducible by purchase. A transactional operation buying a better system is doing exactly the right thing. Road 2 capability rests on the read, the design, and the relationship, and no read transfers, so Road 2 friction is not reducible by any purchase at any price.

Which explains the vendor market better than anything else in my work. The instruments are not frauds. They work. They work on Road 1 friction. They are sold to Road 2 operators, who buy them, apply them correctly, and get nothing, because the drag they are carrying is on the one side no purchase reaches. The operator concludes he executed it wrong and buys the next one.

Load-Bearing Distinction #

Not the shortfall it produces. The distance between capability and delivery is the evidence. Friction is what put it there. Collapse the two and the work stops at measuring the distance, which every operation already does and which changes nothing, because no force has been named or reduced.

Not capability. Capability sets the ceiling. Friction holds the operation under it. An operation performing at its capability has no friction problem, whatever its capability is. An operation with deep capability delivering half of it has nothing but a friction problem, and that is the more common case by a wide margin.

Not a constraint. A constraint limits what is possible. Friction limits what gets delivered against what is already possible. Every condition an operator names as his constraint is either a condition to be read and designed to, or it is friction. Neither one is a limit on what is available.

Not effort. The felt kind is a rational refusal of a real cost. The unfelt kind is invisible to whoever is carrying it. Neither responds to working harder, which is exactly why operators who work harder against friction get nowhere and conclude they are not capable.

Not [Default Gravity]. Default gravity is an installed default overriding a ruling at execution. The ruling exists and gets overridden. Friction operates upstream of that, on whether the operation ever reaches the capability it has. Override, not drag.

Not the visibility family. [Visibility Trap], [Cover Blindness], and [Operator’s Visibility Problem] are all about the information — incomplete data producing certainty, reporting that hides the deciding variable, the attentional limit on what enters the read. Those are properties of what is in front of the operator. Friction is drag on the operation’s own capability, and it is still there when the information is perfect.

Not [Static Decline]. Static decline is a condition of the operator reading his operation as just enough while reservoirs deplete. Friction is a mechanism, present in operations that are growing and operations that are dying, and it is what static decline is often made of.

Not inefficiency. Inefficiency is waste inside a process that is running. Friction is why the process is running below what the operation could run it at, or why a better process never got designed at all.

Without this term, every shortfall in an operation gets explained one of two ways: not capable enough, or not trying hard enough. The first sends the operator shopping for somebody else’s capability. The second sends him into more hours doing the same things. Friction names the actual cause and it is the only one of the three he can reduce starting tomorrow.

Diagnostic Tests #

Test One — The Shortfall Statement. Pick any domain of the operation and state two things: what it is capable of, and what it is delivering. The distance between them is not the finding. It is the signal that something is acting on that domain, and it tells you where to go looking. If the two are the same, either the domain is at ceiling or something is telling you it is, and the second is more likely.

Test Two — The Declined Cost. In that domain, name what you have chosen not to pay. The question not asked, the build not committed to, the experiment not run, the conversation not had. Every item on that list is felt friction with a price already attached.

Test Three — The Untested Belief. Write five things you believe about that domain and have never tested. Each one is a filter running on every decision you make in it, and it is running whether it is still true or not.

Test Four — The Constraint Sentence. Say out loud what is limiting the operation. If the answer is the area, the rent, the labor market, the economy, the operation across the street, or the Guests, you have named a condition and called it a ceiling. Conditions get read and designed to. Friction gets reduced.

Test Five — The Road Test. Before buying an instrument, name whether the drag it addresses is Road 1 or Road 2. Throughput, speed, cost, conversion — the purchase can genuinely help. Read, design, relationship — no purchase reaches it, and the money will feel like progress for two quarters.

Test Six — The Category Sentence. Finish this out loud: an operation like mine cannot. Whatever comes out is a fixed idea operating as a fact, and it is drag in every domain at once.

Test Seven — The Confirmation Circle. List who you talk to about the operation. Count how many have told you that you were wrong in the last year. None means you have built a circle that adds drag and feels like support.

Test Eight — The Reserved Hours. Name the hours in your week that are neither production nor admin. If there are none, the operation is consuming the whole of your capability in running itself, and nothing gets worked on.

Test Nine — The Two Explanations Test. The last time something in the operation did not work, what did you conclude. If the answer was that you lacked ability or were not working hard enough, you skipped the cause. Go back and look for the drag.

Family Position #

Parent of the friction family. Sits inside Perspective, Operating Principles, because it is a read discipline about the operation itself rather than work inside any one domain. Children take the form [X Friction], one per domain that earns an entry.

Manifestation is the default and minting is the exception. Friction appears everywhere in an operation, and naming every appearance would produce a family of entries that all say the same thing about a different room. Most appearances are manifestations and belong in this entry as beats.

No child is named after a Fundamental. This entry is required to carry all five reads, so [Perspective Friction], [Product Friction], [People Friction], [Performance Friction], and [Profit Friction] would duplicate coverage the parent already holds and always will. None of them can exist.

Admission test for a child. Two conditions, both required. It has to cut across Fundamentals rather than sit inside one. And it has to carry drag and a response this entry does not already prescribe. [Read Friction] passes because the four read practices each carry a different drag and each takes a different response. A candidate whose only finding is that there is drag here too fails, and belongs as a beat above.

Perspective read. Friction on the read is the highest-leverage member of the family, because the read is upstream of every other decision the operation makes. Its four practices each carry their own drag. Reading is throttled by attention that production consumes and by filters that alter what comes back. Questioning costs standing, because the decisions being questioned have his name on them. Experimenting costs money and risks a night. Re-reading means finding out he was wrong in front of his cast. Detection is the unasked question and the untested belief, both of which any honest operator can produce in ten minutes. And this is where the indirect rule earns its keep: friction on the read never reduces the value available in the market, only how much of it he reads, which is why the response is always to reduce drag rather than to accept a smaller operation.

Product read. The gap here is between what the read supports and what actually got built. He saw it and built something smaller, because committing capital and standing to a build that is expensive to reverse is the most costly single act in the operation. Then a second drag sets in and it is protective: a Product he built is a Product he is invested in, so reading the market honestly risks the conclusion that the thing with his name on it no longer fits what is available. That is why operations defend builds instead of redesigning them, and why a Product keeps the shape it had when the read behind it was last current.

People read. Two drags running at once. Fixed ideas about what the cast can hold filter what he reads about them, so he designs around a ceiling he assigned rather than the one they have. And the cast is the widest read channel he owns, so friction in the room shuts it off — a lead who learns that carrying bad news up costs him stops carrying it, and quiet gets experienced as absence of problems. Turnover compounds both by emptying the channel each time it fills. Reducing friction in the cast is the cheapest capability gain available in any operation and almost nobody works it.

Performance read. The stage under load runs the highest friction in the operation, and it is structural rather than personal. Attention is fully consumed producing, so the richest material of the turn arrives at the exact moment there is least capacity to collect it. That does not get solved by resolving to notice more. It gets solved by building the collection into the turn as its own work, after lockup while the night is still recoverable, and by putting it on people who were not carrying the entire load themselves.

Profit read. Numbers that arrive pre-interpreted are friction dressed as information: a platform or a vendor chose what gets measured, so the question was answered before the report opened. Past that, the money carries the heaviest felt drag in the operation, because reading the architecture honestly can produce a conclusion that a position defended for years does not work, and that conclusion gets paid for in public. So the ledgers get read for confirmation instead of for what they say, which is how an operation sits in range on every line for years while nothing compounds.

Cross-References To Locked IP #

Children:

• [Read Friction] — drag between the operator’s abilities and his actual read

Manifestations held in this entry:

• Drag on any single Fundamental, all five of which are carried in Family Position above
• Drag on collection, where a turn produces material and the operation takes nothing off it
• Drag on the cast, where capability exists and the operation does not let them hold it
• Drag on commitment, where the design exists and the trigger does not get pulled

Related:

• [Value Congruence] — what read friction holds below the operator’s ability
• [The Read] — the discipline the highest-leverage child operates on
• [The ReRead] — the practice friction suppresses most reliably
• [Question Dumb Shit] — the practice that works directly against unfelt friction
• [Uncertainty Capacity] — what an operator needs to pay felt friction deliberately
• [Operating Helix] — the loop that stalls when friction goes unworked
• [Two Roads] — the distinction that determines whether a purchase can reduce the drag
• [Constant Expiry] — why a filter that formed legitimately is now drag
• [No Static Achievement] — why the work against friction never finishes

Opposing patterns:

• [Default Gravity] — installed defaults overriding rulings downstream, in execution
• [Visibility Trap] — incomplete information producing certainty, a property of the information
• [Cover Blindness] — reporting that hides the deciding variable
• [Operator’s Visibility Problem] — the attentional limit on what enters the read at all
• [Sameness Machine] — the supply that appears to have done the work, removing the felt cost of doing it
• [Static Decline] — the operator condition friction is often made of
• [Repairman Syndrome] — the identity that keeps attention on returning to zero
• [Measurement Lock-In] — pre-interpreted numbers standing in for the operator’s own read
• [Million Dollar Mediocrity] — what an operation delivers when capability is high and friction is unworked

Why This Matters #

When an operation is not delivering, an operator has two explanations available and both are usually wrong. He is not capable enough, or he is not working hard enough. The first sends him out to buy somebody else’s capability. The second sends him into more hours doing the same things. Neither one describes what is happening, and both are expensive.

What is usually happening is that the capability is already there and something is holding the operation under it. Sometimes he knows and has decided not to pay. More often a fixed idea that formed years ago is filtering what he gets back, and the filtered result feels complete, so he stops.

That split is the whole value of the term, because the two kinds respond to completely different work. Felt friction gets priced and paid on purpose. Unfelt friction cannot be paid, because he does not know it is there, and it only comes out by testing things he has never tested. That is a different activity from trying harder at anything.

It also explains why two operators with the same tenure, the same skill, and the same market land in different places. Not talent. How much drag each one carries and how much he has cleared out of his own way.

And it settles what the instrument market is actually doing. The instruments work, on Road 1 friction, which is real and is genuinely reducible by purchase. Sold to a Road 2 operator, the same instrument is applied correctly and delivers nothing, because the drag he carries is on the side no purchase reaches. He concludes he implemented it wrong. That is the mechanism under every arbitrage argument in my work, stated from the operator’s side instead of the vendor’s.

Operating Consequence #

Refuse the two false explanations. When something is not working, the cause is not that you lack ability and not that you are not trying. Go looking for the drag before you go looking for an instrument or more hours.

Measure the shortfall, then go find what caused it. What is the domain capable of, what is it delivering. Naming those two separately is what makes the forces findable, because most operators only ever look at the second number. Then keep going, because the shortfall is evidence and not the thing you are working on.

Sort the drag into felt and unfelt before working on either. Felt gets priced and paid. Unfelt gets tested. Treating the second like the first produces an operator working harder against a filter he cannot see.

Price a declined cost and pay it on purpose. Pick the question you have been avoiding, the experiment you decided against, the conversation you have not had. Name what it costs first so the payment is a decision rather than an accident.

Test standing beliefs on a schedule. Not the decisions. The beliefs under them. Every untested one is running as a fact and every one that formed years ago is running on conditions that have moved.

Run the Road test before every purchase. Name whether the drag it addresses is throughput and cost, or read and design. If it is the second, the money will buy capability you already have.

Stop naming conditions as constraints. The rent, the area, the labor market, the Guests. Each one is either read material or drag. Neither is a ceiling, and calling it one ends the work.

Reserve hours that are not production and not admin. The operation will consume every hour you do not reserve, and capability nobody has time to use is capability you do not have.

Rebuild the circle. If nobody around you has told you that you were wrong this year, you have assembled drag that presents itself as support. Add someone with standing to do it.

Treat it as recurring. Filters form quietly and harden, and declined costs stay declined out of habit. The audit is standing work, not a clearing you do once.

What Changes Tomorrow #

Pick the domain of the operation that is furthest from what you know it could be. One domain. Then write two lines: what it is capable of, and what it delivered last period.

Under that, make two lists. The first is what you have declined to pay in that domain — the question, the build, the experiment, the conversation. The second is what you believe about that domain and have never tested.

Take the largest item on the first list and price it. What does asking that question actually cost you, in standing, in money, in a night of production. Then decide, out loud, whether the drag it is causing is worth more than the price. Most operators find the item they have been avoiding for a year costs less than one bad Friday.

Take the largest item on the second list and go find out whether it is still true. Ask your cast. Ask your Guests, in the specific. Run something small that watching will not tell you. Then set what comes back against what you believed.

Expect to find that the belief was true once. That is the normal result and it is the useful one, because it names a filter that formed for good reasons and then kept running after the conditions under it moved.

Then do the next domain. The capability is already in the building. What you are working on is the distance between it and what walks out the door, and that distance is entirely yours.