Why Smart Decision-Makers Ruin Companies – Without Realising It

This story is no isolated case.

It is happening right now in hundreds of companies – quietly, rationally justified and entirely avoidable.

He was smart. Very smart. Quick mind. Successful head of sales. A numbers person. A decision-maker.

And that was exactly why we thought: He'll get it.

We showed him the analytics. He saw the customer journey. He recognised the pattern. And would act correctly.

We were wrong. Not because he lacked intelligence. But because he lacked something else:

The ability to lead time delay.

The starting point: a system with delay

We were the performance agency. Global. B2C. Marketing worked. Stable. Profitable.

Most important point: the product was not an impulse buy.

From the first click to purchase, an average of 87 days passed.

That means: you do not steer ads → revenue.

You steer cohorts.

Every week a new group of potential customers starts.

These groups need time.

A decision without time logic

Internally a conflict escalated. The CMO left. For weeks decisions were missing. In this gap the budget got cut. Not from strategy. But because no one was there to defend the system.

Campaigns kept running – with smaller cohorts. The pipeline began to shrink. Invisibly. But really.

Then he took over. Sales in his blood. Results-focused.

His mental model was clear – and fatally simple:

Investment → result. Now.

---

The warning that didn't land

We laid everything out:

• Customer journey: 87 days
• Cohort logic: ~13 weeks
• Current revenue = decisions from the past

We said:

"Don't compare this week's budget with this week's revenue.

He nodded. Theoretically.

Then came the sentence that explains everything:

"I'm investing EUR 10,000 this week. I want to see results this week."

And when we pointed to the 13 weeks again:

This wasn't stinginess. Not stupidity. Not defiance.

It was present bias in a delayed system.

Or put more simply:

He ran a system that needs time with the expectation of instant results.

Rational self-destruction

The first weeks looked good. Less budget. Similar revenue.

ROI rose!

The fallacy: that wasn't his performance.

That was the cohorts from before.

Then – weeks later – revenue dropped. Not dramatically. But measurably.

The reaction was logical. And deadly.

• Falling revenue → budget cut.
• Budget cut → smaller cohorts.
• Smaller cohorts → even less revenue later.

You fight a problem in the present and program the collapse of the future.

In the final weeks no one spoke about growth any more.

Only about costs.

And at some point not even about that.

The lesson

It was never a marketing problem. It was a leadership problem.

In delayed systems this applies:

• Stability beats "efficiency"
• Cohorts beat weekly comparisons
• Leadership beats actionism

Not every problem is a performance problem.

Some problems are a time problem.

The bottom line

He was smart. But he could not see the 13 weeks.

And in systems with time delay a law applies:

Impatience is the most expensive decision.