Back to Friction Patterns
GPI DIMENSION: ERROR CORRECTION • STRUCTURAL LOCK-IN

THE FRICTION
LOOP.

Recursive friction patterns. When systems optimize for their own dysfunction and accelerate toward particle state.

QUICK ANSWER

The Friction Loop is a system state where friction becomes the optimization target. The organization unconsciously perfects its dysfunction, creating elegant mechanisms for consistent friction. Each iteration makes particle state more stable.

TL;DR

  • Friction loops = systems that perfect their own dysfunction
  • Particle state becomes the hidden goal
  • Improvements can make things worse
  • Breaking requires system shock, not iteration

ANATOMY OF THE FRICTION LOOP

STAGE 1: INITIAL FRICTION

A system creates friction. Normal response: add processes to prevent recurrence. But the cure contains seeds of deeper particle state.

Signal: "We need better processes"
Reality: Process becomes Decision Latency

STAGE 2: FRICTION OPTIMIZATION

The system starts optimizing around the friction. Workarounds become standard. Exception handling becomes the rule. Dysfunction gets infrastructure.

Signal: "That's just how we do things"
Reality: Friction becomes Structural Lock-In

STAGE 3: RECURSIVE LOCK

Success now depends on dysfunction. Remove the friction pattern and the system collapses. People's jobs exist to manage problems that shouldn't exist.

Signal: "We can't change that—everything depends on it"
Reality: Friction becomes load-bearing

STAGE 4: TERMINAL PARTICLE STATE

The system achieves maximum efficiency at creating friction. Every improvement makes friction more reliable. Success metrics measure dysfunction optimization.

Signal: "Our failure rate is very consistent"
Reality: Friction becomes excellence (GPI 9-10)

FRICTION LOOPS IN THE WILD

CORPORATE FRICTION LOOPS

  • • Meetings to plan meetings (Decision Latency)
  • • Reports on why reports aren't done
  • • Hiring to fix hiring problems (Talent Flow)
  • • Process to manage process debt
  • • Innovation committees that prevent innovation

STARTUP FRICTION LOOPS

  • • Pivoting from pivots (Knowledge Velocity)
  • • Growth hacks that prevent growth
  • • Features to fix feature bloat
  • • Fundraising to fund fundraising (Capital Intensity)
  • • Scaling problems before product-market fit

CLASSIC FRICTION LOOP CASE

Company X had slow deployments. They added approval processes. Deployments got slower. They added automation to speed up approvals. This created more edge cases needing more approvals.

Five years later: 47-step deployment process. 11 full-time employees managing deployment. Average deployment time: 6 weeks.

The Friction Loop: They optimized the approval process instead of questioning why deployments needed approval. GPI: 9.2 (Structural Lock-In).

BREAKING FRICTION LOOPS

RULE 1

Never Optimize Friction

If it shouldn't exist, don't make it better. Delete it. Move toward field state.

RULE 2

Trace to Origin

Find the first friction point. Everything else is recursion.

RULE 3

Shock the System

Gradual change strengthens friction loops. Only disruption breaks them.

RULE 4

Accept Temporary Chaos

Breaking friction loops creates mess. That's proof Error Correction is working.

CRITICAL WARNING

Friction loops defend themselves. They'll convince you that dysfunction is necessary, that particle state is actually field state, that the problem is the solution. The moment you start optimizing the friction, you've lost.

FRICTION LOOP DIAGNOSTIC

DETECT YOUR FRICTION LOOP LEVEL

4 targeted questions to measure your exposure to friction loop.

Takes 60 seconds. No data stored.

BREAK YOUR FRICTION LOOPS

Stop perfecting dysfunction. Start moving toward field state.