Gauging PM Work Effort on a Project

PM effort isn’t just meetings it’s complexity, uncertainty, visibility, and team maturity. I’ve seen value in a simple weighted index (size, risk, stakeholder count, visibility) to compare fairly across PMs. Gut feel is important, but structure makes it more transparent.

Tony Carmody
An essential – and often underestimated – dimension of project planning.
Gauging the Project Manager’s work effort is not just about logging hours; it’s about aligning responsibilities with the real complexity, uncertainty, and stakeholder dynamics of the project.

Many times, the PM is expected to “manage everything” without a clear scope of their own role.
I believe that defining the PM's effort should be part of the formal scope planning process, especially in projects where the PM is simultaneously expected to manage change, governance, team development, and strategic alignment.

A few additional thoughts:
- Complexity mapping tools (like Cynefin or Stacey Matrix) can help estimate PM effort beyond just duration or budget.
- Stakeholder entropy (the number and diversity of stakeholders with conflicting interests) often drives the PM's communication and coordination load.
- Organizational maturity plays a key role — in low-maturity contexts, PMs are often forced to fill structural gaps, increasing their actual effort significantly beyond plan.

Would love to see more standardized models (or heuristics) to estimate PM effort based on project typology, governance needs, and stakeholder complexity.

Thanks for raising such a relevant and overlooked topic!

I usually do it by project complexity rather than size alone, factors like stakeholder engagement, risk profile, and governance needs often matter more than duration or budget. A 3-month regulatory project can take more PM time than a 12-month internal upgrade