The Problem

Structure applied before there is enough constraint pressure to justify it. Tools and process scaffolding (insert multiple tools to coordinate here) deployed as preemptive scaffolding for work that doesn't yet exist in enough specificity to need scaffolding. Structure without tension is bureaucracy — it creates overhead without reducing uncertainty.

Physics Analogies

Electron Shells and Quantum Jumps

An electron doesn't move to a higher orbital gradually. It absorbs a specific quantum of energy and jumps. Below that threshold, nothing happens — the energy dissipates as heat.

Applying process tooling before the team has hit the specific pain that tooling solves means the energy dissipates. People comply without internalizing, or the tools go stale.

Phase Transitions

Water doesn't become steam at 99°C. The pressure has to reach a specific point. Teams are similar — you don't need a Trello board until you've actually lost track of something. You don't need a Figma file until two people are designing the same thing differently.

Goldilocks Zone / Stellar Equilibrium

Stars exist in equilibrium between gravitational pressure (collapse inward) and radiation pressure (expand outward). Too little gravity: a diffuse gas cloud — no structure. Too much: a black hole — all structure, no information escapes. A healthy team operates in the band between those extremes.

Agile Implications

The original agile insight was exactly this: process should emerge from pain, not precede it. "Responding to change over following a plan" is a statement about tension-responsiveness.

Pre-loaded structure:

1. Lacks specificity — generic scaffolding, not shaped by the actual contours of the work
2. Creates compliance burden — people maintain the system instead of doing the work
3. Masks real signals — when everything has a place, you can't feel where the actual pressure points are

The Just-in-Time Principle

Viable tension is the minimum constraint needed to prevent the system from flying apart, applied at the moment it's needed. Not before.

Related concepts:

• Kanban — "start with what you do now" — don't restructure, observe first
• Beer's Viable System Model — each level of recursion only intervenes when the level below can't self-regulate
• JIT manufacturing — inventory (process) is waste unless it's addressing actual throughput demand

Practical Frame

A useful question for a team:

What specific problem does each of these tools solve for us right now?

If we can't name the pain, maybe we stage the tool for later and keep things lighter until we hit that friction.

This turns a philosophical disagreement into an empirical question.

The instinct about what tools is probably right. The question is when — and the answer is: when the team feels the specific tension that tool resolves.