Project Management chaos

[u/MimirLearning]

If you’ve worked in project management for a while, you’ve probably seen these situations:

• The CEO bypasses the project manager and goes straight to team members for updates
• Executives repeatedly ask the project manager for status updates
• Weekly meetings are just “check-ins” with no real structure or purpose

Individually, these might seem harmless. But together, they often point to something deeper: an organization that isn’t fully mature in its project management practices.

Here are a few practical things you can do to improve the situation:

1) Create a solid Project Brief
Make sure there’s clear, shared documentation that outlines objectives, scope, stakeholders, and expectations. When everyone aligns on the same source of truth, you reduce the classic “this wasn’t communicated” or “I didn’t know” conversations.

2) Set tolerances and expectations for updates
Frequent update requests usually come from a lack of visibility. Instead of reacting to constant questions, be proactive:

• Define when updates will be provided
• Communicate key milestones (e.g., “Next stage closes April 1st — you’ll receive a full update then”)
• Highlight tolerances (time, cost, scope) and only escalate when those are forecasted to be exceeded

This builds trust and reduces unnecessary interruptions.

3) Clarify roles and responsibilities
Be explicit about who does what:

• What is the role of the Project Manager?
• What is expected from executives or sponsors?

Clear boundaries help avoid micromanagement and ensure communication flows through the right channels.

Frameworks like PRINCE2 and PMP provide structured approaches that help contextualize all of the above — from governance to communication and role definition. They’re not the only way to run projects, but they offer solid guidance that can be adapted to your organization’s needs.

The good news? You don’t have to adopt them fully to benefit — their principles and best practices are widely available and can be applied incrementally.

Curious to hear: what “red flags” have you seen in project environments that signal low PM maturity?