The spiral, not the pipeline

The pipeline metaphor has won, and I think it's quietly costing us a great deal.

Sales pipeline. Content pipeline. Research pipeline. Hiring pipeline. Product-development pipeline. We borrowed the word from oil and gas — a thing flowing through stages from one fixed point to another — and we welded it onto creative and strategic work where the assumption barely holds. Stage one to stage two to stage three. Inputs on the left, outputs on the right, efficiency in the middle. Anything that doesn't move forward is "stuck." Anything that goes backward is a "regression." Anything that collapses is a "failure."

I've spent enough years inside teams trying to ship work that I can tell you what this metaphor does to the people inside it. It punishes the parts of the cycle that the work needs most.

So here's the working claim: most of the work I care about is not a pipeline. It's a spiral. And the difference is not cosmetic.

What the spiral describes

In 2002, the ecologist C.S. Holling, with Lance Gunderson and a small group of colleagues, published a book called Panarchy. Holling had spent decades watching forests, fisheries, and rangelands, and he had noticed that living systems do not move in a straight line. They cycle. He called the cycle the adaptive cycle, and he gave it four phases:

- Growth. Capital accumulates. New structure forms. Things compound. - Saturation. The system is full. Efficiency rises but flexibility falls. New entrants struggle. The system is locked in. - Release. Something breaks. Capital is freed. Old structure collapses. From the outside it looks like failure. - Reorganization. The freed material rearranges into new structure, often at a new scale. The next growth phase begins.

Then around again. Holling drew it as a figure-eight loop, but the more important property is that each turn touches a different scale than the last. That's why he called it Panarchy and not just "the cycle." The work isn't just repeating itself — it's spiraling.

Once you have the picture in your head, you cannot unsee it in the kind of work I do.

Where the pipeline metaphor fails

A pipeline has three failure modes that the spiral handles cleanly.

One: the pipeline has no room for saturation. In a pipeline, the only relationship to volume is "more is better." But anyone who has run a content program for more than a year has seen what happens when a category saturates. Posting harder doesn't help. The audience is full. The medium is full. The idea-space is full. Saturation is a real phase that requires a real response — and the pipeline metaphor has no name for it, so the team's response is usually to do more of the thing that stopped working.

Two: the pipeline has no room for release. Release is the part where something has to collapse so that new structure can form. In a strategic context, this might be a positioning that has to be retired. In a research context, it might be a thesis that has to be abandoned. In a creative context, it might be a body of work that has to be archived. The pipeline metaphor reads release as failure: things broke, the pipeline emptied, we lost throughput. The spiral reads release as a phase: capital was freed for the next form.

The cost of misreading release as failure is that teams fight it. They try to keep the dying structure alive past its phase. They throw resources into a saturated market and call it commitment. They cling to a positioning that has already lost its grip. Naming the phase changes the move from defense to graceful release.

Three: the pipeline has no concept of scale-shift. A pipeline produces the same kind of output forever. A spiral, by contrast, lifts to new scale on each turn. Strategy work is supposed to do this. The first cycle gets the team a working positioning. The second cycle pushes that positioning into a more demanding context — a bigger market, a harder audience, a more contested category. The pipeline metaphor flattens this. The spiral honors it.

How to tell what phase you're in

I can't give a complete diagnostic — that's a longer piece — but here are the four signals I have started using out loud.

You're in growth when: - New ideas compound on previous ones. - The team's vocabulary is expanding. - Distribution is getting easier, not harder. - Each new piece of work makes the next piece easier.

You're in saturation when: - Effort is constant or rising and output is flat. - The vocabulary stops expanding; people use the same words for everything. - Distribution is steady but plateaued. - New work feels like variations on existing work.

You're in release when: - Something that was load-bearing has stopped working — a positioning, a partnership, a product, a frame. - The team's instinct is to defend the old structure. - Resources spent on defense outpace resources spent on new work. - The mood feels like grief, not panic. (Panic is often saturation. Grief is often release.)

You're in reorganization when: - Old material is being recombined into new shapes. - The team is generative again but in a different register. - New questions are being asked, not just new versions of old questions. - The vocabulary is changing.

These are early. They will sharpen under contact with other operators' work.

Why this matters strategically

The strategic implication is direct. Different phases want different work.

A team in growth wants more ground covered, more bets placed, more compounding. Adding structure here slows them down. The right move is to let them run.

A team in saturation does not want more output. It wants higher-resolution targeting and a sharper read of where the saturation breaks. Adding more posts to a saturated content program is a category error.

A team in release does not want a new pipeline. It wants permission for the collapse, an honest accounting of what's being released, and protection against premature rebuilding. The temptation in release is to skip the phase — to leap past the grief into a new pipeline before the old structure is fully freed. The work doesn't compose well when you do that.

A team in reorganization wants seed material, conceptual bridges, and patience. It does not want KPIs that measure the speed of the new pipeline, because there isn't one yet. The metric that matters is whether the recombination produces things that did not exist before.

Treating all four phases as if they were the same phase — which is what the pipeline metaphor encourages — is one of the most expensive mistakes I see strategic teams make. It is not a small mistake. It compounds.

What the spiral changes about how you plan

The pipeline plans by stage-gates and throughput. The spiral plans by phase and by readiness for the next phase.

A pipeline-shaped plan looks like: by Q2 we will have produced X assets, captured Y leads, converted Z accounts.

A spiral-shaped plan looks like: by Q2 we will have completed our growth phase in this category and be entering saturation; by Q3 we expect to need a release window, during which we will retire the existing positioning and free capital for the next thesis; by Q4 we expect to be in reorganization, during which the team will not be running a high-volume pipeline but will be building the seed material for the next growth cycle.

The second plan is uncomfortable. It contains a phase ("release") that conventional planning treats as failure. It contains a phase ("reorganization") that conventional planning has no idea how to budget for. But it matches how the work actually moves, which is the only thing that matters.

What's still open

I don't have a clean answer yet for KPI design under the spiral. The honest answer is that different phases want different metrics — growth wants compounding, saturation wants resolution, release wants honest accounting, reorganization wants generativity — and the practical question is whether teams can hold four metric regimes simultaneously without the framework collapsing into incoherence.

I also don't know how to introduce this language into a team that has been speaking pipeline for a decade. The vocabulary lift is real. But every team I have helped through a release phase has found the language a relief, because it gave them permission for what they already needed to do.

If you have run a team or a category through a full cycle — growth into saturation into release into reorganization, and out into the next growth — I want to hear how you describe it. The vocabulary will be better when more shoulders have weighed in.