Why Most Good Ideas Die in the Boardroom

The Language Problem Nobody Talks About

I was in Zurich — coffee in hand, Ricoh GR camera ready — sitting by the river on a bright summer's morning, recording cathedral bells as they echoed across the water. The day before I had given a talk on value. Not the abstract kind, not the aspirational kind — the kind that makes executives stop scrolling, lean forward, and actually listen.

The talk kept returning to the same uncomfortable observation: most good ideas die in the boardroom. Not because they are bad ideas. Because they are told in the wrong language, to the wrong audience, without connecting to the thing that audience actually cares about.

The language problem nobody talks about

Years ago I worked with a technical manager. Brilliant mind. Calm presence. And a truly magnificent moustache — the kind that entered the room twenty seconds before the rest of him.

He had real solutions. Evidence-based, practical, achievable. Things the organisation genuinely needed. But every time he presented them to senior leaders, he lost the room.

The problem was not his ideas. The problem was not his delivery — he was a confident and clear presenter. The problem was that he spoke in the language of his domain, not the language of his audience.

Pipelines. CI/CD. DevOps. Infrastructure patterns. His peers understood immediately. Executives did not. Within minutes, phones appeared. Attention drifted. The idea quietly died — not because it was rejected, but because nobody in the room understood what they were being asked to care about.

He was not wrong. He was just not speaking in terms of value.

The translation most people skip

When you ask an executive — or any senior decision-maker — for support, funding, or permission, you are asking them to make a bet. They are going to spend the organisation's time, energy, attention, and money on your idea. They need to understand what they are getting in return.

Most people present the what of their idea clearly. The technical architecture. The process improvement. The new capability. The feature. They describe the thing they want to build with real care and detail.

What they skip is the why it matters in terms the organisation recognises as valuable.

This is the translation gap. And it is where most ideas die.

The problem compounds when people do attempt a value argument — because they often connect their idea to the wrong type of value. They frame a cost reduction initiative as a revenue opportunity. They frame an experiment as an enablement investment. They frame something genuinely valuable as something that sounds like a nice-to-have. And executives, trained to interrogate value claims, spot the mismatch and disengage.

We define four distinct types of value — and understanding which type your idea actually creates, and why that matters differently to different audiences, is the difference between an idea that gets funded and an idea that dies.

Critically, only one of those types — financial value — is external and generates direct revenue. The others are internally declared and often never tested against an outside market. That asymmetry shapes how executives hear your pitch, whether they realise it consciously or not.

What the moustachioed manager did next

We sat down together and stripped his ideas back to first principles. Not what he wanted to build — but why it mattered in terms the organisation could defend internally and externally.

His platform work was, at its core, a cost reduction play — less rework, fewer delays, a more stable foundation that stopped burning engineering time on firefighting. It was also an enablement play — a more resilient platform that gave the organisation the capacity to ship faster and more reliably. And with that enablement in place, it had a clear path toward financial value — faster time to market, reduced failure demand, more engineering capacity directed at features rather than fixes.

Three types of value, clearly named, connected to things the business could measure and defend. Nothing invented. Nothing exaggerated. Just the real value of the work, translated into language the audience actually understood.

He went back in. Same idea. Same calm delivery. But this time framed explicitly in those terms — cost, enablement, financial path. Executives leaned in. They asked questions. He left with the funding and support he had been chasing for months.

Nothing magical happened. The idea did not change. The framing did.

The preparation most people skip

Before any significant ask, it is worth sitting with three questions.

First: which of the four types of value does this idea actually create? Be honest — not aspirational. If it is primarily a cost reduction, say so clearly rather than trying to dress it as a revenue driver. Executives see through misaligned framing quickly, and it erodes trust in the rest of what you are saying.

Second: what evidence supports that value claim? Deming's observation applies here — without data you are just another person with an opinion. Go and find the numbers. Talk to finance. Talk to operations. Talk to whoever can give you the data that connects your idea to the value it claims to create. You do not need perfect data — you need enough to be credible.

Third: is this the right audience for this type of value? A cost reduction argument lands differently with a CFO than with a product director. An experiment argument lands differently with someone building a new capability than with someone trying to defend an existing one. Matching the value type to the audience's priorities is as important as identifying the right value type in the first place.

The ideas that survive the boardroom are not always the best ideas. They are the ideas that have been translated — connected clearly to value that the audience can recognise, defend to their own stakeholders, and feel confident supporting.

You almost certainly have ideas that matter. The translation is the work.