Is Disinformation Driving Your Business Projects?

Project disinformation quietly destroys budgets, timelines, and trust, and it is far more common than most teams admit. Optimism bias pushes people to favor good news and discard warnings, so roughly a quarter of projects miss their stated goals before anyone speaks up. The losses build silently, and leaders often discover the truth only once a modest problem has become a costly public failure.

Table of Contents

Project research adds that about twelve percent of every dollar invested is wasted on poor performance, a figure that climbs when reports go uncorrected. Managers who can tell a reliable figure from a hopeful one protect budgets, schedules, and trust. The construction example below shows how concealment takes root, and the schedule and cost checks that follow give you a way to catch it early.

The Construction Industry – a Prime Example

The construction industry shows what happens when teams hide the truth, and the pattern repeats often enough to measure. Research led by Bent Flyvbjerg finds that roughly nine in ten megaprojects exceed their budgets, driven in large part by optimism bias. Projects can look healthy for years and then collapse at the very end, producing major losses and plenty of blame.

Years ago, a West Australian construction company considered successful and well managed reported staggering losses of around six hundred million dollars. Those losses built up gradually across several years rather than in a single quarter, which raised an obvious question about how such a problem stayed hidden for so long from people who believed the firm was thriving.

When teams examine the problem, a few explanations tend to surface:

Incorrect Information: The answers produced are wrong because the data feeding the analysis was never accurate in the first place, so the team trusts a conclusion built on faulty inputs.
Faulty Systems: There is a fault inside the reporting system itself, so the output becomes unreliable even when the original inputs were sound and the data was entered correctly.
Misinterpreted Results: The information has been read incorrectly, which leads the team to draw the wrong conclusion from valid data that might actually point in a different direction.
Limited Expertise: The project team lacks the knowledge or experience needed to interpret the information correctly and to notice the warning signs before they become serious problems.
Deliberate Concealment: A member of the project team has deliberately covered up the problems, which is one of the core mistakes behind costly overruns, to protect themselves or the wider effort from the scrutiny and blame that honest reporting would bring.
Convenient Ignoring: The team has noticed the problems but decided to ignore them rather than confront an uncomfortable reality that would slow the project down or force them to admit a mistake.

The Project Schedule – Is It Accurate?

A fundamental principle of the APM project management approach is that a schedule is essential for every initiative, and a schedule is the first place disinformation takes hold. PMI project performance research shows that many projects miss goals when timelines are distorted. A project schedule that is never updated hides slippage until it is too late.

There are also incidents where a failure of communication leaves a project completed late, with the project manager caught completely unaware and unable to explain the delay. This emphasizes the importance of effective communication throughout the project lifecycle, especially when schedules come under real pressure and honest updates matter most of all for the outcome.

There are, of course, multiple reasons for a schedule not being met:

Poorly Built Schedule: The schedule is not constructed properly, with errors in the logic, interdependencies, durations, and even the resources assigned, so the baseline cannot be trusted and needs a full rebuild before it can guide the team.
Tight Commissioning Window: The schedule may have included insufficient time for finishing the work and then commissioning the project, which pushes real completion far beyond the published date.
Stale Progress Data: The schedule has not been updated correctly, so any progress shown appears to be more advanced than it actually is, giving stakeholders a false sense of security.
Wrong Metric Focus: The project team has analyzed progress by percentage completeness but is not looking at progress measured against the critical path, so delays on key activities stay hidden.
Optimistic Neglect: The project team simply ignores the schedule and hopes that everything will work out well and be completed on time without taking corrective action even as deadlines slip.
Schedule Manipulation: The team alters the schedule to show that the project is on track even when it is not, masking slippage until the very end of the project.
Excuse Hunting: The team finds faults in the schedule and uses them as an excuse to ignore the fact that the schedule indicates the project will be completed late.

The Project Cost Report

A monthly cost report should reveal losses early, but it can also become the tool that hides them. Reliable cost of quality reporting catches issues before they compound, because unchecked losses waste about twelve percent of project investment. The figures shown to management can differ from reality while a problem stays hidden inside the details.

Again, there are several reasons why this might occur:

Data Entry Errors: Data may be put into the cost report incorrectly, whether through a simple typing mistake or a wrong figure copied from another document, and no one checks it.
Unapproved Over-Claims: The report may include over-claims, such as income from work not yet done or claims not approved by stakeholders that have not been paid at all, or not in full.
Incomplete Cost Capture: The report may include costs that are incorrect, have been omitted entirely, or have simply been forgotten by the team responsible for gathering the figures.
Ignored Warning Signs: Information from the cost report has been ignored because the team hopes things will improve by the end and avoids the fact that the project is losing money.
Hidden Losses: Loss is hidden deliberately, and reports are manipulated to indicate a profit, so management only learns the truth when it is far too late to act.
Misleading Reassurance: The reasons for any loss are explained incorrectly, and management is given indications that the money might be recovered by the end of the project, which never happens.

Misinformation Versus Disinformation: Why Intent Matters

Disinformation and misinformation both distort decisions, but they differ sharply in intent. American Psychological Association research explains that misinformation is false information shared without intent to mislead, while disinformation is false information deliberately intended to deceive. In projects, a manipulated schedule is disinformation, while an honest typing error in a cost figure is misinformation, and the two demand different responses.

That difference changes how a manager responds to what they find. Deliberate concealment calls for stronger oversight, independent checks, and clear accountability, while honest error calls for better training and clearer reporting processes. Both must be corrected, but only deliberate disinformation signals a deeper culture problem that threatens trust across the whole team and its stakeholders.

The distinction matters most when you decide how to respond:

Aspect	Misinformation	Disinformation
Intent	Shared by mistake	Shared deliberately
Example	Typo in a cost figure	Faked schedule update
Fix	Training and checks	Oversight and accountability
Signal	Process weakness	Trust problem

Countering Optimism Bias With an Outside View

Optimism bias is the well-documented tendency to overestimate the chance of success, and researchers regard it as a leading behavioral cause of budget overruns. Bent Flyvbjerg recommends a corrective called reference class forecasting, which bases estimates on the actual outcomes of comparable past projects. That outside view counters the inside view that makes every project feel uniquely likely to succeed.

Teams can apply the same logic without formal forecasting tools. Before approving a schedule or budget, compare it against what similar initiatives actually achieved rather than what the plan optimistically promises. When the optimistic number sits far from the reference class, treat that gap as a warning rather than dismissing it as a one-off exception that will never happen.

Practical ways to bring an outside view into planning include:

Use Benchmarks: Compare planned cost and duration against similar completed projects, so your estimates reflect real outcomes rather than hopeful assumptions about what might happen.
Challenge Forecasts: Question any plan that beats the historical average by a wide margin, and demand clear evidence for why this time will genuinely be different from the past.
Plan for Bad News: Build explicit contingencies and review them whenever warning signs appear, rather than waiting for full confirmation that a costly failure is already underway.

Conclusion

Disinformation rarely announces itself, but it leaves detectable traces in schedules, cost reports, and the tone of team updates. When optimism bias and concealment compound, a meaningful share of projects miss their goals and real investment is lost along the way. The answer is not cynicism but disciplined verification of every figure that guides important decisions.

Make it a habit to query every schedule and every report, compare estimates against real outcomes, and investigate warning signs early rather than waiting for proof. Treat a single red flag as a reason to look closer, because small problems compound quickly into expensive ones. Managers who verify consistently separate truth from appearance and protect their projects from quiet, costly failure.

Frequently Asked Questions About Disinformation in Projects

What is disinformation in a project context?

Disinformation in a project is deliberately or accidentally misleading information that shapes decisions and reporting. It can be false data, manipulated schedules, inflated progress, or costs that are hidden or understated. When teams consume these unreliable signals, they make decisions based on a false picture, and the real state of the project only becomes clear once the damage is already done.

How can project managers detect disinformation early?

Project managers can detect disinformation by cross-checking every report against independent sources and by asking probing questions when figures do not match expectations. Comparing the schedule to actual milestones, validating cost claims against invoices, and encouraging open reporting all help. When several small warning signs appear together, treat them as a signal rather than dismissing each one separately.

What role does optimism bias play in project failure?

Optimism bias makes people favor information that matches what they want to believe and discard anything inconvenient. In projects, this leads teams to ignore cost overruns, slipping schedules, and early warning signs because admitting them feels uncomfortable. Over time, these ignored problems compound, and the gap between reported and real status grows until the project fails in a visible, costly way.

How does an inaccurate schedule hide real project status?

An inaccurate schedule can hide real status when it is never updated, when it ignores the critical path, or when it is deliberately adjusted to show the project on track. If the baseline is built on flawed logic or outdated data, the reported progress looks healthy while actual delivery slips behind. Managers must verify schedule health rather than trusting the date shown.

What should managers do when they spot warning signs?

Managers should investigate warning signs immediately rather than waiting for confirmation. Cross-check the schedule against milestones, reconcile the cost report with real spending, and ask the team direct questions about discrepancies. Escalate serious issues to stakeholders and create a plan to correct the data at its source. Early action prevents a manageable problem from becoming an expensive failure.