A project can be tightly controlled and still be the wrong investment for the organisation.
When a major initiative begins to slip, the instinctive response is often operational: increase reporting, tighten controls, replace the schedule, add assurance, escalate suppliers and ask the project team for a recovery plan.
Sometimes that is exactly what is required.
But sometimes the project team is being asked to recover from a decision that was structurally weak before delivery began. The organisation may have pursued the wrong market, accepted the wrong contract, concentrated too much exposure with one client, authorised more work than its capability could absorb or committed to economics that were never realistic.
In those situations, additional project control may improve visibility without improving the investment.
The Strategic Context
Boston Consulting Group's 2011 Large-Project Management: A Blueprint for Success argued for a three-tier perspective on large-project performance: strategic planning, portfolio management and project management. Its simple logic remains useful because it separates three different executive responsibilities.
Strategy decides where the enterprise wants to compete and what kinds of opportunities it is prepared to pursue. Portfolio management decides which opportunities to select, how much aggregate exposure to accept and how to steer the set of commitments. Project management then delivers individual initiatives.
The distinction can be expressed as select, steer and deliver.
Failure can originate at any of those levels.
That matters because organisations often diagnose a problem at the level where its symptoms appear rather than the level where its cause was created. A project showing cost pressure may indeed have poor cost control. It may also have been underpriced, poorly scoped or exposed to a risk profile the organisation should never have accepted.
A recovery plan that attacks the symptom but protects the original assumption can make the eventual loss larger.
What Leaders Commonly Misread
The most common misread is that a red project status automatically indicates a delivery problem.
Project controls are designed to answer questions such as: Are we on schedule? Are costs within forecast? Are risks changing? Are deliverables progressing? Is the supplier performing?
Those are necessary questions, but they do not answer the upstream question:
Should the organisation still want this project under the conditions that now exist?
The BCG source describes companies responding to difficult project environments by strengthening manuals, audits, controls, KPIs, reporting and contractual protections. The report's caution is that these measures can fall short when the root causes are strategic, operational or behavioural rather than procedural.
This is a powerful executive warning. Control can become a substitute for judgement.
When leaders are uncomfortable reconsidering the original investment decision, they may ask project teams to produce increasingly detailed evidence that execution will somehow restore the initial promise.
Related article: Portfolio Management Is Capital Allocation in Action
Reframing the Issue
A troubled project should be treated as a portfolio hypothesis under review, not merely a delivery variance to be corrected.
The leadership task is to identify where the problem originated.
There are at least three layers.
Strategic selection failure
The enterprise may have chosen an unattractive market, client, geography, technology or risk position. The project is then carrying a strategic error.
Examples include entering a market where the organisation has no defensible advantage, accepting a customer whose contractual behaviour destroys margin, or pursuing a technology simply because competitors are doing so.
The project team cannot control these conditions away.
Portfolio construction failure
The individual project may be reasonable, but the portfolio may not be.
A business can accept too many large projects at once, concentrate exposure in one customer or region, create an unhealthy contract mix, overload a scarce technical function or consume so much leadership attention that execution quality falls across the portfolio.
From a single-project perspective, every initiative may appear defensible. At portfolio level, the combined system is fragile.
Related article: Capacity Is a Strategic Constraint: Match Ambition to What the Organisation Can Absorb
Execution failure
Some problems are genuinely local. Planning may be weak. Engineering interfaces may be poorly managed. Procurement may be late. Roles may be unclear. Risk ownership may be inadequate. Supplier performance may deteriorate.
These problems belong in the project-management system and should be corrected there.
The mistake is not using project control. The mistake is assuming every failure originates in execution.
Why More Control Can Make the Wrong Bet Harder to Stop
When a project is already politically important, highly visible or financially significant, more governance activity can create an illusion of recoverability.
Each new review produces another recovery milestone. Each recovery milestone creates a reason to wait. Additional sunk cost can then strengthen the emotional case for continuing.
The organisation becomes better at monitoring deterioration while becoming worse at changing course.
This is especially dangerous where project termination is culturally treated as failure. The supplied BCG/PMI practitioner material makes the opposite point: strong portfolio cultures are willing to discontinue initiatives when necessary and do not punish people for surfacing concerns.
A mature governance system therefore asks two questions in parallel:
Can this project be recovered?
and
Should this project be recovered?
Those are not the same decision.
The Portfolio View of Risk
The BCG large-project report also argues for a portfolio-wide risk view rather than isolated project reporting. The strategic value of that idea is not a particular scoring model. It is the ability to see aggregate exposure.
Leaders should be able to answer questions such as:
- How much revenue depends on a small number of clients?
- How much margin is exposed to fixed-price contracts?
- Which projects rely on the same scarce technical experts?
- How much execution risk is concentrated in one region or supplier?
- How many major initiatives are entering their most resource-intensive phase at the same time?
A project may be acceptable in isolation and still be unacceptable as the next addition to the portfolio.
That is why project approval cannot be reduced to “Does this business case work?” The harder question is “What happens to the enterprise's total risk and capability position if we add this commitment?”
Related article: Risk Transparency Is Not Risk Control: Build Portfolio Coping Capacity
Decision Framework
When a major initiative deteriorates, use a three-level failure-origin test.
1. Strategy. Has the attractiveness of the market, client, technology, geography or commercial model changed? Were our original assumptions valid?
2. Portfolio. Is the initiative still the best use of scarce capital, capability and executive attention given the rest of the portfolio? Has aggregate risk become too concentrated?
3. Project. Are the remaining problems primarily matters of planning, execution, governance, interfaces, suppliers, scope or risk management that can realistically be corrected?
Then classify the response.
- If the strategy remains valid and the project problem is recoverable, intervene operationally.
- If the project is attractive but the portfolio is overloaded, resequence or reallocate resources.
- If the strategic economics have deteriorated, redesign, renegotiate or exit.
- If capability is the constraint, decide explicitly whether the capability should be built, bought, partnered or the commitment reduced.
- If uncertainty is too high to justify full continuation, create a bounded decision point rather than funding indefinite recovery.
The discipline is to match the level of intervention to the level of the problem.
From Strategy to Execution
Immediate action begins by separating project status from investment status. For material initiatives, add a portfolio-level review that tests whether the original strategic and economic assumptions remain valid.
Medium-term capability building should integrate project risk, contract exposure, resource concentration and strategic fit into portfolio reviews. Project dashboards should not be the only evidence available to executives. Leaders need a synthetic view of what the portfolio is becoming.
Long-term strategic positioning requires learning from failure origins. If the same contract type repeatedly underperforms, the problem may be commercial strategy. If the same capability bottleneck appears across projects, the issue is organisational investment. If every downturn produces low-price commitments that later destroy margin, the problem is portfolio discipline.
The organisation should improve not only how it delivers projects, but how it chooses them.
Signals to Monitor
Warning signs that a project problem may actually be an upstream portfolio problem include:
- recovery plans repeatedly assume additional scarce resources that do not exist;
- profitability depends on optimistic future variations or claims;
- multiple projects are competing for the same critical capability;
- leadership attention is concentrated on rescuing one initiative while other strategic work deteriorates;
- contractual or market conditions have changed materially since approval;
- the business case survives only because sunk cost is treated as a reason to continue;
- project controls become more detailed while the strategic rationale becomes less clear.
These signals should trigger reconsideration, not merely another reporting cycle.
Questions for the Leadership Team
- Which of our current red projects are execution problems, and which are symptoms of poor selection or portfolio overreach?
- Are we prepared to revisit the original strategic assumptions when a major project deteriorates?
- Where is risk concentrated across clients, contract types, geographies, technologies and scarce capabilities?
- Do our recovery decisions consider opportunity cost, or only the money already spent?
- What portfolio conditions would cause us to stop, renegotiate or materially redesign an initiative?
- Are project teams being held accountable for structural choices that were made above the project level?
Closing Perspective
Project controls are essential, but they operate inside a boundary created by strategy and portfolio choice.
When that boundary is sound, disciplined delivery can protect value. When the original bet is poor, stronger control may simply produce a more precise record of value destruction.
Executive leadership therefore has to do more than ask whether projects are being managed well. It must keep asking whether the organisation is still managing the right projects at all.
About EraNorth Insights
EraNorth Insights publishes practical analysis on strategy, projects, operations, transformation and decision intelligence for professional and organisational use. About EraNorth.