Collection points
Decision latency; resource conflicts and queues; switching costs; zombie projects; planning overhead — plus two shadow levies (alignment drift and benefit evaporation).
Whitepaper · August 2026
The Hidden Decision Tax.One dollar in five.
How decision latency, resource conflicts, switching costs and zombie projects quietly take about one dollar in five from project portfolios — and how to measure your own rate.
Executive summary
Every project portfolio pays a tax that appears on no budget line.
It is not a visible cost item attached to a project that fails; write-offs get counted, eventually. It is the recurring, structural levy collected by four mechanisms that standard project management reporting cannot see: work that continues while a stop decision waits to be made; people and teams idling in queues for contended resources; productivity burned in switching between too many concurrent assignments; and projects that nobody can kill because no one can justify the decision without an alternative scenario. A fifth levy — the planning machine itself: annual cycles, recurring reviews, and the replanning cascades that follow every unplanned change — bills its meeting hours on top, even in an agile system.
We call this
The hiddendecision tax
The hidden decision tax at a glance
Roughly one dollar in five of annual portfolio spend
The evidence assembled here estimates the combined levy at roughly one dollar in five of annual portfolio spend for a typical large organization — about 10% in the conservative case, 30% or more where portfolio maturity is low.
≈21%of annual portfolio spend for a typical large organization (central estimate)
≈10%conservative case
≈34%in low-maturity portfolios
17–23%central rate if the overlap adjustment runs 15–40%
Why you don’t see it
Each levy is booked as normal project variance — overruns, delays, “resourcing challenges” — never as the portfolio-level design flaw it is.
How to see it
Five meters computable from data you already hold. Most organizations can produce a defensible first estimate in one week and a full assessment in four to six weeks.
This tax is significant on transformation and technology portfolios, where dependencies are densest, specialist resources are scarcest, and business cases decay fastest, but it is not confined to them. Any portfolio that runs on annual funding decisions, shared resources and executive sponsorship pays it: capital programs, product development, R&D pipelines, even M&A integration.
A systematic issue
This tax is avoidable, not a series of accidents
When a project fails, executives typically hear the following excuses: the vendor underdelivered, the requirements moved, the sponsor left. Portfolio reviews process these stories one at a time, as unavoidable events, from a reactive lens. However, the evidence points to a systematic issue beyond luck or fortune.
45%over budget on average for large IT projects
56%less value delivered than predicted
17%overrunning so badly (200–400%) that they threatened the company’s survival
The joint McKinsey–University of Oxford study of more than 5,400 IT projects — still the largest project-level database assembled [1].
Failure rates at this level, stable across decades, technologies and methodologies, are not a run of bad luck. They became part of the planning ecosystem for many organizations. The tax metaphor makes this systematic issue very clear.
- A tax is recurring — it collects every year, not just in bad years.
- It is proportional — a bigger portfolio pays more, automatically.
- It is collected silently — distributed across hundreds of status reports as small delays, partial allocations and quiet extensions, never aggregated into a single number anyone must defend, and not owned by a single team.
- It is levied on successful portfolios too: an organization can deliver every project and still pay 15% in latency, queues, switching and zombies along the way, because the tax is charged on how the portfolio runs, not on whether individual projects land.
Failure is not the tax. A portfolio with zero write-offs is under-ambitious — cheap, fast-failing exploration is the price of option value, and abandoning proofs of concept that lack clear business value is healthy behavior. The tax is narrower: spend that continues after the information to stop was available, capacity consumed by avoidable contention, replanning and switching, and projects sustained by inertia rather than by a business case that would survive re-approval. That is why this paper prices mechanisms, not failures.
The levies
The tax hides well because each mechanism disguises itself as something respectable.
Four mechanisms do most of the collecting, and a fifth — the planning machine itself — bills for the time spent operating them.
Levy 2.1
Decision latency
Paying full burn on the already-decided
Between the moment the information to stop, redirect or downsize an initiative exists and the moment the decision lands, the initiative burns at full rate.
How it hides: spend during decision latency looks like perseverance.
Evidence: McKinsey’s resource-reallocation research found a third of companies move only about 1% of capital year to year (the average is 8%) [19].
2–8%of portfolio spend, central ≈4%
Levy 2.2
Resource conflicts
The queue tax
When more initiatives are approved than the shared resources can serve, queues form. At the portfolio level the queues interlock. No one is idle, nothing moves — the project-portfolio version of a deadlock, invisible to any single project’s status report because each one truthfully reports “waiting on another team.”
How it hides: queue time looks like dependencies being managed.
Evidence: in the only sizeable published measurement of delivery flow — 63 software teams tracked over twelve months — work items were actively progressing for just 35% of their elapsed life on average; the other two-thirds was waiting [17].
2–7%of portfolio spend, central ≈4%
Levy 2.3
Switching costs
The tax that looks like productivity
Overloaded portfolios respond to scarcity by splitting people: 40% here, 30% there, 30% on “run.”
How it hides: context switching looks like high utilization — everyone is busy.
Evidence: engineers working on two or more projects spend an average of 17% of their effort on cross-project interruptions, per a 2017 empirical study built on developer effort reports [14].
3–10%of portfolio spend, central ≈6%
Levy 2.4
Zombie projects
The tax on the unkillable
Some projects are dead — in value, progress or strategic relevance — and keep collecting funding anyway, because in most organizations stopping requires a stronger case than starting. Zombies are what decision latency becomes when the decision never arrives.
How it hides: zombie projects look like commitment.
Evidence: the landmark MIS Quarterly escalation study (2000, ~600 IS audit professionals): 30–40% of IS projects escalate — absorb resources despite failing performance [10].
3–10%of portfolio spend, central ≈6%
Levy 2.5
Planning overhead
What the machine itself taxes
The four levies price what the portfolio’s decision system fails to do. This one prices what running this planning system costs.
The bill: real, recurring, paid in the scarcest currency the organization has (senior attention), and almost never totaled.
Evidence: APQC’s benchmark of 2,617 organizations shows annual budget cycles of 28 days or less for the top quartile versus 56 days or more for the bottom [25].
The load lands on the most expensive people: executives average about 23 hours a week in meetings, and in the underlying survey of 182 senior managers, 71% called their own meetings unproductive [23]. Even the paperwork is measurable: 72% of project professionals spend half a day or more every month just collating status reports [13].
0.5–3%of portfolio spend, central ≈1.5% — the smallest levy in the model, and the only one visible in a calendar export
Shadow levies 2.6
Alignment drift and benefit evaporation
Two further mechanisms collect alongside the four
Alignment drift happens when company strategy moves and part of project work does not follow. Benefit evaporation: business cases are written to win funding, then never revisited.
Priced conservatively: only the slice of spend justified by benefits nobody tracks or objectives no longer current.
Evidence: PMI found fewer than half of organizations reporting high alignment between projects and strategy [3].
3–10%of portfolio spend, central ≈6%
2.7 · How the levies compound
The levies are one system.
Overload creates contention (2.2) and fragmentation (2.3); fragmentation and queues stretch durations, which raises cost 15% per added year [1] and multiplies the exposure window for strategy change; longer, staler initiatives are harder to justify and harder to kill (2.4); unkilled zombies hold the very resources whose scarcity created the queues; and every quarter of decision latency (2.1) holds the whole loop in place.
Volatility feeds the machine too: every unabsorbed change triggers a replanning cascade (2.5), whose meetings consume the very capacity that would have delivered the work. This is why point remedies disappoint: a WIP limit without faster kill decisions just queues the zombies; faster kills without reallocation just strand the freed capacity.
The tax is levied by the loop, and it is cut by breaking the loop — which is a portfolio-design decision, not a project-management one.
The evidence
The outcome data show what the disguises cost
Every figure is cited to a named source with its type and limitations stated.
48%of digital initiatives meet their business outcome targets
Gartner, 2025 CIO and Technology Executive Survey: 3,186 CIOs and technology executives, 88 countries [6]
51%of U.S. technology executives saw no performance gain from transformation investment within 24 months
KPMG, 2023 U.S. Technology Survey: 400 U.S. technology executives [7]
9.7–13.5%of every project dollar wasted through poor project performance alone
PMI, four editions, 2013–2018 [2][3][4]. A floor that captures the visible failures but not the slower leaks this paper prices.
20%of strategic objectives missed through implementation failure
Economist Intelligence Unit, survey of 500 senior executives [5]
38%of companies capture less than half of targeted transformation value
Bain & Company: 2016 survey of roughly 300 companies; Harvard Business Review, 2024 [8]
About the evidence. Sources are named with year, sample and method where disclosed; academic and peer-reviewed inputs [1][10][14][15] carry the most weight. Most portfolio evidence is survey-based, not audited — and most of its producers sell remedies, an interest that runs toward larger estimates. Self-reporting biases the other way (85% of executives believe their organizations deliver projects effectively, against the measured record [3]). Ranges are used throughout; exposure measures (“spend at risk”) are kept distinct from realized losses; and maturity comparisons are associations from self-reported cross-sections, not proofs of causation.
The tax-rate model
The rate: how big is the tax?
Each levy carries a conservative, central and high estimate. Because the levies co-occur and partially price the same dollars — a zombie staffed by multi-assigned people queuing for environments is one pot of money — the raw sum is reduced by a 25–30% overlap adjustment before quoting a combined rate.
| Levy | Conservative | Central | High | Evidence base and construction |
|---|---|---|---|---|
| 2.1 Decision latency | 2% | 4% | 8% | 10–25% of spend re-decided yearly × 2–6 months of full burn between signal and decision [1][5][19] |
| 2.2 Resource conflicts & queues | 2% | 4% | 7% | ≈65% of delivery time is queue time [17]; +15% cost per added year [1]; priced on duration effects only |
| 2.3 Switching costs | 3% | 6% | 10% | Measured 17% effort drag on multi-assigned staff [14]; labor ≈65% of spend; 60% concurrency assumed |
| 2.4 Zombie projects | 3% | 6% | 10% | 30–40% of projects escalate [10]; 10–25% of budget carried beyond viability (never-stopped tail) |
| 2.5 Planning overhead (three arenas) | 0.5% | 1.5% | 3% | Frequency × duration × attendees × hourly cost across annual, recurring and cascade planning [22][23][25] |
| 2.6 Shadow levies (drift + evaporation) | 3% | 6% | 10% | <50% report high strategy alignment [3]; −56% value vs. business case [1]; conservative slice only |
| Raw sum | 13.5% | 27.5% | 48% | |
| Overlap adjustment (25–30%) | −3.5 pts | −7 pts | −14 pts | Levies co-occur; same dollars not counted twice |
| Combined tax rate | ≈10% | ≈21% | ≈34% | Sensitivity below |
The rate, stated carefully
A typical large organization pays a hidden tax of ≈21% of annual portfolio spend — one dollar in five — with ≈10% as the conservative case and ≈34% where portfolio maturity is low.
The best-documented floor is 5–10%: PMI’s high performers report just 2% of spend at direct risk from failure [4], and the balance is residual switching, queuing and drift that even disciplined portfolios carry. The distance between your rate and that floor is the addressable tax.
Sensitivity
The overlap adjustment is the model’s largest judgment: varying it between 15% and 40% moves the central rate between 23% and 17%.
Worked example
The tax on a $200M portfolio
On a $200M portfolio: ≈$42M a year, of which roughly $22–32M is realistically addressable — the rest is the residual drag even excellent portfolios carry.
≈$42Ma year, at the ≈21% central estimate
$22–32Ma year: the difference between paying the typical rate and the floor
≈$2Mplanning overhead in the illustration below: about 1% of portfolio spend, before counting the decisions the ceremonies failed to produce
Planning overhead, illustrated
Unlike the other levies, this one is directly computable from data the calendar system already holds. Four variables capture it — meeting frequency (sessions per cycle), meeting duration (hours per session), attendees (people pulled in, with preparation time counted), and loaded hourly cost — multiplied and then summed across three planning arenas that behave differently enough to deserve separate meters:
- Arena 1 — annual planning. The long cycle: months of pre-meetings, template rounds, draft submissions and negotiation, concentrated on the most senior attendees. Its defining inefficiency is the input-to-decision ratio: the costliest decision process in the company exists to move, on average, 8% of the spend [19].
- Arena 2 — regular reviews. Quarterly business reviews, monthly steering committees, portfolio boards, stage gates. Overhead scales with initiative count × attendee list × cadence; the waste share is every session whose content a dashboard could have delivered — status recitation that produces no funding, scope or sequencing decision.
- Arena 3 — unplanned change and the replanning cascade. The most expensive arena per episode, and the only one that scales with volatility rather than the calendar. A priority shift, a slip or an urgent intake does not re-plan one project: through shared resources and dependencies it forces re-estimation, re-sequencing and re-negotiation across every coupled initiative — the meeting-load twin of the deadlock in 2.2. Portfolios that cannot evaluate a change against the whole picture pay this arena twice: first the meetings to absorb the change, then the meetings to repair the schedule damage the first round caused.
An illustration for a $200M portfolio at a $110 loaded hourly rate:
| Component | Illustration | Cost |
|---|---|---|
| Arena 1: annual planning | An annual cycle consuming 60 hours each (sessions plus preparation) from 100 leaders and planners | ≈ $0.7M |
| Arena 2: regular reviews | Monthly reviews across 30 initiatives (1.5 hours × 8 attendees) plus quarterly portfolio boards | ≈ $0.5M |
| Arena 3: unplanned change and the replanning cascade | A dozen replanning cascades a year, each touching six dependent projects | ≈ $0.3M |
| Report assembly | Report assembly at the measured half-day-plus per professional per month [13] | ≈ $0.5M |
| Total | About 1% of portfolio spend — before counting the decisions the ceremonies failed to produce | ≈ $2M |
Governance-heavy, federated organizations run at multiples of this. Model range: 0.5–3% of portfolio spend, central ≈1.5%.
Measure your own rate
Benchmarks are helpful, but your own numbers decide.
The assessment computes a defensible first estimate of the tax from data most organizations already hold — PPM/portfolio records, resource assignments or timesheets, finance actuals, and workflow tools.
The one-week triage
Six questions, one analyst, five working days. Each maps to a levy; together they bound the tax well enough to decide whether the full assessment is worth running.
The five meters
The full assessment runs five meters over a preceding 12–24-month window. Each produces a levy estimate as a share of portfolio spend; four to six weeks with one analyst and portfolio-office support is a typical effort.
The roll-up
Combine the meters the same way the tax-rate model above combines the levies: sum the five measured levies plus a shadow-levy allowance (use half the switching-meter rate as a conservative proxy if unmeasured), then apply the 25–30% overlap adjustment. Report three numbers to the executive team: the rate (% of portfolio spend), the amount (currency, annualized), and the addressable share (the amount minus the 5–10% floor).
The one-week triage: six questions
| Question | Where the answer lives | What it signals |
|---|---|---|
| What share of portfolio funding actually moved in the last 12 months? | Finance actuals vs. prior-year allocation | ≤8% (the McKinsey average [19]) means the portfolio cannot re-decide — every levy runs longer than it should |
| For the last 5 stopped initiatives: how long from first documented red flag to formal stop? | Gate records, status reports, steering minutes | Median >8 weeks indicates a heavy latency levy (2.1); >6 months indicates zombies are only dying of old age (2.4) |
| What share of delivery staff are assigned to 2+ initiatives this month? | Resource plan / timesheets | >50% multi-assigned puts the switching levy (2.3) near its central estimate or above |
| For 20 recently delivered work items: what share of elapsed time was spent waiting? | Workflow tools (status timestamps), team leads | Waiting share >50% signals a heavy contention levy (2.2); >65% matches the worst measured environments [17] |
| What share of active initiatives would be re-approved today, at today’s numbers, against today’s strategy? | Portfolio review — ask each sponsor to answer in writing | Every honest “probably not” is a zombie or drift candidate; <80% re-approval marks a portfolio overdue for a kill round |
| How many attendee-hours went into planning, steering and review meetings last quarter? | Calendar export — recurring series titled plan / review / steering / prioritization, with attendee counts | Annualized cost above ≈2% of portfolio spend signals ceremony-heavy planning (2.5); a rising share of unplanned replanning sessions signals cascade volatility (arena 3) |
The five meters
| Meter | Data required | Computation | Reading it |
|---|---|---|---|
| Decision latency meter (levy 2.1) | Last 10–20 stopped / redirected / downscoped initiatives: date of first documented decisive signal, date of formal decision, date work actually stopped; monthly burn per initiative | Latency spend = SUM (burn × months between signal and effective stop). Add reallocation latency: funding moved late × months of delay | Express as % of annual portfolio spend. Also report median stop latency in weeks — the single most motivating number in most assessments |
| Contention meter (levy 2.2) | Sample of 30–50 delivered items: active vs. waiting time by state; roster of the 10 most-requested shared resources and their allocation counts | Queue share = waiting ÷ total elapsed. Levy ≈ queue-driven duration extension × (portfolio cost × 15%/year duration-cost factor [1]); flag any resource allocated to 4+ initiatives | Queue share above ~50%, or any critical resource on 4+ initiatives, indicates the portfolio is approved beyond its real capacity |
| Switching meter (levy 2.3) | Resource assignments or timesheets: share of delivery staff on 2+ and 3+ concurrent initiatives; loaded labor cost of the delivery population | Levy = labor cost × multi-assigned share × 17% (measured drag [14]; use up to 40% [15] only as a ceiling scenario) | Multi-assigned share is the control variable: every 10 points of concurrency reduction returns ≈1% of portfolio spend at the measured drag rate |
| Zombie meter (levy 2.4) | Full active-initiative list with YTD spend; four screening tests per initiative (below) | Levy = SUM over initiatives failing ≥2 tests of (spend × probability weight); probability weight 50% for 2 fails, 100% for 3–4 | Failing initiatives are candidates, not verdicts — each deserves the comparative review in 4.4; the meter prices the exposure |
| Planning overhead meter (levy 2.5) | Calendar data for planning / steering / review series: frequency, duration, attendees; loaded rates; count of replanning episodes and the projects each touched; report-assembly time | Overhead = SUM (frequency × duration × attendees × rate), computed separately for the annual, recurring and cascade arenas; waste share = sessions producing no funding, scope or sequencing decision (sample the minutes) | Overhead above ≈2% of spend, or fewer than ~1 material decision per 10 meeting-hours, marks planning as ceremony; a cascade arena growing quarter over quarter marks a portfolio absorbing change without machinery to evaluate it |
The four zombie screens. (1) Re-approval: would this initiative be approved today, at current cost-to-complete and current strategy? (2) Freshness: has the business case been revalidated in the last two quarters? (3) Ownership: is there a named owner accountable for the benefits after delivery? (4) Momentum: has it passed its last two gates without scope, schedule or funding change forced by evidence? An initiative failing two or more screens is not necessarily dead — but the burden of proof has shifted to it.
Reading your combined rate
| Your combined rate | What it means | What to do |
|---|---|---|
| Below 10% | At or near the documented floor; likely a disciplined, continuously re-planned portfolio | Verify the meters are accurate (especially self-reported waiting time) |
| 10–20% | Typical range; the tax is real but not yet structural | Attack the largest single meter first — usually switching or latency; both return money within two quarters |
| 20–30% | The central estimate for most large organizations; every levy is collecting | The loop (2.7) is running: pair faster kill decisions with reallocation and concurrency limits — single fixes will disappoint |
| Above 30% | Low-maturity range; consistent with PMI’s 28%-at-risk cohort [4] | Portfolio-level intervention: re-approve the portfolio from zero, with the comparative machinery of 4.4 in place before the next planning cycle |
Present conservative and central cases side by side; resist the temptation to present only the larger number — the conservative case is the one that survives challenge, and it is usually alarming enough.
4.4 · What cuts the rate
Unlike most taxes, this one is optional.
PMI’s cohort data show low-maturity organizations putting $280 million of every $1 billion at direct risk from failure versus $20 million for high performers — a fourteen-fold difference in exposure [4]. The high performers are not there by luck; they decide faster, load their people less, sequence around contention, and can kill projects because they compare them against the whole portfolio.
Decision service levels
Stop, pivot and reallocation decisions carry the same cycle-time discipline as delivery; funding moves more than once a year (active reallocators: +4 points of annual shareholder return [19]).
Comparative kill justification
Termination cases are argued at portfolio level — this money serves the strategy better there — which is the only argument that survives sponsorship politics (2.4).
Concurrency limits
Work in progress is matched to real capacity, and multi-assignment is the exception that needs justifying, not the default (every 10 points of concurrency cut ≈ 1% of spend returned).
Contention-aware sequencing
Initiatives are scheduled against the shared-resource calendar, not just the strategy calendar, before approval (2.2).
Benefits with owners
Business cases survive delivery, with named owners and revalidation dates (2.6).
Planning that decides, not performs
Top-quartile organizations close annual budgeting in 28 days or less against 56-plus for the bottom quartile [25] — the difference is standing data and small, frequent decision forums instead of mass ceremony (2.5).
In BCG’s research, transformations getting the governance factors right succeeded at 80% against a 30% baseline [9]; in PMI’s, high performers delivered 90% of projects to goals against 34% [4]. Associations, not proofs — but they concentrate exactly where the tax collects.
The decision layer
How aangine can help
We didn’t build another PPM tool. We built the planning layer that PPM tools are missing.
Levy 2.1 · Decision latency
In minutes. Not weeks or months.
See what changed. Discover what you missed. Decide what changes next.
100xfaster portfolio decisions
What our customers report in their case studies.
Levy 2.2 · Resource conflicts
Know exactly who’s doing what — and what’s missing
Resource bottlenecks kill portfolios silently. aangine’s heatmap visualization reveals conflicts, gaps, and over-allocations before they become crises.
- Identify bottlenecks before they surface
- Automated scheduling around constraints
Levy 2.3 · Switching costs
Capacity planning
Agile capacity planning that adapts to market shifts, project surges, and organizational changes. Know your true capacity at any moment.
- Optimize allocation across the entire portfolio
- Over/under-allocation identification
Levy 2.4 · Zombie projects
Compare every possible future before you commit
Play out dozens of scenarios in clicks, not weeks. See the full impact of every decision — resources, budgets, timelines — before you commit to a direction.
- Side-by-side scenario comparison
- Align stakeholders on a direction in minutes
Levy 2.5 · Planning overhead
Untangle complexity across hundreds of projects
One delayed project can cascade across your entire portfolio. aangine maps every dependency, syncs timelines, and orchestrates shared resources so everything flows.
- Cross-project dependency mapping
- Cascading impact visualization
- Automated reporting and alerts
Shadow levies 2.6
Align strategy, OKRs, and delivery in one place
Bridge the gap between strategic intent and execution reality. Track OKRs, monitor budget and CapEx/OpEx, and see how every initiative connects to your strategic priorities.
Your data. Your systems. No rip & replace.
aangine doesn’t replace your execution tools — it supercharges them. With our flexible plug-in architecture, we can integrate with virtually any platform.
AI discovers and highlights.
The AI Portfolio Analyst surfaces risks, patterns, anomalies and connections the human eye might miss.
Algorithms calculate and optimize; AI discovers and highlights; humans decide. The result: faster, clearer decisions when it matters most.
aangine TV
The Hidden Decision Tax, on film
Three short films on the hidden cost of poor portfolio planning: why business isn’t chess, a PMO treasure hunt, and the five villains behind the tax.
Your next move
The first step costs one analyst-week.
The hidden decision tax is the most measurable large inefficiency most organizations have not measured. It is collected in mechanisms every portfolio manager recognizes, priced by evidence that has been stable for two decades, and — unlike most costs of its size — it responds to decisions entirely within the organization’s control: decide faster, load people honestly, sequence around scarcity, and make stopping as justifiable as starting. On a $200 million portfolio, the difference between paying the typical rate and the floor is $22–32 million a year, every year. The data is already yours.
Our complimentary Portfolio Value Assessment runs the one-week triage from The Hidden Decision Tax whitepaper on your own portfolio data, so you get a defensible first estimate of your hidden decision tax and which levies drive it.
Sources
References cited on this page
Numbered as in The Hidden Decision Tax whitepaper (August 2026). Most portfolio evidence is survey-based, not audited.
- [1] McKinsey & Company and University of Oxford (BT Centre for Major Programme Management), “Delivering large-scale IT projects on time, on budget, and on value,” October 2012. Study of 5,400+ IT projects.
- [2] Project Management Institute, “Pulse of the Profession” series: 2013 ($135M wasted per $1B), 2016 ($122M), 2017 ($97M), 2018 ($99M / 9.9%). Practitioner surveys, samples ~800–4,455; 2017 edition.
- [3] PMI, Pulse of the Profession 2018 media release (regional waste spread; 31% of projects miss goals; alignment findings from the 2016 edition), and Pulse of the Profession 2016.
- [4] PMI, “Pulse of the Profession 2013” ($20M vs. $280M at risk per $1B for high vs. low performers; 90% vs. 34% of projects meeting goals). Survey of ~800 practitioners; “at risk” is an exposure measure, distinct from realized loss.
- [5] Economist Intelligence Unit / Brightline Initiative, “Closing the Gap: Designing and Delivering a Strategy that Works,” 2017. Survey of 500 senior executives at companies with $1B+ revenue.
- [6] Gartner, 2025 CIO and Technology Executive Survey (fielded 2024): 3,186 CIOs and technology executives, 88 countries, ~$351B IT spend; 48% of digital initiatives meet or exceed outcome targets. Press release, 22 October 2024.
- [7] KPMG, “2023 U.S. Technology Survey.” 400 U.S. technology executives, April–June 2023.
- [8] Bain & Company, “The ‘What, Who and How’ of Delivering Results,” 2016 (survey of roughly 300 companies); M. Mankins and P. Litre, “Transformations That Work,” Harvard Business Review, May–June 2024.
- [9] Boston Consulting Group, “Flipping the Odds of Digital Transformation Success,” October 2020. Survey of 825 senior executives plus client experience with 70 companies.
- [10] M. Keil, J. Mann and A. Rai, “Why Software Projects Escalate: An Empirical Analysis and Test of Four Theoretical Models,” MIS Quarterly 24(4), 2000. Survey of IS audit and control professionals (579 returned surveys).
- [13] Wellingtone, “The State of Project Management” reports: 2020 edition (111 organizations, 29 countries) and 2026 edition (72% of project professionals spend half a day or more per month collating reports).
- [14] A. Tregubov, B. Boehm, N. Rodchenko and J. A. Lane, “Impact of Task Switching and Work Interruptions on Software Development Processes,” Proceedings of ICSSP 2017. Empirical study based on developer effort reports.
- [15] American Psychological Association, “Multitasking: Switching costs,” 2006; summarizing J. Rubinstein, D. Meyer and J. Evans, Journal of Experimental Psychology: Human Perception and Performance 27(4), 2001.
- [17] N. Brown, “Our survey says… uncovering the real numbers behind flow efficiency” (63 teams, 12 months) and “The many flaws in flow efficiency,” ASOS Tech Blog. Single-company measurement; the largest published dataset of its kind.
- [19] Y. Atsmon (McKinsey & Company), “How nimble resource allocation can double your company’s value,” August 2016.
- [22] Accenture and Cranfield School of Management (A. Neely, M. Sutcliff, H. Heyns), “Driving Value Through Strategic Planning and Budgeting,” 2001, reporting Hackett Group benchmark data. Figures date from c. 1998–2001.
- [23] L. Perlow, C. Hadley and E. Eun, “Stop the Meeting Madness,” Harvard Business Review, July–August 2017. Executive meeting load ≈23 hours/week; survey of 182 senior managers.
- [25] APQC, Open Standards Benchmarking: annual budget cycle time (N = 2,617 organizations): top quartile ≤28 days, bottom quartile ≥56 days.
The whitepaper is an evidence-based framework prepared for executive audiences. It is not audited financial analysis; the tax-rate model and self-assessment state their assumptions so they can be challenged and re-based against actual portfolio data. Nothing here constitutes financial advice.