Hey Reader,

You've spent the last five weeks learning to spot warning signs.

People saying yes but meaning no.

Key people disappearing.

Your team pushing harder but getting nowhere.

Each one felt like a different problem.

But here's what I learned managing teams across India, Middle East Asia and the UK:

These aren't five different diseases.

They're five symptoms of the same thing.

Your project doesn't have controls.

THE DIAGNOSIS: PROJECT CONTROLS

A project control is a mechanism that keeps your team aligned, informed, and able to make decisions in real time.

Think of it as the immune system of a delivery.

When controls are weak, you don't get five separate crises.

You get a cascade.

The Five Core Controls:

1. Governance - Who decides what, and when.
2. Communication - How decisions and status reach the people who need to act on them.
3. Risk Management - Where problems surface before they become emergencies.
4. Resource Clarity - Who owns what, and whether they have what they need.
5. Progress Visibility - Real-time signals about whether you're on track.

One breaks down, you get warning signs.

Two or more break down simultaneously, you get a failing project.

HOW THIS EXPLAINS THE FIVE SIGNS

1. Sign #1 (People say yes but mean no) → Governance is weak. People can't voice concerns safely, so they don't.
2. Sign #2 (Key people disappear) → Communication is failing. No visibility, no engagement.
3. Sign #3 (Everyone wants something different) → No clear decision-maker. Everyone fills the vacuum with their own interpretation.
4. Sign #4 (Team works harder, moves slower) → Resource Clarity and Progress Visibility are broken. Work gets duplicated; blockers go unspoken.
5. Sign #5 (Sponsor disappears) → They stop hearing about progress and only hear about problems.

None of these are people problems.

They're control architecture problems.

HOW TO CHECK YOUR CONTROLS

Governance: Can you say no?

• Is there a clear decision-maker for scope?
• Do people know where to escalate without political risk?
• Are decisions documented and shared with the full team?

Communication: Does everyone hear the same message?

• Is there a single source of truth for project status?
• Do updates reach decision-makers weekly, not monthly?
• Can team members flag concerns without repercussion?

Risk Management: Do problems surface early?

• Is there a process for raising risks and blockers?
• Are they reviewed weekly, not quarterly?
• Does someone own the mitigation plan?

Progress Visibility: Do you know if you're actually on track?

• Are your metrics specific? Not "90% complete," what does that actually mean?
• Is progress tracked in real time, not estimated retroactively?
• Does your team see the same metrics your sponsor does?

Resource Clarity: Does the team have what they need?

• Does each person know what they own?
• Are dependencies mapped and managed?
• Is there a clear process for flagging resource gaps?

ONE SMALL THING TO START

You don't need perfect controls.

You need real ones.

Pick the one control that's most broken on your current project, usually it's communication or governance and spend 30 minutes this week building it.

• Communication: Schedule a weekly 30-minute standup. Status shared in real time, unfiltered.
• Governance: Document who decides what. Post it somewhere visible. Test it by having someone escalate something this week.
• Risk Management: Create a simple blockers list and review it weekly.

One control.

One week.

See what changes.

WHY THIS SERIES EXISTED

Once you see the controls problem instead of the people problem, your instinct shifts.

You stop asking "Why isn't this person engaged?" and start asking "How do we make status visible so they can stay engaged?"

You stop assuming teams are lazy and start asking "What blockers aren't we surfacing?"

That shift from blame to architecture is where everything changes.

The five signs aren't a personality problem.

They're a system design problem.

And system design problems have solutions.

YOUR CHALLENGE

What control is broken on your project right now - governance, communication, risk, visibility, or resources?

Reply and tell me.

I want to know what's happening in the projects you're running.

P.S. The projects that succeed aren't run by superhuman PMs.

They're run by people who built simple, relentless systems to keep the team connected.

​​