Decide the Question First: Framing Before Choosing on Large Capital Projects

Around the world, owners, sponsors and governments are committing unprecedented sums to large capital projects: energy transition assets, process plants, mines, transport corridors, water systems and digital infrastructure. Each of these investments passes through a long sequence of studies, gate reviews, options papers and board submissions before a single foundation is poured. Enormous effort goes into analysing alternatives, refining estimates and polishing schedules. Far less attention is given to a more basic question that sits upstream of all that work: what, precisely, is being decided? When the question is vague, contested or quietly substituted for a more convenient one, even the most rigorous analysis can deliver a precise answer to the wrong problem. The result is a project that is executed efficiently against an objective that was never the right one, and the consequences surface years later, when they are most expensive to correct.

This comprehensive blog will explore why framing the decision must come before choosing among options on large capital projects. It is written for project directors, project managers, owner representatives, programme management consultants and sponsors who prepare or approve front-end decisions. We will examine the difference between doing things right and doing the right thing, why the front end of a project is where the frame is set, and how human judgment makes a thin story feel like a complete question. We will then look at how logically identical descriptions can change a choice, how to name the live decision in a single sentence, why purpose should be fixed before means, and who should own the frame. Finally, we will consider how shaping turns the question into a coalition matter, how to structure a problem once the question is stable, how to tell a wrong problem from a wrong estimate or a contested context, and what a practical framing discipline looks like for project leaders.

1. Introduction: Precise Answers to the Wrong Question

A familiar pattern repeats across large capital projects. A schedule slips, and a recovery plan is commissioned. A cost estimate rises, and a value-engineering exercise begins. A partner raises concerns, and an options study is launched. In each case a capable team is mobilised, the analysis is thorough and the report is well presented. Yet the underlying decision may never have been examined. The recovery plan may be accelerating a concept that no longer serves the business. The value-engineering exercise may be trimming scope when the real issue is commercial. The options study may compare variants of a solution when the owner has not agreed what problem the project is meant to solve.

Professional analytics practice describes this failure in plain terms: teams that skip problem framing often solve the wrong challenge with great precision. The recommended remedy is equally plain. Work should begin with a clear statement of the business problem, question or opportunity, expressed in business rather than technical terms, and stakeholders should agree on that statement before any modelling begins.

On large capital projects the stakes of skipping this step are unusually high. Decisions are long-lived, capital is committed in large tranches, and many parties (owners, sponsors, consultants, designers, contractors, lenders and public authorities) each bring their own view of what the project is for. Framing is the discipline that turns those views into one decision that can be owned, structured and tested.

2. Doing Things Right Versus Doing the Right Thing

Systems thinking draws a sharp distinction between efficiency and effectiveness. Efficiency is doing things right; effectiveness is doing the right thing. The two are easily confused, because organisations are far better at measuring efficiency. Progress curves, earned value, productivity rates and cost performance indices all measure how well work is being done. Very few routine reports ask whether the work being done is the right work.

The systems view adds an uncomfortable observation: the righter an organisation does the wrong thing, the wronger it becomes. Correcting mistakes while pursuing the wrong objective does not reduce error; it compounds it, because every improvement entrenches the wrong direction. It is, in that sense, better to do the right thing imperfectly than to do the wrong thing perfectly. The same perspective warns that improving the parts of a system separately may not improve the whole, and may make overall performance worse.

Large capital projects are especially exposed to this trap. They are organised into packages, disciplines and contracts, each with its own targets. A designer can optimise a layout, a contractor can optimise a construction sequence and a procurement team can optimise a supply strategy, while the asset as a whole drifts away from what the business actually needs. Practitioner guidance on problem framing offers a simple illustration from outside construction: a well-executed solution aimed at a symptom, such as a loyalty programme introduced when the real issue lies in customer onboarding, still misses the real problem. The equivalent on a large capital project is a superbly managed schedule recovery for a configuration that should have been reconsidered.

Figure 1: Doing things right versus doing the right thing. Efficiency without effectiveness compounds error.

3. Why the Front End Decides the Frame

The research literature on the front end of projects is consistent on one point: many of the factors that determine project outcomes are built into the definitional decisions made before execution begins. The front end is where the opportunity space is explored, conceptual alternatives are carved out, success criteria are defined and stakeholder preferences are surfaced. A recurring failure pathway is the "rush to solution", in which inadequate early definition locks a project onto a concept before the problem has been understood. The same literature observes that fewer resources are often spent identifying the best concept than on polishing tactical delivery.

Owner-side benchmarking reaches a similar conclusion from a different direction. Front-end loading is the process that defines a project before execution, organised in phases separated by gates that can allow a project to proceed, recycle or stop. The first phase covers the business case and a feasibility screen; the second closes scope; the third, before full-funds authorisation, covers advanced definition and the execution plan. The exit from the first phase, where the business question is settled, is described as the least well managed gate, and too few projects are stopped once the third phase has begun. That benchmarking reports that the investment in thorough front-end loading is around 3 to 5 percent of capital cost and 30 to 40 percent of cycle time, and that projects with the best front-end loading averaged more than four times the net present value per dollar invested of the rest. Schedule pressure is named as the usual reason front-end work is cut, often alongside unclear objectives.

A related distinction is drawn between the owner and the contractor. The owner's responsibility is to specify the right project; the contractor's responsibility is to deliver the project as specified. No amount of delivery excellence can compensate for an owner that has not done the first job. Part of that first job is technical: the Basic Data, the body of scientific information about the reservoir, orebody, plant condition or process on which design rests. If Basic Data is wrong or incomplete, the design cannot be true, and errors cascade into execution. Framing therefore has two faces at the front end: the business question of what the asset must achieve, and the technical question of what is actually known about the conditions it must work in.

4. Why a Thin Story Feels Like a Finished Question

If framing matters so much, why is it so often skipped? Part of the answer lies in how human judgment works. Behavioural research describes a pervasive habit captured in the phrase "what you see is all there is". The fast, intuitive mode of thinking builds the most coherent story it can from whatever information is active in the mind, and treats information that has not been retrieved as if it does not exist. It cannot use what it does not have.

The crucial insight is that subjective confidence depends on the coherence of the story, not on the quantity or quality of the evidence behind it. People rarely ask what important evidence is missing. A thin story, if it hangs together, feels finished. The same mechanism is used to explain a family of related errors, including overconfidence, framing effects, the inside view and the focusing illusion, in which too much weight is placed on whatever happens to be in view.

On a large capital project the effect is easy to recognise. A gate pack that contains only the champion's slides can feel entirely sufficient to the people reviewing it. The missing analysis, the alternative concept that was never studied, the stakeholder whose objection was not recorded: none of these is felt as missing, because none is in view. A clear, confident options paper can therefore create the impression that the question has been settled when it has never been asked.

The same research offers a simple counter-measure. Before a meeting discusses an issue, each participant writes down a short summary of their own view. This prevents the first confident speaker from setting the frame for the whole room, and it surfaces differences in how participants understand the question before those differences are smoothed over by discussion.

5. Same Facts, Different Wording, Different Choice

A second, related body of behavioural evidence concerns the framing effect: the influence of formulation on beliefs and preferences. Logically equivalent descriptions of the same outcome can produce different choices, because intuitive judgment responds to the story a description tells rather than to the underlying facts alone. A gamble described as a chance of losing money attracts fewer takers than the same outcomes described as the price of a lottery ticket; a loss feels worse than a cost.

The best-known demonstration is a public health problem involving 600 people. When one programme is described as saving 200 people for certain, most respondents prefer it to a risky alternative. When the same programme is described as one in which 400 people will die, preferences shift towards the gamble. Physicians shown survival statistics and mortality statistics for the same treatment make different choices without noticing that the information is equivalent. The conclusion drawn from this work is striking: preferences attach to the framed problem, and there is no hidden frame-free preference underneath. Rational choice assumes invariance, meaning the order of preferences should not depend on the description; framing effects violate it.

A further distinction is between narrow and broad framing. Narrow framing treats each risky decision on its own; broad framing considers a set of decisions together. When several choices are being made, broad framing is at least as good, yet people still tend to decide problem by problem. A standing risk policy acts as a broad frame expressed as a rule.

It is important to keep two ideas separate. The framing effect is about how the wording of a single choice alters preference. Decision framing, the subject of this blog, is about which question is being decided in the first place. Both matter on large capital projects. A schedule described as "saving 200 days of float" and the same schedule described as "accepting a 400-day slip on the remaining works" can be the same plan, yet the wording will shape the appetite of the board. Leaders should first own the question, then watch the wording used to present the answer.

6. Name the Live Decision

The most practical step in framing is to name the live decision explicitly. Established consulting problem-solving methods place framing at the very start of the analytical cycle. Framing means defining the boundaries of the problem, breaking it into components and forming an initial hypothesis, before designing analyses, gathering data and interpreting results. The engagement rules that accompany this method begin with identifying the key question, then developing an issue tree, then formulating hypotheses, all before extensive data collection begins.

Practitioner guidance summarises the logic neatly: framing discovers the right question, while solving finds the right answer. A well-framed problem also clarifies who owns it, which metrics matter and which teams must be involved.

On a large capital project, naming the live decision can be reduced to a single sentence that every gate pack, steering paper and options study should open with. That sentence should state:

• The choice: what is being decided, expressed as a choice rather than a topic.
• The owner: who has authority to make and change the decision.
• The timing: by when the decision must be taken, and what depends on it.
• The success criteria: what would count as a good outcome for the business, not only for the package.
• The boundaries: what is in scope for this decision and what is deliberately out.

An analysis request that cannot be connected to such a sentence should be treated with caution. Without a named decision and a named decision owner, analysis tends to expand to fill the available time, and teams optimise inside a question that nobody has agreed.

Figure 2: Naming the live decision in one sentence covering choice, owner, timing, success criteria and boundaries.

7. Start From the Why: Thinking Right to Left

A complementary principle from large-project research is to think from right to left. Picture the project as a series of boxes running from left to right, with the ultimate goal or result in the box on the right. Planning should begin by asking why the project exists and deciding carefully what belongs in that right-hand box. Only then should the left-hand boxes, the means of delivery, be filled in.

The same idea appears under other names: backcasting, theory of change and working backwards from the customer experience to the technology. Its characteristic failure mode is losing sight of the right-hand box, so that passion for a particular solution, design or technology displaces the purpose it was meant to serve. Experienced project leaders use a simple heuristic to guard against this: keep asking "why?" throughout delivery, and check constantly whether current actions are contributing to the result on the right.

Thinking right to left fits within a broader pattern observed in successful projects: think slow, act fast. Planning is relatively cheap and safe; delivery is expensive and dangerous. Taking the time to create a detailed, tested plan increases the chances of quick and effective delivery and keeps the window of risk small. Failed projects tend to follow the opposite pattern, rushing into action and then dragging through proliferating problems. The research database behind this observation reports that only around 8.5 percent of projects met both cost and schedule targets, and only around 0.5 percent met cost, schedule and benefits targets. Whatever the precise figures for any given sector, the message for framing is clear: the slow thinking that matters most is the thinking about what the project is for.

8. Who Owns the Frame?

A decision sentence is only useful if someone has the authority to set it and to change it. Research on the front end of projects distinguishes three roles. The owner, the permanent organisation, defines needs and ultimately derives the strategic benefits. The sponsor is the individual with the fiscal and political commitment, accountable for strategic benefits and linking corporate governance to project governance. The project manager is tasked with delivering the outputs of a specified project; full delivery responsibility typically marks the end of the front end, and in shaping the project manager is often advisory rather than the sole owner of the frame.

Analytics practice reinforces the point by listing, among the first tasks of any problem-framing effort, identifying stakeholders, sponsors and beneficiaries and securing their agreement on the problem before modelling. Consulting practice implies the same: identifying the key question requires an accountable owner of that question within the client organisation, not only an analyst.

Benchmarking of complex industrial projects places clarity of objectives at the very beginning of its sequence of core leadership practices: the team must fully understand the objectives and the trade-offs between them. That clarity is linked to the leader's social and stakeholder skills and to an integrated owner team whose functions are present, empowered and continuous.

Frame ownership is therefore a governance concept. It identifies the person or body that can change the decision sentence and the success criteria. When ownership is absent, consultants, designers and contractors optimise inside an orphaned or politically floating question. When client and consultant are quietly pursuing different questions, the healthier response is to surface the contest explicitly and escalate it to the sponsor or owner forum, rather than averaging the positions into a vague terms of reference or resolving them inside a package schedule meeting.

9. Shaping: When the Question Belongs to a Coalition

On many large capital projects, no single party can own the frame alone. Research on large engineering projects describes a long front-end phase of search, during which sponsors work through issues, build a coalition, secure permits and shape the project. In the sample studied, this search phase averaged 79 months, compared with an average of 49 months for the engineering, procurement and construction sprint that followed. During search, sponsors still have the freedom to change the configuration of the project. Once the sprint begins, that freedom largely disappears.

Benchmarking of industrial projects gives shaping a precise meaning: the process by which all stakeholders are allocated value and, through that allocation, become aligned on project scope during front-end development. Stakeholders are any parties with an enforceable claim on the project's value, whether internal functions with control rights or external partners, governments, communities and other organisations. Shaping complexity sits alongside scope complexity and organisational complexity as a third dimension, and unexpected shaping difficulty is a typical reason a project that began simply becomes complex midstream. Misalignment among joint-venture partners appears as a driver of weak controls and funding delays.

The implication for framing is significant. On a coalition project, the question "what are we deciding?" cannot be answered by the project team in isolation. It is answered through the shaping process, as value is allocated and scope is agreed. A project that freezes scope before shaping is complete has, in effect, chosen an answer before the coalition has agreed on the question. Framing and shaping are two sides of the same front-end work.

Figure 3: The question is shaped during the long front-end search, while the configuration can still change.

10. Structuring the Question: MECE, Issue Trees and the First Hypothesis

Once the question is named and owned, it can be structured. The established consulting toolkit for this step rests on a principle known as MECE: mutually exclusive, collectively exhaustive. A problem is broken into distinct, non-overlapping issues, and the set of issues is checked to ensure that nothing relevant has been overlooked. Nothing is missed and nothing is double-counted.

Two related tools put the principle to work. A logic tree lists all the components of a problem hierarchically, ending in a detailed MECE map of the problem space; there may be more than one valid breakdown, and the one chosen should suit the audience and the analyses to follow. An issue tree is the evolved form, in which each branch is an issue, often phrased as a question, that can be broken into MECE sub-issues. Answering those questions quickly determines whether the initial hypothesis holds. Not every branch needs equal depth: the thinking should be exhaustive, while investigation is selective.

The approach is hypothesis-driven. An initial hypothesis is formed early, from limited facts already known and a short team discussion, not after exhaustive research. The hypothesis sketches a roadmap for research and analysis, saves time, makes decision making more effective and forces early identification of dead ends. It is tested first with a quick and dirty test: list the assumptions that must be true for the hypothesis to hold; if any of them is false, so is the hypothesis, and this can often be established without heavy analysis. When facts later contradict the hypothesis, the rule is to change the hypothesis, not the facts.

Sequence matters. Structuring tools are only useful once the key question is stable enough to structure. If the question keeps dissolving under analysis, the problem lies upstream, in ownership or in context, and more structure will not fix it.

Figure 4: From key question to MECE issue tree, initial hypothesis, quick and dirty test and focused analysis.

11. Wrong Problem, Wrong Estimate, or Contested Context?

Not every troubled decision on a large capital project is a framing failure. Leaders need to distinguish three different situations, because each calls for a different response.

A wrong problem. The decision question itself is wrong, orphaned or contested between parties. The remedy is to stop, name the live decision, confirm its owner and restart the analysis from the question. Better numbers will not help.

A wrong estimate. The question is right, but the forecast inside it is unrealistic. Behavioural research describes two modes of forecasting. The inside view focuses on the case at hand, its objectives, resources and obstacles, and builds scenarios of progress; even conservative inside forecasts tend to be exceedingly optimistic. The outside view, also known as reference-class forecasting, sets aside the details of the project and examines the outcomes of a class of similar projects, then positions the current project within that distribution. Applied with equal skill, the outside view is much more likely to produce a realistic estimate, and its advantage is strongest for novel ventures. One well-known account describes a curriculum team that estimated its own work at 18 to 30 months, learned that comparable efforts often failed to finish and that those that did took 7 to 10 years, ignored that information and finished in 8 years. Large-project research reaches the same point: every project feels unique, yet treating it as "one of those" is the starting point for realistic forecasts.

A contested context. The question cannot be stabilised because the context itself is turbulent, uncertain, novel and ambiguous. Scenario planning research describes such conditions and argues that under them, conventional predict-and-control planning is insufficient and probability may be irrelevant; plausibility becomes the more useful test. Here the remedy is strategic reframing: developing several plausible future contexts and using them to reperceive the present situation. That reframing is a learning loop rather than a single exercise, and its impact typically arrives only after the cycle of reframing and reperception has been completed, sometimes over several iterations. Research on the use of scenarios also observes that what matters is often less the strategy itself than the frame of assumptions it rests on, such as the time horizon, the breadth of factors considered and the balance between competitive and collaborative stances.

These three situations require different tools. Decision framing fixes the question. Reference-class forecasting fixes the estimate. Scenario-based reframing helps leaders work with a context that will not settle. Applying the wrong tool, for example demanding sharper estimates when the question itself is in dispute, wastes effort and can make the decision worse.

Figure 5: Matching the remedy to the failure: decision framing, the outside view or scenario-based reframing.

12. A Framing Discipline for Project Leaders

Framing is not a one-off workshop. It is a discipline that should run through the life of a large capital project, especially through the front end. Drawing the strands together, the following practices offer a practical starting point.

• Open every gate with a decision sentence. State the choice, owner, timing, success criteria and boundaries before any options or data are presented.
• Ask the gate question explicitly. At each steering checkpoint, ask whether the project is still solving the problem named at the previous gate, or a more convenient substitute.
• Reject orphaned analysis. Decline studies and options papers that cannot be traced to a named decision and a named decision owner.
• Escalate frame disputes. Take disagreements about what is being decided to the sponsor or owner forum; do not bury them in schedule recovery plans or package meetings.
• Collect independent views before discussion. Ask participants to write down their view of the question before the meeting, so the first confident voice does not set the frame.
• Ask what a sceptic would still need to see. Make the missing evidence visible in writing, because it will not be felt as missing otherwise.
• Watch the wording. Present key choices in more than one equivalent framing, such as gains and losses, and consider decisions as a portfolio rather than one at a time where that is possible.
• Structure only after the question holds. Use MECE issue trees and hypotheses once the key question is stable; if it keeps dissolving, look upstream.
• Match the tool to the failure. Distinguish wrong problems, wrong estimates and contested contexts before choosing a remedy.
• Keep a decision record. At consequential decisions, write down what is expected to happen and why. Comparing expectation with outcome later distinguishes the quality of the process from the luck of the outcome, and protects against hindsight reconstructing the decision to look better than it was.

Two cautions apply. First, time pressure and acute stress are associated with faster heuristics and lower decision quality, so framing is most likely to be skipped precisely when it matters most. Second, complexity research reminds leaders that many of the issues facing large programmes are adaptive challenges: changing, interactive problems that defy existing solutions and are not resolved by better schedule control alone. For such problems, the quality of the question is often the most powerful lever a leader has. Leadership scholarship that views leadership as the framing of meaning, shaping how others think about and identify with a situation, points in the same direction: setting the frame is itself a central leadership act.

Conclusion

Large capital projects are rarely short of analysis. They are often short of agreement on what the analysis is for. The evidence reviewed here points to a consistent conclusion: outcomes are largely decided at the front end, through definitional choices that are easy to rush and hard to reverse. Human judgment makes a coherent but thin story feel complete, and the wording of a choice can shift preferences without anyone noticing. Coalition projects add a further layer, because the question is shaped through the allocation of value among many parties.

The response is not more analysis but better sequencing. Name the live decision. Confirm who owns it. Fix the purpose before the means. Structure the question once it is stable, test the first hypothesis quickly, and then apply the right tool to the right failure: framing for the wrong problem, the outside view for the wrong estimate and scenario-based reframing for a context that will not settle. Leaders who decide the question first give every subsequent choice on a large capital project a far better chance of being the right one.

References

1. Ackoff, R. L. (2004). Transforming the systems movement. The Systems Thinker. https://thesystemsthinker.com/transforming-the-systems-movement/
2. Allen, P., Maguire, S., & McKelvey, B. (Eds.). (2011). The SAGE Handbook of Complexity and Management. SAGE Publications.
3. Bailey, K. (2026). Problem framing in strategy. Corporate Finance Institute. https://corporatefinanceinstitute.com/resources/strategy/problem-framing/
4. Bryman, A., Collinson, D., Grint, K., Jackson, B., & Uhl-Bien, M. (Eds.). (2011). The SAGE Handbook of Leadership. SAGE Publications.
5. Farnam Street. (n.d.). The decision journal. Farnam Street.
6. Flyvbjerg, B., & Gardner, D. (2023). How Big Things Get Done. Currency.
7. Friga, P. N. (2009). The McKinsey Engagement: A Powerful Toolkit for More Efficient and Effective Team Problem Solving. McGraw-Hill.
8. INFORMS. (2024). INFORMS Analytics Framework: Explore. Institute for Operations Research and the Management Sciences. https://www.informs.org/Professional-Development/INFORMS-Analytics-Framework/Explore
9. Kahneman, D. (2011). Thinking, Fast and Slow. Farrar, Straus and Giroux.
10. Klein, G. (2007). Performing a project premortem. Harvard Business Review, 85(9).
11. Lovallo, D., & Kahneman, D. (2003). Delusions of success: How optimism undermines executives' decisions. Harvard Business Review, 81(7), 56–63.
12. Merrow, E. W. (2024). Industrial Megaprojects: Concepts, Strategies, and Practices for Success (2nd ed.). John Wiley & Sons.
13. Merrow, E. W., & Nandurdikar, N. S. (2018). Leading Complex Projects: A Data-Driven Approach to Mastering the Human Side of Project Management. John Wiley & Sons.
14. Miller, R., & Lessard, D. R. (2000). The Strategic Management of Large Engineering Projects: Shaping Institutions, Risks, and Governance. MIT Press.
15. Ramírez, R., Churchhouse, S., Palermo, A., & Hoffmann, J. (2017). Using scenario planning to reshape strategy. MIT Sloan Management Review, 58(4).
16. Ramírez, R., & Wilkinson, A. (2016). Strategic Reframing: The Oxford Scenario Planning Approach. Oxford University Press.
17. Rasiel, E. M., & Friga, P. N. (2002). The McKinsey Mind: Understanding and Implementing the Problem-Solving Tools and Management Techniques of the World's Top Strategic Consulting Firm. McGraw-Hill.
18. The Decision Lab. (n.d.). Framing effect. The Decision Lab.
19. Tversky, A., & Kahneman, D. (1981). The framing of decisions and the psychology of choice. Science, 211(4481), 453–458.
20. Williams, T., Vo, H., Edkins, A., & Samset, K. (2019). A Systematic Literature Review: The Front End of Projects. Project Management Institute.