Learning track · Project Controls · Blog

When a Strong Team Loses Control

Project lessons from Paraguay 1 – 4 USA, told from the site office

Written by Dr. Hassan Eliwa, PhD Published June 14, 2026 Updated June 14, 2026 10 min read

Filed under: Planning, Scheduling, Risk, Recovery

When a Strong Team Loses Control — Paraguay vs USA through a project manager's eyes (infographic) — Figure 1 — The match read through a project manager's eyes: pre-match baseline, project controls view, what went wrong and what went right.

I have watched a lot of football and run a lot of project controls, and the two keep teaching me the same lesson. A scoreline of 1–4 is not really a story about control. On paper, the losing side had heritage, experienced players and a serious reputation. On the pitch, none of that survived the first thirty minutes once the structure slipped. If you have ever stood in a site meeting watching a "strong" project quietly fall apart, you already know the feeling.

That is exactly why this match makes such a good teaching case. Swap the stadium for a construction site and the analogy is almost uncomfortable. A capable team, a confident plan, and then a string of small, unmanaged events that compound into a result nobody wanted. Below, I will walk through what happened through a project controls lens — the dashboards, the failure chain, the recovery roadmap — and tie each point back to jobs I have actually worked on.

Two teams, two projects, two dashboards

When I diagnose a troubled job, I do not start with blame. I start with the dashboard. A dashboard does not have opinions; it shows you where control is holding and where it is leaking. The infographic below frames both sides of the match as project dashboards, and the contrast is stark — not because one team had better players, but because one project was being controlled and the other was not.

The match as a mega project — Paraguay troubled project dashboard versus USA well-controlled project dashboard — Figure 2 — The same event read as two project dashboards: a troubled project versus a well-controlled one.

Read the two columns the way you would read a weekly report. One side shows schedule slipping behind plan, poor quality, high risk exposure, weak communication, late recovery action and falling stakeholder confidence. The other shows the opposite across the board. Here is the same comparison as a table I could drop straight into a steering report:

Control area	Troubled project 🔴	Controlled project 🟢	What it really measures
Schedule performance	Behind plan	Ahead of plan	Are we keeping the critical path?
Execution quality	Poor	Strong	Rework, defects, first-time-right
Risk exposure / response	High, uncontrolled	Controlled	Are risks owned and mitigated?
Communication	Weak	Clear	Does information reach decision-makers in time?
Recovery action	Late	Ready / early	How fast can we respond to a slip?
Stakeholder confidence	Falling	Positive	Do sponsors still believe the plan?

The failure chain: how 1–0 becomes 1–4

No project fails at the end. It starts failing the moment control is lost early, and then the failure cascades. The match shows this perfectly. Early pressure was not absorbed; a defensive gap opened; confidence dropped; communication broke down; there was no recovery plan; and the scoreline ran away. On a construction job the chain looks identical — only the vocabulary changes.

The Failure Chain — how one early lapse compounds into defeat (six-step horizontal flow diagram) — Figure 3 — The failure chain. Each unmanaged link makes the next one more likely.

#	On the pitch	On the project	Where it bites
1	Early pressure	First slip on the critical path goes unflagged	Week 2–3, when the baseline is still 'fine'
2	Defensive gap	No mitigation plan or float to absorb the slip	Procurement and early works
3	Lost confidence	Team stops trusting the programme	Daily huddles turn into excuses
4	Poor communication	Reports get optimistic; bad news travels slowly	Monthly report vs. site reality
5	No recovery plan	Nobody owns the catch-up logic	When the client finally asks 'how do we recover?'
6	Heavy defeat	Schedule and cost overrun, claims, reputation hit	Handover, final account, the next tender

A real example: the wastewater plant that lost the first month

On a wastewater treatment upgrade I supported, the contractor lost roughly three weeks in the very first month — a late geotechnical result delayed the foundations for a new clarifier. Three weeks does not sound fatal. The problem was that nobody treated it as a control event. There was no early-warning flag, no time-impact analysis, and crucially no recovery logic. By the time it surfaced in the monthly report, the slip had already pushed concrete pours into a wet-weather window, which pushed mechanical installation, which pushed commissioning. The original three weeks became nearly three months at handover. The defensive gap in week three is what eventually produced the 'heavy defeat' at the end.

What the numbers were already telling us

Here is the uncomfortable truth: in most troubled projects, the data turns red weeks before the people do. If you are tracking earned value honestly, the Schedule Performance Index (SPI) and Cost Performance Index (CPI) start drifting below 1.0 long before anyone says the word 'recovery'. The chart below contrasts a project that held control against one that slipped — and notice how the controlled project takes an early dip, corrects, and holds, while the uncontrolled one degrades in a straight, predictable line.

Schedule and Cost Performance chart — SPI and CPI over twelve reporting periods comparing a controlled project that holds against an uncontrolled project that slips — Figure 4 — SPI and CPI over twelve reporting periods: control that holds versus control that slips.

The mini-dashboard in the original infographic put the troubled project at SPI 0.62 and CPI 0.68 — both deep in the danger zone. In plain terms, that project was getting about 62 cents of schedule progress and 68 cents of cost value for every dollar planned. You do not recover from numbers like that with effort and optimism. You recover with a structured plan, owned and dated. Try the math yourself with the SPI calculator and CPI calculator, or model the whole picture in the EVM calculator.

Index	Reading	Interpretation	Action threshold
SPI = 1.00	On schedule	Earning value at the planned rate	Maintain & monitor
SPI 0.90–0.95	Early warning	Slip beginning — investigate now	Flag in weekly report
SPI < 0.85	Recovery zone	Material schedule erosion	Trigger recovery plan
CPI < 0.90	Cost erosion	Spending ahead of value earned	Re-forecast EAC, escalate

Recovery is a plan, not a hope

The single biggest difference between the two sides was not skill. It was the presence — or absence — of a recovery plan. 'Hope is not a recovery strategy' sounds like a slogan until you have lived the alternative. When a project slips, the controlled response is methodical: detect, diagnose, re-baseline, re-sequence and execute, with dates and owners against every step. Below is a 90-day recovery roadmap in Gantt form — the kind I would build in Primavera P6 the week a project tips into the recovery zone. See more patterns in our project recovery playbooks.

90-Day Project Controls Recovery Roadmap

Notice the shape of it. The first two weeks are not about building — they are about seeing clearly: detecting the true extent of the slip and re-validating the baseline before anyone commits to a catch-up promise. The recovery plan is then approved at a formal gate (the diamond) before mitigation begins, so the team is not accelerating on a plan nobody signed off. This is the discipline the match was missing entirely.

Detect & diagnose (Wk 1–2): quantify the real slip with a time-impact analysis — not a gut feel.
Re-validate the baseline (Wk 3–4): confirm logic, durations and constraints still reflect reality.
Re-sequence the critical path (Wk 4–6): find legitimate catch-up logic — parallel paths, re-prioritised works.
Refresh risk & re-balance resources (Wk 5–9): update the risk register and put crews where the path needs them.
Approve at the gate (Wk 9): a sponsor-signed recovery plan, not a verbal promise.
Execute, re-forecast & report (Wk 9–13): act, then re-measure honestly and tell the truth in the report.

Common mistakes (and how the controlled project avoided them)

✗ Common mistake	What it looks like on site	✓ The controlled habit
Reputation as a plan	"This contractor always delivers" — so nobody checks the early data	Earn confidence weekly from the dashboard, not from history
Late reporting	Slips surface in the monthly report, a month too late	Real-time data and weekly early-warning flags
Optimistic forecasts	EAC quietly stays green while site burns	Re-forecast honestly; escalate before damage spreads
No critical-path focus	Effort spreads across non-critical tasks	Protect the critical path above everything else
Recovery improvised	Catch-up by overtime and pressure, no owner	Recovery plan ready before the crisis, not after

Expert tips from the site office

Make 'early' a metric. Track how many days pass between a slip happening and a slip being flagged. If that gap is widening, your control system — not your team — is the problem.
Run a two-minute dashboard, every day. Five indicators — schedule, cost, risk, quality, momentum — beat a fifty-page report nobody reads. The original infographic's mini-dashboard is the right instinct.
Protect the first 30 minutes. In football it is literally the first thirty minutes; on projects it is front-end planning. Win the start and recovery stays cheap. Lose it and every fix costs more.
Pre-write the recovery logic. Keep a standing recovery template so that when SPI dips below 0.85 you are filling in a plan, not inventing one under pressure.
Tell the truth in reports. Honest red beats comfortable green. The controlled project's advantage started with reporting that decision-makers could actually trust.

Key takeaways

Project Management Lessons from Paraguay vs USA — seven distilled lessons infographic — Figure 6 — The same lessons, distilled: strong teams lose when control systems fail.

About PMMilestone.org — Free AI-Powered Project Management Tools

If this way of thinking resonates, the good news is you do not need an enterprise budget to start working like the controlled project. PMMilestone.org is a free, AI-powered project management platform built for exactly this — turning control from an idea into a daily habit. I point graduates and busy site teams to it because it removes the friction between 'I should track this' and actually tracking it.

What you get on PMMilestone.org: a genuinely free, ad-supported toolkit built by working project professionals, not a paywalled SaaS funnel. The platform combines calculators, learning content and reference material in one place so you can plan, control and recover without juggling ten different apps.

Feature	What it does	Why it matters on real projects
34+ free calculators 🧮	EVM (SPI/CPI/EAC), schedule, cost, earned value, productivity and risk tools	Run the numbers in seconds instead of rebuilding spreadsheets every week
PM Academy 🎓	Structured lessons across planning, scheduling, cost and risk control	Up-skill site engineers and graduates without an expensive course
443+ term glossary 📚	Plain-English definitions of project controls and contract terminology	A shared vocabulary stops the "communication gap" that sinks projects
AI-powered assistance 🤖	Guidance and templates that speed up everyday controls tasks	Less time formatting, more time managing the critical path
Elite Project Controls (EPCT) ⭐	A deeper system for practitioners who want to operate at a senior level	A path from "using tools" to "owning the controls function"

The bottom line: control is a discipline, not a personality trait — and the right tools make that discipline repeatable. Explore the full toolkit free at PMMilestone.org.

Tags:Project ControlsPlanningSchedulingRisk ManagementRecovery PlanningConstruction ManagementEarned Value ManagementLeadershipFootball Analytics

Continue Learning

More Learning Tracks from the Project Controls Academy.

Learning track

Construction Claims Career Path

A practical roadmap for engineers moving from site delivery into planning, delay analysis, claims, commercial controls and senior claims consulting.

Read track

Learning track

Project Controls Digital Transformation Roadmap

A future-focused guide to modern project controls through data integration, reporting automation, Power BI, AI, BIM and digital PMO capability building.

Read track

Dark navy project controls dashboard with Gantt charts and KPIs

Learning track

Project Controls Fundamentals

Scope, schedule, cost, risk, quality and reporting — the six disciplines that hold every successful capital project together, taught from first principles.

Read track

Dark navy earned value dashboard with glowing S-curves

Learning track

Earned Value Management

From PV / EV / AC to SPI, CPI, EAC, ETC, VAC and TCPI — the full toolkit for measuring and forecasting project performance.

Read track

Featured Academy