Two project managers. Same organisation. Same workload.
One ends every week exhausted — inbox full, chasing updates, putting out fires. The other finishes Friday with a clear record of what moved, what is next, and what does not need their attention at all.
Same hours. Different results.
The difference is not effort. It is structured.
Table of Contents
The Problem with Hustle Culture in Project Management
There is a belief in many organisations that the best project manager is the busiest one. The one who responds fastest. The one who is always across every detail. The one who never seems to stop.
It sounds like dedication. But in practice, it often looks like this:
Status updates collected manually every week
The same stakeholder is asking the same question for the third time
Decisions made from memory instead of a documented baseline
A project that runs on one person — and slows down the moment that person is unavailable
That is not a high-performing project. That is a project held together by individual effort.
And individual effort is not a system. It is a risk.
What Structure Actually Means
Structure is not bureaucracy. It is not more meetings, more templates, or more documentation for its own sake.
Structure is the set of simple, repeatable habits that remove the need to make the same decision twice.
It looks like this:
Communication cadence → Stakeholders know when they will hear from you. They stop asking because the update is already scheduled.
A single source of truth → The project register, the schedule, the risk log. One place. Everyone knows where to look.
Decision records → When a call is made, it is written down. Who decided, what was decided, and why. No more "I thought we agreed to..." conversations.
A weekly review → 30 minutes, same time every week. Look at what moved, what is blocked, what needs a decision. Not reactive. Deliberate.
None of these is complicated. All of them require consistency.
The Hustle PM vs The Structured PM
Here is what this looks like in practice:
Hustle PM | Structured PM | |
|---|---|---|
Communication | Responds to every message as it arrives | Sets a cadence — stakeholders expect it |
Project status | Held in their head | Documented and visible to the team |
Decisions | Made verbally, forgotten quickly | Recorded with rationale |
End of week | Exhausted, unsure what moved | Clear on progress, blockers, and next steps |
Risk | Everything depends on them | The system runs with or without them |
The structured PM is not less busy. They are busy on the right things.
Why This Is Hard to Change
Most project managers know they need better structure. The problem is that building a structure takes time you feel you do not have.
When you are already behind, slowing down to build a system feels like a luxury. So you keep running. And the pattern continues.
The way out is to start small and start with the thing that creates the most friction today.
If you are chasing the same status update every week — set up a standing request that goes out automatically.
If stakeholders keep asking where the project stands, create one shared document and stop answering the same question twice.
If decisions keep getting revisited, start keeping a one-line decision log in your next meeting.
One change. One week. That is enough to start.
Bottom Line
Effort matters. But effort inside a broken system just produces tired people.
If your weeks feel like controlled chaos, the answer is probably not more hours.
It is one clear communication cadence. One single source of truth. One decision record.
Structure is not the reward for getting on top of things. It is how you get on top of things.
P.S. Not sure if you qualify for the PMP yet? The PMP Eligibility Checker walks you through the requirements in under a minute. Free: vandersonbaril.com/products/pmp-eligibility-checker
I would also be interested in hearing how you are handling structure on your current projects. While I may not be able to respond to every message, I do read all replies.
Thank you for reading, and see you next Saturday.
