Why Project Managers Need Different Guidance at Different Stages

One of the quiet assumptions we carry in project management is that experience is cumulative in a straight line. You learn the tools, you master the frameworks, you gain judgment, and eventually, you’re “senior.”

But what if that story is incomplete?

In my recent conversation on Project Management Matters with Jesse Fewell, PMBOK® Guide Eighth Edition Chair and longtime contributor to PMI standards, I found myself confronting a blind spot I didn’t realize I still had: we forget what it felt like to be junior.

It is not due to a lack of empathy, but because experience changes how we see guidance.

From Doing Projects to Shaping a Profession

Jesse’s journey into project management will sound familiar to many: an accidental entry, rooted in technical work, shaped by frustration with how projects were being run rather than by a love of templates or processes.

What stood out wasn’t just how he became a project manager, but when he crossed an invisible line: from wanting to do the work well, to feeling responsible for helping others do the work better. That shift came because of volunteering with PMI.

A single phone call to PMI set off nearly two decades of contribution: agile communities, practice guides, standards work, and eventually chairing one of the most consequential editions of the PMBOK® Guide.

The Seventh Edition and What Happened

The PMBOK® Guide Seventh Edition didn’t quietly evolve like other standards, but it was disruptive to the profession.

It polarized practitioners and challenged long-held expectations. It certainly surfaced uncomfortable questions about value, outcomes, and whether “doing the project right” mattered if we were building the wrong thing.

Jesse does not see this disruption as a mistake, it was necessary. But there had to be a rebalancing and that perhaps can’t be achieved without swinging the pendulum.

The Eighth Edition, which Jesse chaired, didn’t attempt to erase that disruption. Instead, it synthesized it, bringing back structure, processes, and life-cycle thinking, while retaining the emphasis on principles, value, and context.

In the end it was not a retreat, it was a reconciliation.

The Real Insight: Different Practitioners Need Different Guidance

The most important realization Jesse shared wasn’t about standards at all.

It was this:

Project management requires tiers of guidance, because practitioners are at different stages of their journey.

Early-career professionals want clarity, structure, and direction. Senior practitioners rely on judgment, pattern recognition, and trade-offs.

The mistake we make, especially as experienced leaders, is assuming that what we no longer need is no longer valuable.

In reality, standards aren’t failing when they feel “too basic,” they’re serving someone else.

Why Standards Are Still Necessary in an AI World

It’s tempting to ask: why bother with standards when AI can generate a methodology in minutes?

Jesse’s answer was blunt and grounded in reality. AI amplifies what already exists.If your data, processes, and thinking are fragmented, AI doesn’t create intelligence, it scales confusion.

Standards, at their best, don’t compete with AI, they discipline it.

They provide the shared language, structure, and assumptions that make automation and augmentation meaningful rather than dangerous.

Leadership, Volunteering, and the Harder Skill

Leading volunteers to build a global standard isn’t easier than leading employees, it’s harder in different ways. Yes, there’s no paycheck, authority, or compliance leverage, but what remains is purpose, credibility, and trust.

Perhaps that’s the quiet reminder running underneath this entire conversation:

Project management isn’t fundamentally about tools or techniques. It’s about judgment, applied with humility, context, and care for both the work and the people doing it.

A Final Thought

Standards don’t exist to tell you what to think but they are there to help you think better, especially when experience, technology, and pressure tries to short-circuit process.

The profession doesn’t move forward by choosing between tradition and innovation, it moves forward by learning how to hold both at the same time.

Thanks for reading Project Management Matters! Subscribe for free to receive new posts and support my work.