Saying "yes" and "no" without politics: the power of capacity scenarios

A CEO should never make trade-offs without a clear view of the impacts.

And yet. How many portfolio decisions are still made like this: "they've been pushing for 3 months", "we'll figure something out", "let's see next quarter".

It's human. It's comfortable. And it's exactly what's killing your delivery.

Because behind every unframed "yes" there's an existing project taking on water. A team absorbing the hit in silence. A customer commitment slipping. And no one sees it — until the crash.

Why trade-offs turn political

The reason is simple: capacity is never on the table.

When a VP walks into the executive committee with "a critical project," the discussion is about ambition, business impact, perceived urgency. Never about the question that really matters:

What do we take out to make room for it?

And since no one wants to be the one who takes something out… everyone says yes. The backlog swells. Teams suffocate. Deadlines blow up. And 6 months later, the executive committee wonders "why aren't we delivering."

The answer is brutal: because you said yes to everything, which amounts to prioritizing nothing.

Capacity scenarios: the CEO's most underused weapon

A capacity scenario isn't a fine-grained planning exercise. It's a decision-making tool that makes the invisible visible.

The principle is devastatingly simple:

→ If we add project X… → Then we push Y back by 3 months… → And we put Z on hold… → With this measurable impact on deliverables, workload and risks.

You no longer ask the executive committee "should we do X?". You ask it "do we prefer scenario A, B or C — and here's what each one costs".

The goal isn't to predict perfectly. The goal is to decide cleanly — with facts, not politics.

The decision framework (ready to use Monday morning)

For every new request that enters the portfolio, the executive committee must rule on 5 dimensions:

1. Business impact — measurable, not declarative. "It's strategic" isn't a number. What revenue? What risk reduction? What concrete operational gain?

2. Real urgency vs. political urgency — the real question: what happens if we do it in 6 months instead of now? If the answer is "nothing serious"… it's not urgent.

3. Capacity required per team — not "we need 5 devs," but "we need 3 back-end FTEs, 1 data, 0.5 architect for 4 months." And above all: do these people exist and are they available?

4. Dependencies — what does it block if we launch it? What gets blocked if we don't? Dependencies are the number-one blind spot in poorly managed portfolios.

5. Risk — technical (we've never done it), organizational (it touches 4 teams), regulatory (a legal deadline). Risk radically changes prioritization.

This framework doesn't slow decisions down. It prevents fast bad decisions.

What this changes in practice

When you shift from a "say yes and we'll see" mode to a capacity-scenarios mode, the culture changes at its core:

"Yes" becomes a real commitment. No longer wishful thinking. Saying yes means allocating identified resources, on a realistic timeline, with a validated scope. It holds everyone accountable.

"No" becomes a protection, not an insult. Saying no to a project no longer means "your topic isn't important." It means "your topic is important, but if we do it now, here's what we sacrifice — and that sacrifice is worse."

The CIO earns their place on the executive committee. No longer in "we'll do our best" mode — but bringing data, scenarios, quantified trade-offs. The CIO goes from supplier to strategic partner.

The business units finally understand the real cost of their requests. When a director sees that "their" project pushes back 2 other initiatives, they start thinking differently. Some withdraw their request on their own. That's the sign the system works.

The maturity test in one question

Ask your CIO this question: "If I ask you to add a project tomorrow morning, how long will it take you to show me the impact on the existing portfolio?"

If the answer is "a few hours" → you have a system.

If the answer is "I'd need to look into it" → you're flying blind.

And flying blind is a luxury no IT department can afford anymore.

Capacity scenarios aren't just one more tool. They're the missing link between strategy and execution. The one that turns intentions into decisions — and decisions into results.

This article first appeared in my LinkedIn newsletter Il était une fois un CODIR, where every two weeks I share real-life situations from the leadership team.