Particle State can come from real weight: regulation, safety, capital, risk, or a business model built around stability.
The danger is mismatch. A heavy business can survive in slow terrain. It gets exposed when the world starts asking for speed, learning, or a cleaner customer experience.
The Read
In Particle State, the company has weight. Sometimes the weight is a moat. Sometimes the weight keeps the company from updating what it already knows.
Scale
Read the low end and high end as field position. The live pressure decides what the score means.
| Score 1-3 | The business has enough shared context, agency, and flexibility to move without turning every change into a campaign. |
| Score 4-6 | The system is mixed. Some movement is still possible, but legacy structure, incentives, or assets are starting to set the pace. |
| Score 7-10 | Decisions travel up and down. Knowledge sits in silos or veterans. Errors stay alive until they become expensive enough to force action. |
| Watch for | Friction can become identity. The business protects the process even when the process is the problem. |
Signals
The tells you would expect to see when the read is close.
A small change requires multiple committees, approvals, or budget cycles.
Nobody knows the real workflow except the people who have been there for years.
Customers tolerate pain because switching costs are worse.
The company treats delay as normal, then builds reporting around the delay.
Builders leave; survivors stay.
The most profitable part of the model may be the gap, not the value creation.
Tape
Company tape gives the pattern something real to push against.
| Epic Systems | Deep healthcare lock-in where switching costs can exceed the pain of staying. |
| Higher Education | Credential moats, tenure systems, accreditation, and institutional habits slow operating change. |
| Government | Some friction is constitutional and intentional; the read depends heavily on terrain and mandate. |
| Boeing | Safety, supplier, production, finance, and culture failures compounded across a very heavy system. |
Use Today
How the read turns into a map, packet, or decision people can use.
| Name the weight | Separate useful stability from dead process. |
| Find the first release | Look for the smallest move reducing lock-in or exposing hidden delay. |
| Respect the risk | Match the move to what the system can absorb. |