Project management, Project Portfolio Management

Project success rate: why Standish data points to the sponsor, not the project manager

The single most-cited number in project management is Standish Group’s “31% of projects succeed.” It tends to surface in PMO presentations as a benchmark of the discipline’s overall performance. What the same report shows underneath the headline number is more useful for PMO leaders making operational decisions: project success rate moves from 18% to 67% depending on one variable, the maturity of the executive sponsor. Sponsor maturity does more work than methodology, tooling, or project manager experience combined.

This article looks at what that gap actually means in operational terms, what Standish CHAOS 2020 and Wellingtone 2024 say together about the conditions in which sponsors decide, and how FlexiProject’s Acceptance paths, Project Condition, and Portfolio Reports work together to turn the sponsor from a passive escalation point into an active decision-maker.

In this article, you will learn: What Standish CHAOS 2020 actually measures and why the “challenged” category matters more than the headline number Why executive sponsor maturity moves project success rate from 18% to 67%, and what “mature sponsor” means operationally How Wellingtone 2024 data on baselines, KPIs, and manual reporting frames the conditions in which sponsors make decisions Three structural failure modes of sponsor governance: decision latency, visibility gap, and baseline drift How FlexiProject’s Acceptance paths, Project Condition, and Portfolio Reports work as one system to support sponsor-level decisions

What Standish CHAOS 2020 actually measures

The Standish Group has been publishing the CHAOS report since 1994, and the 2020 edition, Beyond Infinity, uses what the authors call “modern measurement”: a four-dimension definition of project success covering on-time delivery, on-budget delivery, target outcome achievement, and customer satisfaction. Under this measurement, applied to software projects, 31% of projects are classified as successful, 50% as challenged, and 19% as failed. The headline number, 31%, gets cited most often, but for PMO leaders the more operationally relevant category is the middle one. “Challenged” means the project was delivered, but with material deviation from one or more baseline dimensions. That category is where most PMO budgets actually go.

The three outcome categories explained

Standish’s “successful” requires all four dimensions to land within tolerance: schedule, budget, target outcomes, and customer satisfaction. “Failed” means the project was cancelled before delivery or delivered but never used. “Challenged”, by far the largest category at 50%, covers the operationally common case: the project shipped, but late, over budget, with reduced scope, or with weak business outcomes. For a PMO running 30 projects, this translates to roughly 15 projects per year that consume full resources but produce partial value. The “challenged” rate is the realistic target for PMO improvement work, since moving projects from challenged to successful is more tractable than rescuing failures.

Why the 31% number matters for PMOs, not just for IT teams

Standish’s sample focuses on software projects, which has led some PMO leaders to dismiss the data as irrelevant to construction, R&D, or business transformation portfolios. The dismissal misses the point. The patterns that produce “challenged” outcomes – late decisions, missing baselines, weak sponsor engagement, ambiguous scope changes – are not industry-specific. They are governance patterns. Standish data on software projects is the most quantitatively rigorous picture we have of how those patterns affect outcomes. A PMO managing capital projects, regulatory programs, or product launches will recognize the same patterns in its own portfolio reviews.

The single biggest lever: executive sponsor maturity (67% vs 18%)

When Standish segments its data by executive sponsor maturity, the project success rate moves from 18% to 67%, a 3.7x multiplier. No other single factor in the dataset produces a comparable effect. Methodology choice (waterfall vs agile vs hybrid), team experience level, project size, and tool sophistication all show smaller, less consistent correlations. The sponsor variable dominates them all. For a PMO leader reading the data, this has a direct implication: the highest-leverage operational investment is not in upgrading project managers or selecting better methodology: it is in building the system around executive sponsor decisions.

What “highly mature sponsor” means in practice

The Standish definition of sponsor maturity is behavioural, not titular. A highly mature sponsor does four things consistently across the project lifecycle. First, decisions move within days rather than weeks, change requests, scope adjustments, and risk responses are not held for monthly steering committees. Second, the sponsor owns the business case actively, including its evolution as conditions change, not just at kickoff. Third, project reviews are based on data from the system rather than on PowerPoint summaries prepared by the project manager. Fourth, the sponsor signs off on the baseline plan as a strategic commitment, with the same seriousness as a capital allocation decision. None of these behaviours require a specific job title: they require role discipline and system support.

Why the project manager cannot compensate for a low-maturity sponsor

A common reaction from PMO leaders looking at this data is to invest in better project managers, on the assumption that a strong PM can compensate for a weak sponsor. The structural asymmetry of the two roles makes this impossible at portfolio scale. The project manager has operational authority: running the plan, coordinating the team, escalating risks. The sponsor has strategic authority: reprioritizing the portfolio, allocating budget, approving scope changes that exceed PM tolerance. When the strategic decisions take three to four weeks to land, the PM can run the plan flawlessly and still produce a “challenged” outcome. The Standish data confirms this at scale: PM excellence cannot substitute for sponsor decision speed.

What Wellingtone 2024 adds to the picture: baselines, KPIs, reporting

The Standish number tells PMO leaders that sponsor maturity matters. Wellingtone’s State of Project Management 2024 tells them why most sponsors operate below maturity in the first place, because the conditions for mature decision-making are not in place. Wellingtone reports that only 34% of organizations usually or always complete projects on time, 34% on budget, and 36% deliver full benefits. The data on the system conditions behind those outcomes is the more useful part of the report: only 48% of organizations usually or always baseline their schedules, around half do not have access to real-time KPIs, and at least one day per month is spent manually building status reports.

Sponsors decide on stale data, and it shows in the success rate

When half of PMO operations produce manual status reports once a month, the sponsor is structurally three to four weeks behind project reality. A risk flagged in week two of a four-week reporting cycle reaches the sponsor in week six. By the time the steering committee discusses it, the risk has either materialized or self-resolved, either way, the sponsor’s decision arrives too late to change the trajectory. The same pattern applies to scope changes, budget overruns, and resource conflicts. The Standish 18%-to-67% gap is not primarily about sponsor talent or commitment. It is about whether the system feeds the sponsor current data fast enough to make timely decisions.

Three structural failure modes of sponsor governance

The combined Standish and Wellingtone data isolates three operational gaps that produce most of the project success rate degradation. They show up in PMO diagnostics consistently, and each one disables a different layer of sponsor effectiveness. None of them are a question of sponsor intent or skill: they are system gaps that the PMO is responsible for closing. The next three sections diagnose each gap; sections six through eight describe the operational response.

Decision latency: when “we’ll discuss it next steering” costs weeks

Most PMOs operate on a monthly steering rhythm, which means the average decision cycle for sponsor-level questions is two weeks. A scope change identified in week one waits for the meeting at week three; if the meeting defers the decision for additional analysis, the answer lands at week seven. For projects with eight-to-twelve week phases, this single delay can consume 50% of a phase. The Standish data on sponsor maturity captures this: organizations with mature sponsors have decision cycles measured in days, not weeks, because they do not bundle every decision into a monthly forum. The forum still exists, it just stops being the only path to sponsor approval.

Visibility gap: sponsors look at slides, not at the system

When 50% of PMOs report that real-time KPI access is unavailable to leadership, the sponsor’s view of the portfolio is filtered entirely through PM-prepared materials. This creates a structural distortion: the sponsor sees the version of project state that the PM chose to surface, after PM-led prioritization of what is worth raising. Important signals get smoothed out, ambiguous risks get phrased optimistically, and the sponsor’s strategic decisions rest on curated rather than direct data. Mature sponsors close this gap not by demanding more reports, but by accessing the system themselves, looking at current project condition, risk register, and budget status without intermediaries.

Baseline drift: when “the plan” means “the latest schedule”

Wellingtone’s finding that only 48% of organizations consistently baseline their schedules has a direct consequence: in 52% of PMOs, “on plan” means “on the current version of the plan.” Without a frozen reference point that requires formal change control to modify, every status report describes the present rather than deviation from a strategic commitment. The sponsor’s decision space collapses, because there is nothing to decide against: the plan keeps adjusting to reality rather than reality being managed against the plan. This is the most quietly damaging of the three gaps, because it makes the other two harder to detect. A clean status report with no baseline is not actually green.

What mature sponsors do differently across the project lifecycle

Sponsor maturity is not a personality trait or a leadership style: it is a set of operational behaviours tied to specific moments in the project lifecycle. Four moments matter most: Project Charter approval, baseline approval, mid-project reviews, and change request decisions. At each moment, the mature sponsor does something structurally different from the immature one, and the difference compounds across the portfolio. The PMO’s role is not to coach sponsors into better behaviours: it is to design the system so that mature behaviours are the path of least resistance and immature behaviours produce friction.

Charter approval as a strategic gate, not a formality

The Project Charter is the first concrete moment where sponsor maturity is observable. An immature sponsor signs the Charter as a procedural step, after the project has been substantially scoped and the team mobilized. A mature sponsor treats Charter approval as the investment decision it actually is: reviewing the business case, the target outcomes, the resource commitment, and the assumptions that justify proceeding. Standish data shows that projects with active sponsor engagement at Charter stage have substantially higher success rates than those where Charter approval is reduced to a signature workflow. The Charter is the cheapest place to kill a weak project; once execution starts, the cost of stopping rises every week.

Mid-project reviews tied to risk and budget data, not opinions

The format of the sponsor-PM review changes the quality of decisions that come out of it. When the review is structured around a status deck – slides prepared by the PM, narrative led by the PM, decisions framed by the PM – the sponsor’s contribution is limited to reacting to what was presented. When the review is structured around the system itself – current project condition, live risk register, baseline-to-actual variance – the sponsor’s contribution shifts to identifying what is missing, questioning assumptions, and triggering decisions that the PM could not raise alone. The shift is small in operational terms but large in outcome terms over a portfolio.

How FlexiProject's Acceptance paths cut decision latency

Decision latency is the most directly addressable of the three sponsor governance gaps, because it is fundamentally a workflow problem rather than a behavioural one. FlexiProject‘s Acceptance paths provide a predefined decision-making process for approving key project documents: Project Charter, Project Plan, baseline changes. Rather than holding decisions for the next steering committee, the approval routes asynchronously through the predefined sequence of approvers, with each decision recorded with timestamp and approver identity. The monthly steering meeting still exists for strategic discussions; what changes is that routine sponsor-level approvals stop blocking project progress between meetings.

Decisions move asynchronously, with an audit trail

Each Acceptance path is configured per workspace, so different business units can have different approval routes for the same document type. The path defines the sequence of approvers, the conditions for moving to the next step, and the actions available at each step (approve, reject, request changes). When a Project Plan is submitted for approval, it routes through the sequence automatically, each approver sees the document in their queue, makes the decision, and the next approver is notified. The full audit trail is preserved, which matters both for compliance and for diagnosing where decisions slow down. If a particular approver consistently holds documents for two weeks, the data is visible, and the PMO can address the bottleneck directly.

Approval routes mapped to project size and risk

The strength of predefined approval routes is that they can be calibrated to project scale. A small initiative might require single-approver sign-off from the PMO lead. A large or high-risk project might route through PMO, finance, and executive sponsor in sequence, with conditional branches based on budget thresholds or risk categories. The routes are configurable per workspace, which lets different business units adapt the governance model to their context without requiring central reconfiguration for each project. The result is that sponsor attention is concentrated on the decisions that genuinely require it, while routine approvals do not consume sponsor time.

Project Condition and Graphical Summary as the sponsor's own view

The visibility gap closes when sponsors can access current project state directly, without depending on PM-prepared materials. FlexiProject’s Project Condition provides a status view of each project covering schedule, budget, scope, and risk dimensions, refreshed continuously as the underlying data changes. The Graphical Summary aggregates this into a portfolio-level visualization that a sponsor can scan in minutes. Together, these two views replace the cycle of preparing, distributing, and discussing monthly status decks with continuous access to current state, which means sponsor decisions can be triggered by signals rather than by reporting calendars.

From monthly status decks to always-current condition signals

The post on automation of project reviews covers the operational shift in detail: status reports stop being a separate artefact produced for sponsors and become a continuous view that sponsors access directly. The Project Condition view shows where each project stands across the four key dimensions, with drill-down to the specific tasks, risks, or budget lines that are driving the status. A sponsor reviewing portfolio condition before a Tuesday morning decision sees Monday’s data, not data from three weeks ago. The decisions that emerge are faster, more targeted, and more likely to address actual rather than reported issues.

Portfolio Reports: from project signal to portfolio decision

Sponsor effectiveness scales when individual project signals can be aggregated into portfolio decisions. A single project showing red risk status is a project-level question; three projects in the same business unit showing red status is a portfolio-level question requiring resource reallocation, scope rebalancing, or strategic deferral. FlexiProject’s Reports and Project portfolios modules provide the aggregation layer, letting sponsors and PMO leaders see patterns across projects that would not be visible in individual project reviews. This is where organizations with the highest project success rate in Standish data operate, at the portfolio level, with the project level as input rather than as the unit of decision.

When a single project signal becomes a portfolio question

The transition from project-level to portfolio-level decisions is what separates mature from immature governance. An immature governance model handles each project’s risks, delays, and budget pressures in isolation, escalating to the sponsor when individual projects exceed tolerance. A mature model uses portfolio reports to detect patterns: three pharmaceutical projects all flagging clinical trial delays, two infrastructure projects competing for the same critical resource, four product launches all forecasting Q4 completion against a shared launch window. These patterns are invisible at the project level and obvious at the portfolio level, but only if the system aggregates the signals in real time, not at quarter end.

Frequently asked questions (FAQ)

Does the executive sponsor have to be at C-level?

The Standish definition of sponsor maturity is behavioural, not hierarchical. A director-level sponsor with strong role discipline – fast decisions, active business case ownership, system-based reviews – produces better project outcomes than a C-level sponsor who treats the role as ceremonial. What matters is whether the sponsor has the authority to make the strategic decisions the project requires, and the discipline to make them within the right timeframe. Some organizations assign C-level sponsorship to all major projects; others tier sponsorship by project size and risk. Both models work, provided the sponsor at whatever level operates with maturity.

How often should a sponsor review a project?

For active projects, a bi-weekly cadence between the project manager and sponsor works in most environments: fast enough to surface risks before they escalate, slow enough to avoid drowning the sponsor in operational detail. The portfolio-level review can run monthly, because portfolio decisions operate on a longer time horizon than project decisions. What matters more than the cadence is that the reviews are tied to system data rather than to prepared materials, and that the sponsor has access to current project condition between scheduled reviews when escalation is needed.

Do Acceptance paths replace the steering committee?

No, they complement it. The steering committee remains the forum for strategic discussions: portfolio reprioritization, major scope changes, executive-level escalations. What Acceptance paths replace is the practice of bundling routine sponsor-level approvals into the same monthly meeting, which creates the decision latency problem. With approval routes in place, the steering committee can focus on the small number of decisions that genuinely require collective discussion, while the larger volume of individual approvals moves continuously through the system.

What if the sponsor “doesn’t have time”?

The “no time” response usually signals one of two underlying issues: either the sponsor is overloaded with approval requests that should be handled at a lower level, or the system makes individual approvals more time-consuming than they need to be. Acceptance paths address both: they route routine decisions away from sponsor level where possible, and they make the remaining sponsor-level decisions fast to process because the relevant context is attached to the approval request. When a sponsor can approve a baseline change in two minutes from a mobile device with full context visible, the “no time” objection stops applying.

Does this change require an organizational culture shift?

Less than PMO leaders often assume. The Standish data shows the operational mechanism: decision speed, baseline discipline, system-based reviews. These are workflow choices, not cultural ones. Organizations that change the workflow – implementing approval routes, baseline approval gates, direct sponsor access to project condition – find that sponsor behaviours adjust to fit the new system within one or two quarters. The cultural narrative of “more engaged sponsors” tends to follow the operational change rather than precede it.

Project success is a sponsor system problem, not a PM problem

The Standish CHAOS 2020 finding that mature sponsorship moves project success rate from 18% to 67% reframes what PMO improvement work should focus on. The conventional emphasis on better project managers, better methodology selection, or better tool features captures real but secondary effects. The dominant variable is the system around executive sponsor decisions: whether decisions happen in days or weeks, whether sponsors see current data or curated reports, whether baselines hold or drift. Wellingtone 2024 data on manual reporting, missing baselines, and absent real-time KPIs describes the operational conditions in which most sponsors currently work, and those conditions structurally prevent the maturity that Standish identifies as the success driver.

The strongest PMO initiatives are not the ones that add a fourth tool to patch a gap in the third. They are the ones that operate decision routing, project condition visibility, and portfolio aggregation as a single coherent system, with shared data, shared cadence, and clear ownership of where strategic decisions get made. FlexiProject combines Acceptance paths, Project Condition with Graphical Summary, and Portfolio Reports in one platform precisely because the sponsor-maturity problem is a system problem, not three separate workflow problems. The success-rate gap that Standish documents is closed not by individual heroism at sponsor level, but by infrastructure that makes mature sponsor behaviour the default path.