Project Manager

If a project were a film, the project manager would be the director — not writing the script or operating the camera, but making sure everyone's in the right place, the schedule holds, and the final cut ships on time. It's a coordination role at its core, and in agency life, it's where most scheduling headaches either get solved or created.

A project manager (PM) owns the delivery of a specific project. They define the project timeline, track milestones, manage client expectations, and make sure the team has what they need to deliver every deliverable on the list.

The Daily Juggle

In practice, a PM's week looks like this:

• Monday: Review the allocations for the week. Is the designer actually available, or did another project steal 50% of her time? Check the timeline and adjust.
• Tuesday-Thursday: Run standups, clear blockers, update the client, track budget burn. Flag any scope creep before it metastasizes.
• Friday: Review the week's progress against milestones. Update the schedule if things slipped. Communicate changes to stakeholders.

Most of this work is reactive — things change, and the PM adapts. But the best PMs are proactive: they see the overallocation forming two weeks out and talk to the resource manager before it becomes a crisis.

PM vs. Resource Manager

This is the tension point in every agency. The PM fights for *their* project — they want the best people, full-time, no distractions. The resource manager balances *all* projects — sometimes that means pulling someone from Project A to save Project B.

Good PMs understand this trade-off. They advocate for their project but accept portfolio-level decisions. Great PMs actively collaborate with the resource manager, flagging upcoming bandwidth needs early so allocation decisions aren't last-minute scrambles.

What Makes a PM Effective

A few things separate the great ones from the mediocre:

They know their numbers. Not just the project budget, but the burn rate, the team's utilization, and the profitability forecast. When they ask for more hours, they know the financial impact.

They communicate early. A timeline slip reported two weeks in advance is manageable. The same slip reported the day before the deadline is a disaster.

They protect scope. The PM is the gatekeeper. When a client asks for "one more thing," a strong PM responds with a change request, not a silent nod. Scope creep dies when PMs enforce boundaries.

They use the schedule as truth. A PM who lives in the timeline view, checking allocations daily and adjusting proactively, avoids 90% of the surprises that derail projects. The schedule isn't a formality — it's the single source of truth for who's doing what and when.

In WrkSched, PMs get a project-filtered view of the schedule — all allocations for their project, budget tracking, and the ability to request resource allocation changes without seeing the chaos of the full organization's timeline. It's the PM's command center, focused on what matters: delivering this project.