How to simplify project management

I have built a beautiful dashboard.

The detailed RAID log.
The dependency map.
The clean project plan.
The kickoff deck that looked like it deserved its own steering committee.

And then the team still asked the same questions.

What matters this week?
Who owns this?
What changed?
What is blocked?
What decision do we need?

That is when the lesson gets uncomfortable.

Sometimes the project system is not too simple.

Sometimes it is too heavy to use.

This issue is about simplifying the work without losing control.

More structure is not always more control.

Sometimes it is just more structure.

Project managers overbuild for good reasons. Projects are messy. Stakeholders want visibility. Delivery work has dependencies, risks, approvals, testing, scope movement, budget pressure, and people asking for “just a quick update” every 17 minutes.

So we build artifacts.

Kickoff decks. Dashboards. RAID logs. Plans. Trackers. Governance packs. Status reports. Meeting agendas. Decision logs.

None of those are bad.

The problem starts when the artifact becomes more important than the behaviour it was supposed to support.

A dashboard that nobody uses is not visibility.
A RAID log that does not move items is not control.
A meeting with no decision path is not alignment.
A project plan that scares people away is not planning.

Rigour is not the number of project artifacts.

Rigour is whether the system helps people decide, deliver, and focus.

Simple project management is not weak project management.

Weak project management is when the system looks mature but the team still cannot see what matters next.

The goal is not to delete process.

The goal is to keep the process that helps the work move.

Use the Decide or Deliver Filter before adding, keeping, or sending any project artifact.

For every meeting, dashboard, tracker, plan, report, or governance check-in, ask:

If the answer is vague, the artifact probably needs work.

Here is how the filter applies in real delivery work.

A kickoff does not need to be a 40-slide tour of everything everyone might need to know someday.

Simpler filter: Align on Why, What, Who, When, and first checkpoint.

If the team leaves the kickoff with more information but no shared operating rhythm, the deck was busy, not useful.

A meeting should have a point before it has an agenda.

Simpler filter: If the meeting purpose cannot be summarized in one sentence, it is not ready.

“Review project status” is not enough. “Decide whether UAT moves by three days or gets another reviewer” is useful.

Dashboards often become data pretending to be communication.

Simpler filter: Pick the three signals that change action this week.

Not every metric deserves the same space. Some numbers are decoration wearing a business-casual outfit.

A plan should guide people, not scare them.

Simpler filter: Can the team use it to understand the next milestone, key dependencies, ownership, and timing?

If the plan is so complex that only the PM can interpret it, the plan has become a private control tower. That is fragile.

A complete RAID log can still be passive.

Simpler filter: Every active item needs an owner, next action, or decision path.

If an item has been “monitored” for six weeks, it is probably not being monitored. It is being parked.

These should not prove that work happened.

Simpler filter: Show what changed, what needs attention, what decision is needed, and what happens next.

If the update does not help someone decide or deliver, it is probably noise.

The asset for this issue is the Project Simplicity Filter.

It helps you review the project artifacts that tend to grow quietly over time:

Use it to ask:

The point is not to make project management casual.

The point is to make the system easier to use.

Use the filter to see what helps decisions, what helps delivery, what clarifies ownership, and what can be simplified without losing control.

If the artifact helps the work move, keep it.

If it only makes the project look managed, challenge it.

You’ll find the filter button in The Move section below.

AI can help here as a clutter reviewer.

Not as the final judge.

Use it when you have a project artifact, meeting agenda, dashboard, or update that feels too heavy, but you are not sure what to cut.

Best use case: reviewing a bloated agenda, dashboard, report, or status update before it reaches stakeholders.

One caution: do not paste confidential, client-sensitive, personal, or restricted information into AI tools unless your organization and client rules allow it.

AI can spot clutter.

The PM still needs judgment, context, and stakeholder awareness.

Use the Project Simplicity Filter to review one artifact this week and ask one question:

Does this help the team decide or deliver?

Which project artifact would you like to simplify immediately?