The illusion of control

Do not index

The Predictive Path

Course 1: Strategy without control

Lesson 1: The illusion of control

The illusion of control

Why a revenue system you can see in complete detail can still be one you cannot steer.

Your dashboards can be flawless and you can still have no idea why the number moved. Seeing what happened is not the same as knowing what caused it — and only the cause lets you change what happens next. This lesson is about why a clearer view often comes with less control, not more.

The question that empties the room

A board meeting. The numbers are fine — a healthy pipeline, a forecast that holds, flat churn. Then an investor asks one question.

"If you deliberately slowed growth next year to protect margin — what actually happens, and how confident are you?"

Five capable people. Five different answers. No way to tell which is right.

The CFO has every dashboard ever built. Not one of them answers the question.

That room is the subject of this course. The data was not missing. Revenue reporting answers one question extremely well: what happened. It is close to useless at a second one: what happens if we change direction on purpose. Those two questions feel related. They are not. One is a record. The other is a guess about a system you just changed deliberately. A pile of the first never adds up to the second.

That failure has three properties. Worth naming up front:

It is structural — produced by how the revenue system is built, not by who runs it.

It grows with success — more scale, more segments, more motion all widen it.

It is invisible until tested — only a direction-change question reveals it.

Most leadership teams hit this and ask for better dashboards. That instinct is the trap.

You see more and steer less

Your revenue system is the most instrumented it has ever been. Marketing sees demand. Sales sees every deal. Customer teams see usage and health. Finance sees the forecast and the variance. You have never been able to see more.

You are very likely less able to steer it than when you could see far less.

Sit with that for a second, because the rest of the lesson depends on it. It is not a criticism of anyone in the room. It is a structural claim, and it holds for most companies past a certain size — including the well-run ones. More sight has not produced more control. It has produced more detail about the present, which is a different thing, and the gap between them is the whole problem.

Here is the claim in one line:

Seeing a revenue system and steering it are two different capabilities. At small scale they look like one. At scale they separate — and nothing tells you the day they did.

Test it on your own company. If we changed direction deliberately — margin over growth, or the reverse — what happens, and how sure are we? If the honest answer is "we'd model it, and we still would not agree," then seeing and steering have already come apart in your system. The rest of this lesson is why.

You control growth. You only watch everything else.

Most revenue leaders genuinely do control growth, in the way that matters day to day.

They move targets. They push pipeline. They pull demand spend forward, add sellers, discount to close a quarter. Top-line revenue is responsive. Pressure goes in, movement comes out, fast enough that cause and effect feel connected. That builds a habit of mind: intervene, watch the system react, conclude you are steering it. The loop is short and it closes. A loop that closes teaches you that you are in control.

But revenue is the most responsive dimension of the system. Almost everything traveling with it behaves nothing like it:

whether the margin inside that revenue holds or erodes

whether the customers won this quarter expand or decay over two years

how much support load the new business drags behind it

when the revenue actually turns into cash

whether the forecast gets more trustworthy or less as the mix shifts

None of these answer the wheel the way revenue does. They respond to structure, slowly, and the response lands long after the decision that caused it — usually after the people who made it have moved on. Dashboards report them accurately, but only as states after the fact. What each one became. Never how it was built, or how it would have come out different under a decision made earlier and upstream.

So you can be genuinely in control of the fast dimension and genuinely not in control of the slow ones, and feel in control of all of it. The feeling is a true thing stretched too far: revenue moves when pushed, so the system is steerable. The first half is true. The second does not follow.

More dashboards will not fix this

The reflex is to treat this as a visibility problem and add instrumentation. That reflex is the trap. More instrumentation produces more resolution on the present — a different thing from control.

In a small revenue system, seeing and steering genuinely overlap. That is the source of the confusion, because almost every leader learned the job in a smaller system. When revenue runs on a few levers, the causal chains are short. Something slows, you see why, you push the right place, it recovers. A leader can be excellent for years and never notice that seeing and steering are not the same thing — because at that size, they are.

At scale, the chains stop being short. Outcomes are produced by trajectories that interact:

which customers were admitted shapes the margin two years out

how deals were structured shapes the rhythm of cash

which expansion was encouraged shapes the support load

how the segment mix drifted shapes whether the forecast can be trusted

Instrumentation captures each of these as a state — accurately, in the present tense, one variable at a time. What it cannot show, however good it gets, is how moving one of them on purpose reshapes the others over time. The dashboard answers what is each thing now. The boardroom asked what becomes of all of them together if we change one deliberately. The first never adds up to the second.

This is where visibility turns deceptive instead of merely thin — and it is deceptive because it is so good. You can watch the engine run in perfect detail and still not predict how to steer it toward a chosen future, or what that steering costs elsewhere, later, when the cost is expensive to undo. Control has become observational. It looks directional because the picture is so sharp.

"What happened" is not a lever

Reporting answers what happened well. It is structurally weak at the second question: why did it happen, and would it happen again under different conditions?

A forecast that reconciles to actuals explains a result. It does not explain how the result was built. Those sound similar. They are not, and the difference is everything. Revenue can grow cleanly, on plan, for several quarters while the system holds no durable understanding of how the company's goals were actually produced underneath it:

which selection logic let in the customers who turned out to matter

which behaviors built durable value, not volume that looked identical for three quarters and then did not

which cost structures absorbed the support load the new business created

which expansion reinforced margin and cash, and which covered for erosion elsewhere and bought time no one chose to spend

When those links stay opaque, leadership sees outcomes but cannot connect them to what produced them. Growth, margin, and cash arrive as results — things that happened — not as consequences that were, in principle, designed. A team managing results rather than the conditions that produce them is doing something subtly different from steering. It is maintaining an accurate explanation of a system it is not shaping.

An explanation is not a lever. It tells you what the system did. A lever needs why, and "what happened" never contains "why." This is why strong quarters reassure less than they look like they should — the point the next lesson takes up directly.

A dashboard is a photograph of a moving thing

A dashboard freezes the system at a moment. A trajectory describes where it is heading, and whether that direction is what the company is trying to become. Only one of those is decision-relevant when the decision is about direction.

A customer can be healthy on every present-tense measure while narrowing off long-term value. The snapshot shows health, because health is a fact and the narrowing is a direction.

A segment can grow while its support intensity climbs underneath it, drifting off the margin it is supposed to deliver. The growth number looks like success the whole time.

Expansion can close reliably while covering for weak adoption beneath it — growth borrowed forward against a future that has not been told it is paying.

None of these are failures. Every one looks like success in the snapshot. They are directional shifts, and a directional shift is invisible to an instrument that measures states, because a state has no direction inside it.

This reframes what strategy is, and the reframe is the load-bearing idea of the course:

Strategy is not the choice of targets. It is the choice of trajectories — and keeping the ability to influence them while they can still be influenced.

A target is a destination you assert. A trajectory is a path the system is already traveling whether or not anyone is shaping it. Choosing targets without the ability to see and shape the trajectories underneath them is not strategy. It is forecasting with ambition attached. That is exactly what emptied the boardroom: a trajectory question, asked of a team that only had snapshots.

Success is what breaks it

This is the part most often misread as a people problem. Reading it that way sends companies looking for the answer where it is not.

Early on, you do not need structure. Intuition covers the gap. You cannot even see the gap yet. The founders know the customers by name. Segments are few, the motion is simple, one or two people hold the whole revenue system in their heads and reason about it correctly, live, with no instrumentation. The distance between seeing and steering does not exist in any way anyone can feel — not because it was solved, but because the system is small enough for one mind to span.

Then the company succeeds, and success is what breaks it.

New segments. A wider product line. New markets, new pricing, new motions. None of these are mistakes. Every one of them is what growth looks like. But each one lengthens the chain between a decision and its consequence, adds interactions that no longer fit in one head, and puts the system into permanent motion. It is never the same system two quarters running.

The instruments built to manage it were designed for a system that holds still long enough to be photographed. They are now asked to steer something that does not hold still. Control does not erode because anyone got worse. It erodes because the system started changing faster than understanding could move across it — and nothing was built to carry understanding once it outgrew the span of one mind. At the scale where that would have been cheap to build, it did not seem necessary. By the scale where it is necessary, its absence is the thing being felt in the boardroom.

The three beliefs that expire on you

The illusion of control is not the belief that everything is fine. Leaders who feel it are often sharply aware something is wrong. It is three smaller beliefs, each true at small scale, each false at large scale, none of which tells you the day it expired:

Visible, therefore steerable. That seeing the system and directing it are one capability. They were — once, when it was small.

Explainable, therefore repeatable. That an account of what happened is a grip on why. It is not, and never was. At small scale the difference did not bite.

Accountable, therefore in hand. That someone owning the number is the same as the system being directable toward it. This confuses responsibility for an outcome with the ability to construct it.

Each one holds right up until leadership is asked the question that depends on the difference — and the honest answer is that nobody can say. Not because the data is missing. Because the data does not contain that kind of answer.

The question did not remove control. It revealed that control had been observational longer than anyone noticed, because nothing had asked for the directional kind until now. That is the problem this course exists to take apart. Not that leaders stopped paying attention — they are paying more attention, to more instruments, than ever. The problem is that the attention went to outcomes and almost none of it to construction. A revenue system understood only by its outcomes can be watched in perfect detail and cannot be steered at all.

Next up

If visibility explains why leadership feels less certain even when nothing is visibly wrong, the next question is the harder one — the one that turns a strong quarter into a source of unease instead of confidence.

→ Continue to Grow on purpose

———

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