Grow on purpose

Do not index

The Predictive Path

Course 1: Strategy without control

Lesson 2: Grow on purpose

Grow on purpose

Why a good quarter you cannot explain is more dangerous than a bad one you can.

Anyone can grow once. The number goes up, the quarter closes, and no one can say precisely what produced it. Growth you can't reproduce on purpose isn't control — it's a result you can't promise to repeat. This lesson is about the difference between growth that arrived and growth you can run again.

The quarter that should feel good and doesn't

The numbers came in strong. Revenue above plan. Churn flat. Two big expansions closed. By every dashboard, a good quarter.

The CEO asks the obvious question: can we do that again next quarter, on purpose?

Nobody says no. Nobody can say yes either. The honest answer is some version of "probably, if conditions hold" — which is not a yes. It is a hope wearing a yes.

That hesitation is the subject of this lesson. The company did not lose performance. It lost something harder to see and more expensive to lose: the ability to reproduce the result deliberately. And the moment that goes, confidence starts draining — long before any number turns.

This is the part that surprises leaders most:

A strong quarter you cannot explain damages confidence more than a weak quarter you can. A weak quarter you understand comes with a lever. A strong quarter you don't understand comes with nothing — just the hope it happens again.

Early success is assembled, not engineered

Early success is rarely built on purpose. It is assembled from things that happened to line up.

A favorable market. Strong early adopters. Positioning that landed. A few good decisions made at the right time by people who could hold the whole picture in their heads. These combine into momentum, and momentum produces growth, and growth produces confidence.

At that stage, leadership does not need deep causal understanding. The system is responsive. Adjustments seem to work. Outcomes arrive fast enough that intuition still feels reliable, because the loop between decision and result is short enough to reason about by feel.

Then the company scales, and the same success starts asking a different question:

Can we repeat this on purpose — not just in revenue, but in margin, expansion, support load, and cash timing?

This is where many companies stall. Not because success disappeared. Because how it was built was never visible in the first place, and you cannot deliberately repeat a thing whose construction you cannot see.

You can name who bought. You cannot name why it worked.

At this stage leaders can answer the surface questions with full confidence. They can name the customers, the segments, the deals that closed, the revenue that arrived.

What they cannot name is the layer underneath:

which selection logic admitted the customers who turned out to matter

which behaviors actually created value over time, versus volume that looked like value for three quarters

which costs were structural versus incidental

which trade-offs were accepted without anyone deciding to accept them

Knowing who bought is not the same as knowing why it worked.

That gap stays invisible until someone asks a stress question. What happens if we tighten selectivity? Add a segment? Change pricing? Slow expansion? Push growth harder? Each of these is answerable only if the construction is understood. When it is not, the honest answer to every one of them is a shrug dressed up as judgment. The system delivered an outcome. It did not reveal its logic, and an outcome without its logic cannot be stress-tested — only repeated and hoped over.

Repetition is the real test, not success

Early success rarely tests a leadership team. Repetition does, because repetition asks the questions success let you skip:

which customer attributes actually mattered, not which ones we assumed

which behaviors compounded value versus which ones drained it

which structures — pricing, contracts, support models — made the outcome viable rather than incidental

which assumptions were true, and which were merely convenient and never checked

In a lot of companies these questions have no clean answer, and the effect of that is not loud. It is a slow change in how leadership behaves. Plans get more cautious. Investment timing turns conservative, or erratic. Targets get set, then hedged in the same breath. Strategy conversations drift toward narrative — the story of why it will work — because the structural answer for why it worked last time is not available.

That is not a loss of ambition. It is a loss of causal clarity, and the two look different from outside. When outcomes cannot be repeated deliberately, leadership is not steering the system. It is hoping the system repeats, with a forecast attached to the hope.

Failure gets investigated. Success gets a pass.

Here is the asymmetry that makes this so hard to catch in time.

When numbers miss, organizations investigate hard. Root cause, retro, corrective action. When numbers hit, they move on. Failure is examined for causes; success is accepted as proof. Nobody runs a retro on a quarter that beat plan.

That asymmetry has a compounding cost. Outcomes accumulate without any matching accumulation of understanding. Every good quarter that goes uninvestigated is a quarter of construction knowledge the company chose not to acquire. Confidence thins while the dashboards stay green, which is exactly why nobody flags it — there is no alarm for a result you got without knowing how.

You can hear it start, though, in the questions leadership begins asking sideways:

"Are we sure this holds?"

"What happens if growth slows?"

"Can we actually afford to scale this?"

These are not pessimism. They are a leadership team noticing, accurately, that it cannot answer structural questions about a system it is accountable for. The questions are the early signal. They show up well before the numbers do.

Outcomes are not the same thing as consequences

Underneath all of this is a category error. Most organizations track outcomes. Very few model consequences. They are not the same thing, and treating them as the same is the error.

Outcomes answer: did revenue grow, did margin hold, did churn stay in range. Consequences answer a different set: what did this growth require, which costs scale with it, which behaviors does it reinforce, which risks did it defer rather than resolve.

A company that tracks only outcomes can watch performance and cannot shape trajectory. Growth becomes something to monitor instead of something to design. Margin becomes a result instead of a structure. Cash becomes a number instead of a behavior. The company is successful and not steerable at the same time, and those two facts stop being in tension once you see that one is about outcomes and the other is about consequences.

This is also why confidence erodes before performance does. A leadership team can feel, accurately, when it no longer understands the system it is responsible for — and it feels that the moment repeatability goes, not the quarter results finally turn. Decisions get heavier. Alignment takes longer. Commitments soften. Explanation replaces design. None of that needs declining results. It only needs the loss of repeatability.

The real cost is who decides what happens next

The true cost of non-repeatability is not operational confusion. It is the loss of decision leverage — and decision leverage is the thing strategy is made of.

When outcomes cannot be reproduced deliberately, leadership stops controlling when and how consequences unfold. Decisions still get made. They are just increasingly shaped by outside pressure rather than internal intent:

fundraising timing becomes reactive instead of chosen

valuation becomes negotiated rather than earned

growth pace gets set by runway rather than by strategy

hiring and investment get pulled forward or delayed by pressure, not design

In those moments, hesitation is not a failure of nerve. It is a rational response to lost optionality. When you cannot say what happens if you change one variable, you stop exercising choice and start protecting position. Decisions get deferred. Strategy narrows to what feels survivable instead of what is right.

And control moves elsewhere without anyone handing it over. Investors start dictating timing. The market dictates pace. Operational constraints dictate strategy. Not because leadership abdicated, but because the system can no longer explain how its outcomes are constructed or how they would change under different conditions. The cost does not show up in revenue. It shows up in who gets to decide what happens next.

Drifting is not the same as failing

Success answers one question: did we get here? Repeatability answers a different one: can we choose where to go next?

Companies that cannot repeat outcomes deliberately are not failing. They are drifting — and drifting is harder to see than failing, because every individual quarter still looks fine. They observe results but cannot author them. They explain outcomes but cannot design consequences. They grow but cannot say what the next unit of growth will cost or produce.

That is the point where strategy starts to break. Not because ambition ran out, but because the outcomes were never built as a system in the first place — only achieved, then hoped over. Naming that is the whole job of this course. The next lesson takes the same gap and follows it into the org chart, where it turns reasonable expectations into roles no individual can actually fulfil.

Next up

Once outcomes cannot be repeated on purpose, the problem moves from performance to responsibility — and leaders start being handed jobs that no one in the structure can actually do.

→ Continue to The impossible jobs

———

This article is part of The Predictive Path

By Niko Laine, SaaS CFO

→ About the author

→ LinkedIn

You can read it on its own or explore the full curriculum.

→ View The Predictive Path

→ Explore courses