Visibility isn't an exec-committee use case

A director buys a tool. The goal fits in a single sentence, the one you find in every business case: 'give the executive committee visibility.' Budget approved, rollout launched, teams trained.

Eighteen months later, the verdict. There are dashboards. There are reports, now half-generated by AI. There are even nice portfolio slides. Everyone can see. And yet, no one decides anything differently than before. The same projects drift, the same trade-offs are made on gut feel, the same overloads blow up in June.

How can a tool deliver exactly what was asked of it, and change nothing?

Because visibility was never the question. It's actually the opposite: when an organization buys a tool 'to get visibility,' it's almost always an admission that it couldn't name the decision it wanted to make. Ten years advising mid-market companies and large groups have convinced me of one thing: we don't suffer from a lack of visibility. We suffer from not knowing what to look at, for whom, and to decide what.

Why we buy tools that serve no purpose.

'We need visibility.' It's probably the most expensive sentence an executive committee ever utters. It sounds obvious, reasonable, hard to argue with. And that's precisely what makes it dangerous.

Because it says nothing. Visibility into what? Timelines, workload, budgets, risks, benefits, dependencies? For whom? The project manager steering their week doesn't need the same thing as the CEO weighing their year. And above all: to decide what? Visibility that leads to no decision isn't visibility. It's decoration.

When you buy a tool on that word, you're buying a mirror. It reflects your organization back at you, sometimes beautifully. But a mirror settles nothing. You see the overload, and you fund it anyway, because seeing was never the problem.

AI has just killed visibility as a sales pitch.

Here's what makes this mistake even more costly today than it was yesterday.

Everything that used to be about 'seeing, consolidating, formatting' is becoming free. Aggregating statuses, generating a report, producing the portfolio slide for Monday's executive committee: AI now does it in seconds, from what you already have in a Jira, an Asana, a spreadsheet. Visibility is being commoditized before your eyes.

In other words, if a tool's promise boils down to 'you'll see better,' that promise has just lost all its value. You no longer need a tool to see. You need one to decide.

And the decision, for its part, cannot be commoditized. Because it doesn't depend on the ability to display a data point, but on the quality of the process that produces that data and the cadence at which you confront it with a choice. That's what stays rare. That's what creates value.

A tool is only worth as much as the process it serves.

This is the point most tool purchases forget to ask: what is the nature of the process this tool supports?

Take any category. A CRM is worthless if the sales process underneath isn't clear: who qualifies, who follows up, who decides to kill a deal. A finance tool is worthless without the closing and trade-off process it equips. A BPM bought 'for transparency' when you already have a Jira only adds a redundant layer of visibility on top of a process no one has defined.

The opposition every transformation consultant keeps rehashing, people versus process versus tools, has become sterile from being recited so often. The point isn't to 'align' them in the abstract. The point is concrete and brutal: for which decision do you choose a given tool, in service of which process, operated by whom. When that chain is clear, the ROI follows. When it's blurry, the tool fails, the process stays inefficient, and the teams don't deliver their value. Not for lack of effort. For lack of an answer to a question no one ever asked.

So let's actually ask it. Which decisions deserve for an organization to build a continuous process around them, and not just one more dashboard?

The three decisions that truly deserve a process.

From watching what works and what fails, I see only three. Three decisions, structural, recurring, that every organization already makes, but most often badly, because it makes them without a process and without a cadence.

It's precisely around these three decisions, and nothing else, that we built AirSaas. Not around visibility. Around the decision.

What you say yes to.

Demand management. Every idea, every candidate project, every 'we really should do this' ought to be qualified before it enters the portfolio: tied to real capacity and to an expected benefit. The decision isn't 'is this a good idea' (almost all of them are), it's 'which one do we give up so the others can move forward.' That's the purpose of our demand-management process: turning a stream of wants into a trade-off you own.

What you can actually deliver. Capacity scenario planning. It's the chain that runs from the brief to scoping, then to AI-based workload estimation, all the way to scenario simulation: quarter by quarter, team by team, what really holds up. The decision: which scenario you commit to, knowing what it displaces. This is where the famous one euro out of ten that organizations waste, by funding a capacity they've never measured, is at stake.

What you actually gained. Benefits management. A business case promises millions. Almost no one checks, three and six months later, whether the benefits materialized. Without that loop, the organization never learns, and the next trade-off is made blind all over again. The decision: what do we reinvest, what do we stop, what did we learn.

These three are not features. They're the three moments when an organization truly decides what it becomes. A tool that serves them creates value. A tool that merely displays them produces none.

The real question before buying anything at all.

Let's return to the director from the start, with their dashboards and their AI-generated slides. Their mistake wasn't choosing the wrong tool. It was asking the wrong question. They asked 'how do we see,' when the only question that matters is: decide what, by whom, and at what cadence.

This is the question that should precede every tool purchase, in any category. Not 'will it give me visibility,' but 'which decision, made by whom, will this process make better and more regular.' If you can't answer it, no tool will save you. You'll buy one more mirror.

Visibility isn't a use case. It's a by-product. The use case is the decision. And an organization that knows which decisions it wants to make, for whom, continuously, no longer needs anyone to sell it visibility. It already knows exactly what to look at.

This article first appeared in my LinkedIn newsletter Il était une fois un CODIR, where every two weeks I recount situations lived through in leadership committees.