RESOURCE MANAGEMENT
Most project managers have confused status updates with leadership. The job site doesn’t need another narrator, it needs someone willing to make a call.
KYLE Mussmacher March 2026
7 MIN READ
There’s a project manager somewhere right now copying last week’s schedule update into an email, adding a few red-yellow-green dots, and calling it leadership. Their superintendent just made three decisions for them before lunch. And nobody in the trailer sees a problem with that.
Here’s the uncomfortable truth the construction industry keeps dancing around: the majority of PMs aren’t managing anything. They’re narrating. They watch the project happen, they document it with varying degrees of accuracy, and they relay that information upstream. They’ve turned themselves into human middleware, expensive, error-prone, and completely replaceable by a decent dashboard.
That’s not project management. That’s sports commentary with a hard hat.
THE REPORTER PROBLEM
Construction has quietly developed an epidemic of PMs who think their job is to observe and relay rather than decide and direct. It’s not hard to see how we got here. The industry’s obsession with documentation ; RFIs, submittals, daily logs, cost reports: has created a culture where the appearance of management is rewarded over the practice of it.
You can fill out every field in Procore, maintain a flawless submittal log, and produce weekly reports that would make an accountant weep with joy and still be a terrible project manager. Because none of that requires you to actually make a decision.
THE PM WHO CAN TELL YOU WHAT HAPPENED YESTERDAY BUT CAN’T TELL YOU WHAT SHOULD HAPPEN TOMORROW ISN’T MANAGING THE PROJECT. THE PROJECT IS MANAGING THEM.
The “reporter” PM has a few telltale behaviours. They escalate everything. They schedule meetings to discuss things they could resolve in a five-minute phone call. They use phrases like “I’m waiting to hear back” as if patience is a strategy. They forward emails without commentary. And the moment something goes sideways, they start documenting their own lack of involvement as a defence mechanism.
This is what it looks like when you’ve optimized for CYA instead of outcomes.
DECISION-MAKING IS THE WHOLE JOB
Strip away the admin, the meetings, the software, the reporting cadences and the core function of a project manager is to make decisions that allocate limited resources against competing demands. That’s it. That’s the gig. Everything else is either a tool to support that function or a distraction from it.
Yet most PMs have never been taught how to actually make decisions under uncertainty. They’ve been taught processes. They’ve been taught software. They’ve been taught to “communicate.” But nobody sat them down and said: your job is to take imperfect information, choose a direction, and own the consequences.
SPEED OVER PERFECTION
A good decision made today beats a perfect decision made next Thursday. The job-site doesn’t pause while you build consensus. By the time you’ve consulted everyone, the crane has been sitting idle for two shifts and you’ve burned $14,000 proving you’re “collaborative.”
REVERSIBILITY IS YOUR FRIEND
Most decisions on a construction project are reversible. Re-sequencing a pour, shifting a crew to a different area, pulling a sub off a task these can be undone. Stop treating every call like it’s carved in concrete. Act, assess, adjust.
SILENCE IS A DECISION
When a PM doesn’t make a call, someone else does , the super, the foreman, the sub. And that someone doesn’t have your budget context, your schedule awareness, or your contractual obligations. Inaction doesn’t preserve options. It delegates authority to whoever’s closest to the problem.
◆ ◆ ◆
RESOURCE MANAGEMENT IS NOT A SPREADSHEET
This is where the reporter problem metastasizes. Because if your understanding of resource management is a labor histogram and a cost-loaded schedule, you’re already behind. You’re describing resource allocation. You’re not managing it.
Real resource management is an active, dynamic, sometimes uncomfortable exercise in trade-offs. It’s telling a superintendent that his preferred crew is getting pulled to another area because the critical path shifted. It’s having the conversation with a subcontractor about undermanning three weeks before it becomes a schedule impact. It’s looking at your equipment spread and realizing you’re paying for a tele handler on a floor that doesn’t need one anymore and actually doing something about it.
Most PMs know these things are happening on their projects. They can see the waste. They can see the misallocations. But they won’t act on what they see because acting requires a decision, and a decision requires ownership, and ownership requires risk. So they report it instead. They mention it in the OAC meeting. They note it in the weekly summary. And absolutely nothing changes.
THE REPORTER
“We’re tracking behind on Level 3 drywall.”
“The electrician is short on manpower.”
“Equipment costs are trending over budget.”
“We may need to re-sequence next month.”
THE MANAGER
“I’m pulling the drywall crew from 5 to backfill 3. Here’s the revised sequence.”
“I called the EC. They’re adding four guys Monday or we’re back charging.”
“I demobilized the tele handler on the 20th. Saves $3,800/week.”
“Here’s the new sequence. I’ve already coordinated with MEP.”
See the difference? Same project. Same information. One PM reported the weather. The other one changed it.
WHY WE KEEP PRODUCING REPORTERS
This isn’t entirely the individual PM’s fault. The industry is structurally biased toward producing reporters, and it starts early.
Entry-level PMs are taught to document everything and decide nothing. They’re shielded from real decisions by layers of senior management who want to maintain control. By the time they get promoted to a level where they could make consequential calls, they’ve spent five years learning that the safe move is to pass information up and wait for direction down. They’ve been trained to be reporters. Then we’re surprised when they keep reporting.
Company culture reinforces this. In organizations where mistakes are punished more harshly than inaction, the rational move is to do nothing and document your way out of accountability. When the post-mortem on a failed project focuses on “who knew what and when” rather than “what decisions were made and why,” you’re telling every PM in the room that the safest career path is to be the most thorough narrator in the building.
YOU CAN’T BUILD A CULTURE OF DECISIVE PROJECT MANAGEMENT ON A FOUNDATION OF PUNISHING PEOPLE WHO MAKE DECISIONS.
THE MATH IS SIMPLE
The technology conversation makes this worse, not better. Every new platform promises “better visibility” and “real-time insights.” Great. Now your PMs can report the news faster. They can produce dashboards that refresh every fifteen minutes showing exactly how much money they’re watching you lose in real time. The data isn’t the bottleneck. The willingness to act on it is.
◆ ◆ ◆
WHAT ACTUALLY CHANGES THIS
If you’re a PM reading this and feeling called out ; good. That’s the point. But self-awareness without action is just more reporting. Here’s what the shift actually looks like:
REDEFINE YOUR OWN JOB DESCRIPTION
Stop measuring your day by tasks completed and start measuring it by decisions made. At the end of every day, ask yourself: what resource allocation did I change? What problem did I solve before it was escalated? What trade-off did I evaluate and resolve? If you can’t name at least one, you narrated today. You didn’t manage it.
GET COMFORTABLE BEING WRONG
You will make bad calls. You’ll move a crew somewhere they didn’t need to be. You’ll push a subcontractor too hard on the wrong issue. You’ll demobilize something a week too early. And the project will survive. Because here’s what nobody tells you: a recovered bad decision almost always costs less than a delayed correct one. The rework from moving a crew too early is cheaper than the idle time from waiting until you were “sure.”
BUILD YOUR RESOURCE INTELLIGENCE
You can’t manage what you don’t understand at a granular level. Know your burn rates by trade, by area, by day. Know which subs are running lean and which ones are burying labor. Know the actual utilization rate of every piece of major equipment on your site—not what the rental invoice says, but what’s actually turning wrenches. This is the information that turns a reporter into a manager, because once you have it, doing nothing with it becomes indefensible.
MAKE THE CALL, THEN COMMUNICATE IT
Notice the order. Decide first. Communicate second. Too many PMs reverse this they communicate the problem, wait for someone else to decide, then communicate the decision. That’s a relay runner, not a leader. Make the call. Tell people what you decided and why. If someone above you wants to override it, let them. But make them override a decision, not fill a vacuum.
◆ ◆ ◆
THE BOTTOM LINE
Construction projects don’t fail because PMs lacked information. They fail because PMs didn’t act on the information they had. Every schedule slip, every budget overrun, every resource that sat idle while someone waited for direction those are the compound interest of indecision.
The industry doesn’t need better reporting tools. It doesn’t need more data. It doesn’t need PMs who can write longer status updates. It needs people who look at a problem, assess the options, pick the best one they can with the information they have, and move. Then do it again tomorrow.
Stop reporting the news. Start making it.
YOUR RESOURCES ARE LEAKING
If your PM team is narrating problems instead of solving them, your utilization rates are paying the price. Let’s find the gap between what your project knows-and what it does about it.
Resource Management 