4
15% weight

STRUCTURAL LOCK-IN.

How much the current structure constrains what's possible next. Not just technology. Org charts, vendor contracts, physical infrastructure, anything that makes changing direction expensive.

MODULARSWAP ANYTHINGVSENTANGLEDTOUCH ONE, BREAK FIVE

FLEXIBLE VS FROZEN

1510
FieldTransitionParticle

THE SCALE

SCORE 1-3

Pivoting doesn't require rebuilding

The org can replace components without breaking everything else. Contracts are short. Architecture is modular. What got you here doesn't have to be what gets you there.

SCORE 7-10

The org is committed to its current form

Changing how work gets done requires changing the org itself. Expensive, slow, and politically dangerous. Touch one thing, break five. So it doesn't happen.

THE WEIGHT OF LEGACY

High lock-in doesn't make transformation impossible. It makes it expensive enough that the people with authority to approve it are the same people whose power depends on things staying the same.

THE MAINTENANCE TAX

Organizations with high structural lock-in spend 60-80% of IT budget maintaining what already exists. Not because they planned it that way. Because the existing infrastructure demands to be fed. What's left over for new capability is whatever the maintenance doesn't eat first.

70%
Maintenance (Particle)
30%
Maintenance (Field)

EXAMPLES

FLEXIBLE SYSTEMS (Score 1-3)

Shopify

Modular architecture means components can be swapped without rebuilding everything. The platform bends when strategy changes.

2.2
Stripe

API-first. Decoupled services. Architecture designed for optionality, not permanence.

1.5

LOCKED-IN SYSTEMS (Score 7-10)

Comcast

$124B+ in total assets tied to cable infrastructure, parks, studios, and linear TV rights. Every strategic option runs through that constraint first.

6.95
Phillips 66

40-year refineries priced at original investment. Unwinding them means taking losses nobody wants to authorize.

6.4

DIAGNOSTIC QUESTIONS

1What would it cost to replace your core platform in two years?
2How many processes exist because of a vendor contract?
3If you had to pivot your delivery model in 90 days, what would break?
4What percentage of budget goes to maintaining existing infrastructure vs new capability?
5Who benefits organizationally from things staying the same?