
Stop Turning Project Managers Into Human Glue
When every question, update, approval, and problem lands with one project manager, that person becomes human glue. They spend their day chasing answers, translating decisions, and moving work between people who should be able to work together directly. The team may look busy, but delivery slows down. Skilled consultants wait for direction. Senior people get pulled into minor issues. Billable time drops while coordination time rises.
For a VP of Professional Services, this is more than a project management problem. It's a resource underutilization problem. You already have capable people on payroll, but they can't spend enough time delivering client work. That creates lost revenue, weak utilization, and higher Bench Cost when projects stall or start late.
Adding another project manager might help for a while. But if your workflows still route everything through one person, you'll simply create more human glue. The better fix is to clarify ownership, set better operating rules, and give the team connected information they can trust.
Many project delays begin with a simple question: "Who owns this?"
A consultant finds a data issue. Does the project manager decide what happens next? Does the technical lead? Does the client sponsor need to approve it? If nobody knows, the question goes to the project manager by default.
That default is costly. A project manager may spend 20 minutes getting context, another 20 minutes finding the right person, and more time explaining the answer back to the team. Meanwhile, the consultant waits. Multiply that across several projects, and you can lose hours of productive delivery time every week.
Start by defining ownership for the decisions that happen most often. You don't need a huge process document. A simple project responsibility map can cover the basics:
The project manager owns plan health, risks, schedule changes, and client status communication.
The delivery lead owns technical decisions, quality standards, and work estimates.
Individual consultants own task updates, issue reporting, and completing assigned work.
The account lead owns commercial discussions, expansion opportunities, and contract changes.
The client sponsor owns approvals, priorities, and decisions that affect scope or timeline.
The key is to define not only who does the work, but who can make the call. If every decision requires project manager approval, your team won't move at the speed it should.
Set decision thresholds as well. For example, a delivery lead may be able to adjust task sequencing without escalation. But an estimated 10-hour increase in effort might require project manager review. A change that affects fixed-fee variance, scope, or client commitments should trigger account and client approval.
This protects the project manager from becoming a bottleneck while still keeping control around important decisions. It also gives senior consultants room to lead. That's important when you're trying to improve productive utilization without adding headcount.
2. Replace status-chasing with connected workflows
A project manager often becomes human glue because project information lives in too many places. Tasks are in one tool. Time is in another. Client questions are in email. Resource assignments sit in a spreadsheet. Financial data is held by finance. Nobody has the full picture, so the project manager becomes the person who connects it all.
That isn't sustainable.
When information is disconnected, people ask for updates instead of finding them. A consultant asks whether they should start a task. The project manager has to check the schedule, confirm the client decision, review the assigned hours, and ask another person about a dependency. The work itself may take two hours, but coordinating it can take nearly as long.
Connected workflows reduce this drag. Your team should be able to see, in one place:
What work is assigned and what is due next
Which tasks are blocked and who owns the blocker
Planned hours compared with actual hours
Current resource capacity and upcoming availability
Project budget, WIP, and fixed-fee variance
Pending scope changes and client approvals
This doesn't mean every person needs access to every financial detail. It means each role needs the information required to act without waiting for a project manager to interpret it.
Use simple workflow rules to make this stick. For example, a blocked task should be logged against the relevant project task, not sent as a private message. A scope question should be tagged as a change request, with estimated effort and client impact attached. A consultant should update task progress and time daily, not wait for Friday afternoon.
These habits create cleaner project data. Clean data gives the project manager a clearer view of delivery health. It also helps a service delivery leader spot underutilization early. If someone has open capacity next week, but several projects have unassigned work, that should be visible before the person ends up on the bench.
A PSA platform can bring these signals together. With resource management, project plans, time capture, and financial tracking connected, leaders can make staffing decisions from current data instead of chasing updates across tools.
3. Manage capacity as a delivery asset, not a staffing spreadsheet
Most services teams track who is assigned. Fewer teams actively manage whether those assignments make good use of available capacity.
That gap leads to resource underutilization. One consultant may be overloaded while another has room in their schedule. A project may have budgeted hours but no named resource. A new project may be sold without checking whether the right skills are available. Then delivery starts late, employees get shuffled at the last minute, and Resource Churn rises.
Treat capacity like any other delivery asset. Review it regularly and use it to guide project decisions.
Start with a forward-looking capacity review. Each week, look at the next four to eight weeks and ask:
Who has billable capacity available?
Who is overcommitted?
Which projects have planned work without a confirmed resource?
Which skills will become a constraint?
Where could a delayed client decision create bench time?
Are people spending too much time on internal coordination instead of client delivery?
Separate Billable vs. Productive Utilization in these reviews. A person can be busy with internal meetings, rework, reporting, and status chasing, yet still produce little billable value. Productive utilization helps you see whether delivery time is being used well, not just whether calendars are full.
You should also use WIP limits. If a consultant is assigned to five active projects, they may spend much of the week switching contexts, attending status calls, and waiting on approvals. Giving them fewer active projects, with clearer priorities, may improve delivery speed and quality even if their total assigned hours stay the same.
For fixed-fee projects, capacity discipline is especially important. Every hour spent waiting, redoing work, or resolving unclear ownership increases fixed-fee variance. If that pattern continues, your realization rate falls even though the team appears fully utilized.
A strong resource management process lets you match the right person to the right work at the right time. It also gives you a more honest view of Revenue Backlog. You can see not just what work has been sold, but whether you have the capacity and skills to deliver it profitably.
Project managers should coordinate delivery, not carry the entire operating system on their shoulders. When ownership is clear, workflows are connected, and capacity is managed actively, skilled people can spend more time delivering and less time waiting. Where is human glue slowing down your team today?
About Continuum
Continuum PSA helps services leaders reduce resource underutilization by connecting resource management, project delivery, time tracking, budgets, and revenue data in one system. With clearer visibility into capacity, assignments, project progress, and financial performance, your team can put available skills to work, reduce Bench Cost, and improve profitable delivery without adding unnecessary headcount.



Comments