Back to Growing Pains

Transformation

The Spiral Model

Change rarely moves in a clean line.

Most transformation plans pretend the business can walk from old to new in a straight line. Current state over here. Future state over there. A roadmap in the middle with clean arrows and confident dates.

Real change does not behave so neatly. The business loosens, tightens, panics, learns, returns to an old habit, then sees the habit differently. It comes back around, but not to the same place. This is the spiral.

No Clean Jump

You cannot skip phases just because the strategy deck wants speed. Each phase builds the capability needed for the next one. A rigid company needs enough structure to function while it learns to move. A loose company may need new boundaries before it can scale.

Trying to jump from particle to field without the middle work creates chaos without coordination. The system does not become modern. It becomes confused.

The Return With Learning

The spiral is not failure because an old pattern returns. Pressure brings old patterns back. The question is whether the business can see the pattern sooner, hold it differently, and choose a better move the next time.

Amazon did not start with AWS. It learned books, warehouses, marketplace, infrastructure, logistics. Each move carried capability from the last one. Most transformation stories clean up this part too much.

The Next Reachable Move

Name the current state honestly. Particle, transition, field, or a mix by function. Then choose the move the system can actually absorb.

Good transformation keeps enough boundary to function while creating enough movement to learn. Too much boundary hardens the past. Too much movement breaks trust.

Questions to carry

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

The current stateParticle, Transitioning, Field, or a mix across functions.
The skipped phaseThe phase leaders want to leap over usually returns as resistance.
The reachable moveSmall enough to absorb, real enough to change the path.

Use it when

Use this read when transformation is being treated like a clean jump instead of a staged change.