Within Sharper Thinking
Is the System Creating the Delay?
When a project stalls, better analysis looks beyond blame to goals, authority, priorities, and feedback loops.
On this page
- Blame versus system diagnosis
- Feedback loops and authority
- Better project explanations
Page outline Jump by section
Introduction
When a project stalls, the weakest explanation is often the most emotionally satisfying one: someone was lazy, careless, difficult or incompetent. Sometimes that is true. More often, delay is produced by the system around the people: unclear goals, split authority, shifting priorities, optimistic plans, weak feedback loops and decision rules that reward reassurance over reality. System-level reasoning does not excuse poor performance. It asks a better diagnostic question: what conditions made this failure likely, repeated or hard to correct?
For analytical thinking, this matters because project failure is rarely a single event. It is usually a chain: early ambiguity creates hidden work; hidden work breaks schedules; schedule pressure suppresses bad news; suppressed bad news delays decisions; delayed decisions make the original plan less realistic. The useful thinker looks beyond blame to the mechanism.
Blame versus system diagnosis
Blame asks, “Who caused the delay?” System diagnosis asks, “Why did this delay keep making sense to the people inside the project?” That shift is not soft or evasive. It is more demanding, because it requires evidence about incentives, governance, information flow and the gap between the official plan and the real work.
A stalled software rollout, for example, may appear to be a delivery-team failure. A system-level explanation may show something different: users were not involved early enough; requirements changed because senior sponsors had not agreed the real purpose; technical teams were measured on milestone completion rather than operational readiness; and no one had enough authority to stop the launch date from dominating every other judgement. The “project manager failed” story is simpler, but it may not explain why competent people repeatedly made poor decisions.
Project management research and professional guidance increasingly frame success as more than hitting a fixed deadline and budget. The Project Management Institute’s 2025 report argues that project professionals need business acumen: understanding the organisation, its strategy, finance, stakeholders and the value a project is meant to deliver, not merely managing tasks against a plan. The report links higher business-acumen proficiency with stronger project outcomes across business goals, schedule, budget and failure experience.[Project Management Institute]pmi.orgProject Management Institute
This distinction changes the quality of analysis. If the explanation is “the team missed the deadline”, the remedy is pressure. If the explanation is “the delivery system rewarded optimistic reporting and deferred unresolved dependencies”, the remedy is different: change escalation routes, make uncertainty visible, clarify decision rights, and measure progress by tested integration rather than slide-deck completion.
When the plan is not the work
Many projects fail because the plan describes a simplified version of the work. This is especially common when a project crosses organisational boundaries, uses new technology, depends on contractors, or must satisfy multiple stakeholders with different definitions of success.
The Crossrail programme is a useful example because the later problem was not simply that construction was “late”. The National Audit Office found in 2021 that, despite efforts to control cost and schedule after 2019, the programme was further from completion and more complicated than Crossrail Ltd or its sponsors understood. The result was a further forecast cost increase of £1.9 billion and 10 to 20 months of delay. The same report highlighted the complexity of bringing together trains, signalling, stations and other assets, and the need for several organisations to work closely to complete the programme. National Audit Office (NAO)+2National Audit Office (NAO)[nao.org.uk]nao.org.ukNational Audit Office (NAO)Crossrail – a progress updateNational Audit Office (NAO)Crossrail – a progress update
That is a system-level failure mode: the visible schedule gave more confidence than the underlying integration work justified. In such cases, asking whether a team is “on track” can be misleading unless “track” includes interface testing, unresolved defects, dependency risk, staffing capability and operational acceptance.
A better analytical question is not “Are the milestones green?” but “What would have to be true for this milestone to mean real progress?” A project may report progress because documents have been signed, components have been built or contracts have been let. Yet the harder question is whether the parts work together under real conditions.
Feedback loops and authority
A feedback loop is the route by which evidence changes decisions. In a healthy project, bad news travels quickly, reaches someone with authority, and changes priorities, funding, design or timing. In a weak project, bad news is collected but softened, delayed, disputed or buried until it becomes too expensive to act on.
Systems thinking is valuable here because it treats a project as interacting parts rather than a list of tasks. PMI’s systems-thinking guidance describes the approach as a way to understand complex interactions and feedback loops, especially in high-risk environments and under time pressure. It stresses that understanding the relationships between parts of a problem is the first step to designing a better solution.[Project Management Institute]pmi.orgProject Management Institute Systems Thinking Boosts Project Outcomes | PMIProject Management Institute Systems Thinking Boosts Project Outcomes | PMI
Authority matters because feedback without power becomes theatre. A risk register that no one acts on is not a feedback loop; it is a record of ignored knowledge. A steering group that receives bad news but cannot change scope, budget, staffing or deadline pressure is not governing the system; it is observing it.
The National Audit Office’s 2025 work on mega-project governance makes this point in institutional terms. It defines governance as the system that provides the framework for managing organisations or projects and making decisions, including formal structures, processes, people and behaviours. It says good governance is clear about who has authority and accountability, and about the investing organisation’s role in defining and controlling the project.[National Audit Office (NAO)]nao.org.ukOpen source on nao.org.uk.
That definition is useful far beyond public infrastructure. A delayed project often needs answers to four authority questions:
- Who can change the deadline when evidence shows it is unrealistic?
- Who can reduce scope without treating it as failure?
- Who can resolve conflicts between departments, suppliers or users?
- Who is rewarded for surfacing risk early rather than preserving confidence?
If the answer to these questions is unclear, the project may continue to fail even when everyone works hard.
How “good news” becomes a failure mechanism
One of the most dangerous project cultures is not open dishonesty but disciplined optimism. People learn which messages are welcome. Risks become “watch items”. Delays become “recoverable”. Dependencies become “being managed”. Teams stop lying to others only after they have first learned to lie to themselves.
The Challenger disaster remains a powerful case because it shows how repeated survival can be mistaken for safety. NASA’s own later safety material describes Diane Vaughan’s concept of normalisation of deviance: people become accustomed to deviations from rules and stop treating them as deviant. In the shuttle case, O-ring erosion and blow-by were accepted as risks despite design expectations of no joint failures. The same NASA material warns that past success can reinforce trust in risky practice instead of objective assessment.[SMA NASA]sma.nasa.govSMA NASAThe Cost of Silence: Normalization of Deviance and GroupthinkSMA NASAThe Cost of Silence: Normalization of Deviance and Groupthink
Columbia Magazine’s 2025 account of Vaughan’s work makes the analytical lesson even sharper. Vaughan initially expected to find calculating misconduct, but her archival research led her to a more systemic account: NASA had routines, language and decision structures that made the O-ring problem appear manageable. Repeated fixes seemed to work because the shuttle kept returning, so the organisation came to see the anomaly as acceptable risk.[Columbia Magazine]magazine.columbia.eduOpen source on columbia.edu.
For ordinary projects, the stakes are usually lower, but the pattern is recognisable. A team ships with known defects because previous releases survived. A finance transformation keeps its launch date because prior slippages were absorbed by overtime. A construction programme treats unresolved interfaces as manageable because each contractor’s individual dashboard looks acceptable. The system teaches people that risk is tolerable until the day it is not.
The hidden role of incentives
Project failure often looks irrational from the outside. Why would people approve a weak business case, preserve a fantasy date or keep spending when warning signs are visible? One answer is that the incentives are local, while the damage is system-wide.
Bent Flyvbjerg’s work on large infrastructure projects distinguishes technical error from psychological and political-economic explanations. In a World Bank paper, he reports persistent cost-estimation inaccuracy in transport projects, including average overruns of 44.7% for rail, 33.8% for bridges and tunnels, and 20.4% for roads in the cited sample. The paper argues that strategic misrepresentation can explain why costs are understated and benefits overstated when promoters are competing for scarce approval and funding.[World Bank]documents.worldbank.orgOpen source on worldbank.org.
This does not mean every project sponsor is lying. It means a competent analyst should ask what the approval system rewards. If only attractive projects receive funding, estimates may become attractive. If delay is punished more visibly than technical debt, teams may hide unresolved work. If senior leaders ask for confidence rather than uncertainty, they will receive confidence.
This is why “optimism bias” is an incomplete explanation on its own. A project can be optimistic because people are genuinely overconfident. It can also be optimistic because the organisation has made realism costly. The analytical task is to distinguish error, pressure and incentive.
The Post Office lesson: governance failure has human consequences
The UK Post Office Horizon scandal is not just a technology failure story. It is a severe example of what happens when a system rejects inconvenient feedback from the people closest to the work. Subpostmasters reported apparent shortfalls and problems, but the organisation’s response treated the computer system as reliable and the users as suspect.
The Institute of Directors’ 2024 policy paper frames the scandal as a failure of governance. It argues that although the case was ostensibly about IT, the root causes lay in human decision-making, organisational culture and business ethics. It says Post Office governance failed to address the possibility that branch shortfalls were caused by bugs, errors and defects in Horizon, and that directors relied too heavily on management and legal reassurance while technological and legal concerns were downplayed.[Institute of Directors]iod.comInstitute of Directors Io D The Post Office Scandal – A Failure of GovernanceInstitute of Directors Io D The Post Office Scandal – A Failure of Governance
Computer Weekly’s long-running coverage of the scandal reports that the public inquiry’s part one report said at least 10,000 people were affected to different degrees by the flawed Horizon system and the Post Office’s response to phantom losses. It also reported serious mental-health consequences among victims.[Computer Weekly]computerweekly.comOpen source on computerweekly.com.
For analytical skill, the lesson is not simply “listen to users”, although that would have helped. The deeper lesson is that a system can define valid evidence too narrowly. If the only trusted evidence comes from the system under dispute, human reports become noise. A better project explanation asks whether the affected people had a credible route to challenge the official model, and whether their evidence could change decisions.
Better project explanations
A strong project explanation should be specific enough to guide action. “Poor communication” is usually too vague. “Engineering risks were reported in technical forums but not translated into sponsor-level decisions before procurement deadlines” is much more useful. It names the mechanism.
A good explanation of project failure usually includes five parts:
Goal clarity: What outcome was the project meant to create, and did key stakeholders mean the same thing by success?
Authority: Who had power to change scope, funding, timing, standards or supplier arrangements when evidence changed?
Priority conflict: Which competing pressures shaped behaviour: launch date, budget ceiling, political commitment, customer need, safety, reputation or contract incentives?
Feedback loop: What information showed the project was in trouble, who saw it, how quickly it travelled, and what decisions it changed?
Adaptation: Did the project update its plan as reality emerged, or did it keep defending the original plan?
This format improves thinking because it separates symptoms from causes. “Testing is late” is a symptom. The system explanation might be that teams could not test earlier because requirements were unstable, environments were unavailable, suppliers were not integrated, and senior leaders treated testing as a final-stage activity rather than a discovery process.
It also avoids a common analytical trap: treating every failure as a lack of discipline. Some delays require tighter execution. Others require renegotiating the project’s purpose. If the goal is wrong, more discipline accelerates the wrong work. If authority is unclear, more meetings create the appearance of control without control itself.
Questions that reveal the system
System-level reasoning becomes practical when it changes the questions people ask in reviews, retrospectives and recovery plans. Useful questions include:
- What information would have warned us earlier, and why did it not change the plan?
- Which risks were known but socially difficult to raise?
- Where did the project depend on informal heroics rather than designed capacity?
- Which metric made the project look healthier than it was?
- Who benefited from keeping the original date, scope or estimate intact?
- What decision was repeatedly postponed because no one owned it?
- What would an outsider with authority stop, simplify or re-sequence?
These questions are uncomfortable because they move attention from individual effort to system design. But that is precisely why they improve analysis. A project can have hardworking people inside a structure that turns effort into delay. It can have talented specialists whose warnings are trapped below decision level. It can have accurate local reporting that adds up to a false global picture.
The practical payoff is better judgement. Instead of asking whether a stalled project needs more pressure, system-level reasoning asks whether pressure is part of the stall. Instead of asking who failed, it asks what the organisation made easy, what it made hard, and what evidence it refused to hear.
eBay marketplace picks
Marketplace Samples
Example marketplace items related to this page. Use the search link to explore similar finds on eBay.
Endnotes
1.
Source: pmi.org
Title: Project Management Institute
Link:https://www.pmi.org/-/media/pmi/documents/public/pdf/learning/thought-leadership/pulse/pulse_of_the_profession_2025-1.pdf
2.
Source: pmi.org
Title: Project Management Institute Systems Thinking Boosts Project Outcomes | PMI
Link:https://www.pmi.org/learning/thought-leadership/systems-thinking-and-project-outcomes
3.
Source: sma.nasa.gov
Title: SMA NASAThe Cost of Silence: Normalization of Deviance and Groupthink
Link:https://sma.nasa.gov/docs/default-source/safety-messages/safetymessage-normalizationofdeviance-2014-11-03b.pdf
4.
Source: magazine.columbia.edu
Link:https://magazine.columbia.edu/article/challenger-disaster-normalization-deviance
5.
Source: pmi.org
Link:https://www.pmi.org/learning/library/communication-method-content-in-project-9937
6.
Source: pmi.org
Title: future of project work
Link:https://www.pmi.org/learning/thought-leadership/future-of-project-work
7.
Source: project-management.com
Title: top 10 main causes of project failure
Link:https://project-management.com/top-10-main-causes-of-project-failure/
8.
Source: audit.scot
Link:https://audit.scot/uploads/docs/report/2017/briefing_170511_digital_future.rtf
9.
Source: nao.org.uk
Title: National Audit Office (NAO)Crossrail – a progress update
Link:https://www.nao.org.uk/wp-content/uploads/2021/07/Crossrail-a-progress-update-2.pdf
10.
Source: nao.org.uk
Link:https://www.nao.org.uk/wp-content/uploads/2025/03/lessons-learned-governance-and-decision-making-on-mega-projects.pdf
11.
Source: documents.worldbank.org
Link:https://documents.worldbank.org/curated/en/968761468141298118/pdf/wps3781.pdf
12.
Source: iod.com
Title: Institute of Directors Io D The Post Office Scandal – A Failure of Governance
Link:https://www.iod.com/app/uploads/2024/10/IoD-The-Post-Office-Scandal-%E2%80%93-A-Failure-of-Governance-1-f04f78664e5242c6bebb0a01035806c2.pdf
13.
Source: computerweekly.com
Link:https://www.computerweekly.com/feature/Post-Office-Horizon-scandal-explained-everything-you-need-to-know
14.
Source: nao.org.uk
Link:https://www.nao.org.uk/wp-content/uploads/2013/12/10320-001-Over-optimism-in-government-projects.pdf
15.
Source: nao.org.uk
Title: 012229 BOOK Lessons learned
Link:https://www.nao.org.uk/wp-content/uploads/2023/03/012229-BOOK-Lessons-learned.pdf
16.
Source: nao.org.uk
Link:https://www.nao.org.uk/reports/the-national-programme-for-it-in-the-nhs-an-update-on-the-delivery-of-detailed-care-records-systems/
17.
Source: nao.org.uk
Title: Completing Crossrail
Link:https://www.nao.org.uk/wp-content/uploads/2019/05/Completing-Crossrail.pdf
18.
Source: london.gov.uk
Title: final london assembly transport committee crossrail investigation report 0
Link:https://www.london.gov.uk/sites/default/files/final_-_london_assembly_transport_committee_crossrail_investigation_report_0.pdf
19.
Source: assets.publishing.service.gov.uk
Title: Mega projects slide pack publication 2026 correction
Link:https://assets.publishing.service.gov.uk/media/69eb2ecd9ca985145673b930/Mega_projects_slide_pack_-publication__2026_correction.pdf
20.
Source: assets.publishing.service.gov.uk
Title: mpa review nhs it
Link:https://assets.publishing.service.gov.uk/media/5a79dfd440f0b66d161aec5c/mpa-review-nhs-it.pdf
21.
Source: humanfactors101.com
Title: normalisation of deviance
Link:https://humanfactors101.com/2016/08/09/normalisation-of-deviance/
22.
Source: GOV.UK
Title: value for money study governance and budgeting arrangements for mega projects
Link:https://www.gov.uk/government/publications/value-for-money-vfm-study-on-the-governance-and-budgeting-arrangements-for-mega-projects/value-for-money-study-governance-and-budgeting-arrangements-for-mega-projects
23.
Source: psychsafety.com
Title: normalisation of deviance
Link:https://psychsafety.com/normalisation-of-deviance/
24.
Source: projectmanagement.com
Link:https://www.projectmanagement.com/blog-post/17944/Episode-345–My-Project-is-Failing–It-is-Not-My-Fault
25.
Source: content.tfl.gov.uk
Title: elc 20210715 supplementary agenda item12 nao report
Link:https://content.tfl.gov.uk/elc-20210715-supplementary-agenda-item12-nao-report.pdf
Additional References
26.
Source: youtube.com
Title: Breaking down barriers to implementing good practice in Project Management
Link:https://www.youtube.com/watch?v=22nj2KOoq18
Source snippet
Holistic View in Project Management | Systems Thinking That Improves Project Success Holistic View in Project Management | Systems Thinki...
27.
Source: youtube.com
Title: Systems Thinking for Leaders: Designing Solutions That Work
Link:https://www.youtube.com/watch?v=wSuQQYv-E64
Source snippet
Holistic View in Project Management | Systems Thinking That Improves Project Success...
28.
Source: youtube.com
Link:https://www.youtube.com/watch?v=Z4eGkp-a8_Y
Source snippet
Mastering Systems Thinking - Pamela Paterson...
29.
Source: youtube.com
Title: Mastering Systems Thinking
Link:https://www.youtube.com/watch?v=W-ztwdJhuKQ
Source snippet
Breaking down barriers to implementing good practice in Project Management...
30.
Source: instituteprojectmanagement.com
Link:https://instituteprojectmanagement.com/blog/3-most-common-reasons-for-project-failure/
31.
Source: prosymmetry.com
Link:https://www.prosymmetry.com/blog/4-famous-project-management-failures-and-what-to-learn-from-them
32.
Source: medium.com
Link:https://medium.com/%40marc.bara.iniesta/9-out-of-10-construction-projects-blow-their-budget-nothing-has-changed-132624cd8cb1
33.
Source: utahavalanchecenter.org
Link:https://utahavalanchecenter.org/blog/27476
34.
Source: facebook.com
Link:https://www.facebook.com/groups/spacehipsters/posts/9383904061654393/
35.
Source: researchgate.net
Link:https://www.researchgate.net/publication/222414633_Columbia_and_Challenger_Organizational_failure_at_NASA
Topic Tree
Follow this branch
Parent topic
Sharper ThinkingRelated pages 29
- Cost Optimism Why Weak Project Estimates Keep Winning Approval
- Crossrail What Crossrail Reveals About Hidden Complexity
- Decision Rights Who Has Power When Plans Stop Working?
- Deviance Drift How Risk Starts Feeling Normal
- Green Milestones When Green Milestones Hide Real Project Risk
- +1 more in sidebar