Ten questions every CEO and CFO should ask about their project portfolio

Blog post — Beyond the Project Curtain

As a CEO or CFO, the information reaching you about complex business change projects is often meticulously filtered. Project teams present what executives want to hear. Status reports are optimised for senior consumption. Governance meetings are performances of competence and control rather than genuine exercises in transparency.

This is not malicious. It is the entirely predictable behaviour of people operating in an environment where delivering uncomfortable truths carries career risk and where the cultural norm of every executive meeting is to convey that things are under control.

The result is that you are frequently governing on the basis of a carefully managed version of reality rather than the operational reality your project professionals are actually living. The gap between those two things is where most project disappointment originates — and where the most value available to any senior leader is concentrated.

These ten questions are designed to close that gap. Deployed at the right stage of a project's lifecycle, they cut through the governance theatre, expose the assumptions nobody has tested, and surface the uncomfortable truths that polished presentations are specifically designed to conceal.

The questions are intentionally multi-faceted. Each one is a trigger that unpacks into a comprehensive line of inquiry. And the inability of a project team to fully answer them is itself the intelligence — an immediate indicator that the underlying proposal lacks the maturity and rigour that should precede significant capital commitment.

At the concept stage — before a business case is drafted

Question 1: What validated problem are we truly solving?

What credible alternatives were rigorously considered? Why is this option demonstrably superior? What are the concrete consequences of inaction? The concept stage is where an insidious momentum for "yes" takes root — fuelled by senior leader enthusiasm, persuasive narratives, and cognitive biases that skew perception toward desired outcomes before the cost or complexity is genuinely understood. This question is designed to halt that momentum before it becomes irreversible.

Question 2: What are the inherent complexities of this project, and do we have the expertise to understand them?

Before committing the bandwidth of your stretched executive team to a full business case, verify your true capacity. Do you possess the necessary expertise in-house, or must you acquire it externally? The original sin of many failing projects is a profound underestimation of complexity, risk, and resource drain at precisely this stage — when enthusiasm makes the challenge seem manageable and the end state seems clear.

At the approval stage — when the business case is presented

Question 3: What is the absolute minimum viable scope that delivers quantifiable strategic value?

If a demonstrably lower complexity, lower cost, lower risk version can achieve the core strategic value, why are we pursuing the more complex, more expensive, higher risk option? This question forces genuine reflection on whether the proposed solution has expanded beyond what the business truly requires.

Question 4: Who holds singular, unambiguous accountability for the end-to-end realisation of the promised value?

And what rigorous, objective evidence confirms that this individual and their team possess the proven leadership, specific expertise, and organisational capacity required? Diffused responsibility is a notorious precursor to project failure. A named leader is not the same as a capable one.

Question 5: Have all foundational assumptions been rigorously identified, documented, and validated?

For critical assumptions — where invalidation would severely impact strategic outcomes or financial projections — what is the quantifiable potential consequence, and what specific proactive mitigation is in place? The sheer volume of detail in a business case allows critical implicit assumptions to hide in plain sight until they become the factors that explain why things went wrong.

During execution — as the project unfolds

Question 6: Is the reported Green status a genuine reflection of a sustainable plan?

Or is it being artificially maintained through excessive unplanned effort and team exhaustion? A project's Green status can be a dangerous illusion. The complaints about unresponsive teams or poor performance later in delivery are often early indicators that initial estimates were fundamentally flawed — and that the team has been running on reserves for months.

Question 7: What is the single most uncomfortable truth about this initiative that poses the greatest risk to its strategic objectives?

This question forces project leaders to step back from the minutiae and articulate what genuinely concerns them — not the challenges already being managed, but the one that they have not yet found the right moment to surface. The answer, and the manner of its delivery, is among the most valuable intelligence available to any executive governing a complex initiative.

Question 8: What structured validation confirms that Business-As-Usual teams are fully prepared to receive and sustain project deliverables?

Project teams are transient. Their success is measured by delivery metrics, not by the enduring health of what they leave behind. This question ensures that the governance layer is looking beyond project closure to operational sustainability.

Question 9: If we had to stop today, what could we salvage, and what would it cost to close?

This is a reality check designed to puncture the illusion of inevitable continuation. Even without an immediate intent to stop, the mere fact that it is being asked reminds everyone that every initiative must continuously justify its existence — and keeps project teams acutely focused on the strategic rationale rather than the momentum of delivery.

Question 10: What is the unacknowledged reality we are collectively avoiding?

Not the obvious challenges already being managed. The nagging feeling nobody has put words to yet. The collective blind spot that everyone intuitively senses but has not dared to articulate. This is an invitation for open dialogue — and for the kind of outside-the-box thinking that prevents unspoken concerns from becoming catastrophic failures.

How to use these questions

The true intelligence from these questions often resides not in the direct content of the responses, but in how those answers are framed — and, crucially, in the strategic silences and glaring omissions. A team that answers fluently at the concept stage but hesitates at the approval stage questions has revealed where their foundational thinking is weakest. A team that provides confident answers to Questions 1 through 5 but cannot fully address Question 7 has told you something important about what is not being surfaced through formal channels.

Use them selectively, at the stages where they are most relevant. And use them consistently — not as a one-time exercise but as the governance reflex that shapes every significant investment decision your organisation makes.

The organisations that ask better questions make fewer expensive mistakes. The ones that do not keep discovering, after the fact, that the information they needed was always there — it just never found a question worth answering honestly.

Want to go deeper?

This post draws on ideas developed at length in Beyond the Project Curtain (CEO/CFO Edition). If what you found here was useful, a free core summary is available to download at ghostquantumco.com/books/beyond-the-project-curtain.

Richard Cantlon offers one-to-one consultations for executives who want to apply these frameworks to a specific initiative. Schedule a session at ghostquantumco.com.