Back to Growing Pains

Structural Lock-In

Friction Is Margin

Somebody may be getting paid in the gap.

Friction is easy to hate when you are the one waiting. The form will not submit. The refund takes forever. The approval sits in somebody’s inbox. The customer has to call twice. From your side, it looks like a bad system.

From another side, the same friction may be revenue, control, headcount, risk cover, or billable hours. This is why it survives. The gap is not always a leak. Sometimes the gap is the store.

The Gap Sells

Some companies make money by removing friction. Others make money because friction remains. The same pattern shows up inside a business. Confusion creates coordinators. Delay creates escalation paths. Tool gaps create manual work. Manual work becomes budget. Budget becomes turf.

Once friction pays someone, simplification stops being a clean improvement. It becomes a threat to the small economy built around the pain.

The Hidden Price

The customer pays in time. Employees pay in attention. Suppliers pay in uncertainty. The company pays in slower learning. But the cost is scattered, while the benefit may be concentrated.

This is the trick. Everyone feels the drag, but one team may get the margin. Everyone complains about the process, but one role gets its authority from knowing the process better than anyone else.

The Money Map

Map friction like a cash flow. Who waits? Who explains? Who gets budget? Who gets authority? Who gets to say no because the gap still exists?

Then decide whether the friction is useful protection, accidental drag, or defended margin. Those are different problems. Treating them the same is why cleanup projects stall.

Questions to carry

The point is not to explain everything. It is to make the next conversation sharper.

The person payingCustomer, employee, supplier, partner, or the business itself.
The person gainingLook for budget, status, control, margin, or safety.
The result of removalThe reaction to simplification usually reveals the real business model.

Use it when

Use this read when a problem is too profitable to vanish on its own.