As someone who has been a PMI member since 1999, I'm considering with some cynicism and amusement the impending release of the next edition of the PMBOK Guide.
While I do understand the need to evolve standards and practice guides over time, I question whether PMI would be better served by helping practitioners better cope with how things really are in their contexts rather than focusing rather exclusively on how things should be.
For example, wouldn't it be great if there was a practice guide which provided practical options for dealing with the most common issues facing PMs? This could include case studies from PMs who had successfully dealt with those issues as well as sufficient context to aid practitioners in figuring out how to proceed.
Luis BrancoCEO| Business Insight, Consultores de Gestão, LdªCarcavelos, Lisboa, Portugal
Kiron Bondale A very timely and insightful reflection and one that resonates with many of us who have witnessed the profession evolve through multiple waves of “guides,” “frameworks,” and “good practices.”
After decades of applying and teaching PMI standards, I tend to agree that the real challenge today is not in codifying how things should be, but in enabling practitioners to navigate how they really are.
The gap is less about knowledge and more about translation, between principle and lived context.
In simple or complicated domains, structure helps; yet in complex or chaotic environments, those same structures often obscure what is actually happening.
As the Cynefin Framework reminds us, maturity lies in the ability to read the system and adapt in real time, not in the elegance of the method, but in the discernment behind its use.
Perhaps PMI is slowly acknowledging this shift.
The PMBOK® Guide (7th Edition) now serves as a foundation of principles and performance domains, defining a shared mindset and vocabulary for our profession.
Meanwhile, the PMI Standards+™ platform complements it by translating those principles into real-world practice, offering contextual guidance, case insights, and adaptive wisdom that connect knowledge with lived experience.
Together they outline a continuum: from principles that guide thinking to practices that inform doing.
That bridge (between intent and application) may be the most meaningful evolution in how PMI supports practitioners today.
Maybe this is where the real value now lies - in the ongoing dialogue between structure and sensemaking, principles and practice, knowledge and experience.
Would you see it that way too?
Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
As somebody that was part of most of the PMI´s standards creation and/or review from 2010 I firmly believe that, in the case of PMBOK, the last version that adds value to our profession was 6th edition. After that everything added confusion instead of value. I agree with you in your point if I understood it well. It could be great to follow the path doing in business analysis related documentation where you have a BOK and a practice guide based on the BOK. On the other side, generative AI made a break in all the professions. The roles as defined by the PMI are "dead" and need to be reinvented or redefined. The PMI is far to that mainly when new certifications without any sense are delivered. Saving Changes...
It's been almost 15 years since I, along with several others, contributed a few chapters to Dave Garrett's book, Project Pain Reliever. This was an attempt to provide approaches to common problems faced by project managers. It would be interesting to see how much of the content would need to be refreshed to be relevant, today. I'm sure my contributions could use a little updating, but there would likely be more new content addressing agile/hybrid challenges.
To Kiron's point, and to speak to part of what Sergio said, we need more than a new /updated Project Pain Reliever. Sergio is not alone in saying that PM roles are dead and project management is evolving so new definitions are needed. There is some evidence for this, but I am more inclined to propose that it's more than role death or evolution. I think that, in many cases, what we're seeing is a rebalancing of the work ecosystem.
What do I mean by that? I think that project management has been over-applied, in some cases; that project managers have been assigned to manage work that wasn't a project, while other roles continue to need to manage projects without formal PM training or titles. That companies are catching on to this and realigning ownership of the work back to a role where it fits better. For example, at a prior employer where I was a project manager and running 6-10 projects at any given time, I also spent three years as as a "scrum master" running a team responsible for fixing bugs and developing enhancements for two different mobile apps. There was no start or end; only releases. It was a good experience, but it wasn't a project.
Now, you could argue that this is an example of how project management is evolving, but that would require changing the definition of a project. I think that one of the outcomes of the growth of agile practices is the recognition of different types of work and different ways of working. There are things that closely resemble projects, but aren't, that have been assigned to project managers in the past, but aren't as frequently today. I think this shift is being misinterpreted as death/evolution of the role.
Where I think PMI would better serve the community, and back in the general direction of Kiron's point, would be in acknowledging the different roles and their expectations. Maybe this would result in additional certifications and BOKs??? I don't know. But it seems like if you follow the notion that PMI's currently defined roles are dead, one possible outcome is that project managers, dealing with time-boxed and unique activities, are going to turn into product managers, managing continuous value delivery for a product.
I do feel it is important to have a standard for how things should be, but rather than trying to be so fluid that it can't hold it's shape, there should be a semi-rigid core supported by the nuances and variations in the application of project management - recognizing that the function of project manager and title/role of project manager may not always be tightly bound. As someone who has been a member of PMI for 20 +/- years, I prefer to think of project management as a profession, but sometimes it's just a skill needed as part of a different role. Conflating the two makes it easier to point to change as proof of the need for evolution and over-extending the standard. Saving Changes...
Program Manager| HARPER SRLSanto Domingo / Distrito Nacional, Dominican Republic
Kiron. Completely agree, much of the PMBOK’s evolution has focused on describing how things should work rather than helping practitioners navigate how things actually unfold in complex environments.
A practical guide filled with real case studies, adaptive tactics, and situational insights would bridge that gap beautifully. Many of us have learned the most not from frameworks, but from seeing how others handled ambiguity, politics, or shifting priorities in the field.
I’d love to see PMI complement its standards with something that captures that lived experience, a kind of “PMBOK in practice.” It would make the guide not just instructional, but applicable.
Saving Changes...
Luis BrancoCEO| Business Insight, Consultores de Gestão, LdªCarcavelos, Lisboa, Portugal
Sometimes I wonder how many of us have actually explored the full ecosystem of PMI publications beyond the PMBOK Guide itself.
Between the Process Groups Practice Guide (2022), the Standards+™ platform, and the Project Success Report (2024), PMI has already addressed many of the gaps we’re discussing here.
These publications together form a continuum (from principles to processes to value) now expanded through the M.O.R.E™ Framework (Manage Perceptions, Own Project Success, Relentlessly Reassess, Expand Perspectives), which connects mindset, responsibility, and capability into the next evolution of our profession.
It seems the real challenge is not the lack of guidance, but how we, as a community, integrate and apply these evolving sources within our collective practice.
...
1 reply by Kiron Bondale
Oct 20, 2025 4:58 PM
Kiron Bondale
...
Luis -
I would agree that there are ancillary resources provided by PMI which do extend to advice for the real world (including the wealth of knowledge they acquired as part of the Disciplined Agile acquisition), but there still is a noticeable bias towards large projects and those environments in which the PM possesses significant power. For practitioners in environments where there are more accidental than "planned" PMs and where organizational maturity for delivery is low, much of the advice is not applicable.
Sometimes I wonder how many of us have actually explored the full ecosystem of PMI publications beyond the PMBOK Guide itself.
Between the Process Groups Practice Guide (2022), the Standards+™ platform, and the Project Success Report (2024), PMI has already addressed many of the gaps we’re discussing here.
These publications together form a continuum (from principles to processes to value) now expanded through the M.O.R.E™ Framework (Manage Perceptions, Own Project Success, Relentlessly Reassess, Expand Perspectives), which connects mindset, responsibility, and capability into the next evolution of our profession.
It seems the real challenge is not the lack of guidance, but how we, as a community, integrate and apply these evolving sources within our collective practice.
Luis -
I would agree that there are ancillary resources provided by PMI which do extend to advice for the real world (including the wealth of knowledge they acquired as part of the Disciplined Agile acquisition), but there still is a noticeable bias towards large projects and those environments in which the PM possesses significant power. For practitioners in environments where there are more accidental than "planned" PMs and where organizational maturity for delivery is low, much of the advice is not applicable.
Kiron
...
1 reply by Luis Branco
Oct 21, 2025 7:14 AM
Luis Branco
...
Kiron Bondale That’s a very important and fair point, and one that deserves more visibility in PMI’s strategic evolution.
Indeed, most formal standards and practice guides still assume a certain level of organizational maturity - governance, sponsorship, and authority structures that many practitioners simply don’t have.
In reality, much of project management today happens in the margins: in environments where power is informal, accountability is shared, and influence outweighs authority.
This is where I believe the next leap for PMI could occur, not just in updating guides, but in reframing how maturity itself is understood.
Maturity is no longer a linear path from chaos to control; it’s contextual fluency - the ability to operate effectively whether structure is strong or fragile.
Disciplined Agile began to open that door by recognizing “context counts,” yet the challenge remains cultural: helping accidental PMs and low-maturity organizations build adaptive capability before compliance.
Perhaps PMI’s future value lies in translating governance into guidance, and frameworks into capacity-building tools that meet practitioners where they are.
In that sense, the evolution of our profession is less about the power we hold, and more about the clarity we bring, especially in places where that power doesn’t formally exist.
Would you agree that this is the real frontier for project management maturity?
Saving Changes...
Luis BrancoCEO| Business Insight, Consultores de Gestão, LdªCarcavelos, Lisboa, Portugal
Oct 20, 2025 4:58 PM
Replying to Kiron Bondale
...
Luis -
I would agree that there are ancillary resources provided by PMI which do extend to advice for the real world (including the wealth of knowledge they acquired as part of the Disciplined Agile acquisition), but there still is a noticeable bias towards large projects and those environments in which the PM possesses significant power. For practitioners in environments where there are more accidental than "planned" PMs and where organizational maturity for delivery is low, much of the advice is not applicable.
Kiron
Kiron Bondale That’s a very important and fair point, and one that deserves more visibility in PMI’s strategic evolution.
Indeed, most formal standards and practice guides still assume a certain level of organizational maturity - governance, sponsorship, and authority structures that many practitioners simply don’t have.
In reality, much of project management today happens in the margins: in environments where power is informal, accountability is shared, and influence outweighs authority.
This is where I believe the next leap for PMI could occur, not just in updating guides, but in reframing how maturity itself is understood.
Maturity is no longer a linear path from chaos to control; it’s contextual fluency - the ability to operate effectively whether structure is strong or fragile.
Disciplined Agile began to open that door by recognizing “context counts,” yet the challenge remains cultural: helping accidental PMs and low-maturity organizations build adaptive capability before compliance.
Perhaps PMI’s future value lies in translating governance into guidance, and frameworks into capacity-building tools that meet practitioners where they are.
In that sense, the evolution of our profession is less about the power we hold, and more about the clarity we bring, especially in places where that power doesn’t formally exist.
Would you agree that this is the real frontier for project management maturity?
...
1 reply by Kiron Bondale
Oct 21, 2025 11:12 AM
Kiron Bondale
...
Agreed - while it is nice to provide guidance for helping the leaders of giga-projects succeed, there are orders of magnitude more small to medium-sized projects being run in companies at lower levels of maturity so the overall impact would likely be greater by focusing in such areas. And, it would go a long way towards reducing the perception that PMI is only interested in large, complex project management and might encourage more accidental PMs to join as members.
Kiron Bondale That’s a very important and fair point, and one that deserves more visibility in PMI’s strategic evolution.
Indeed, most formal standards and practice guides still assume a certain level of organizational maturity - governance, sponsorship, and authority structures that many practitioners simply don’t have.
In reality, much of project management today happens in the margins: in environments where power is informal, accountability is shared, and influence outweighs authority.
This is where I believe the next leap for PMI could occur, not just in updating guides, but in reframing how maturity itself is understood.
Maturity is no longer a linear path from chaos to control; it’s contextual fluency - the ability to operate effectively whether structure is strong or fragile.
Disciplined Agile began to open that door by recognizing “context counts,” yet the challenge remains cultural: helping accidental PMs and low-maturity organizations build adaptive capability before compliance.
Perhaps PMI’s future value lies in translating governance into guidance, and frameworks into capacity-building tools that meet practitioners where they are.
In that sense, the evolution of our profession is less about the power we hold, and more about the clarity we bring, especially in places where that power doesn’t formally exist.
Would you agree that this is the real frontier for project management maturity?
Agreed - while it is nice to provide guidance for helping the leaders of giga-projects succeed, there are orders of magnitude more small to medium-sized projects being run in companies at lower levels of maturity so the overall impact would likely be greater by focusing in such areas. And, it would go a long way towards reducing the perception that PMI is only interested in large, complex project management and might encourage more accidental PMs to join as members.
Kiron
...
1 reply by Luis Branco
Oct 21, 2025 12:11 PM
Luis Branco
...
Absolutely agree, Kiron Bondale, and that’s the paradox, isn’t it?
We now have a wealth of frameworks and resources, yet what many small and mid-sized projects still lack is translation - guidance that meets them where they are, not where theory assumes they should be.
Perhaps that’s where the next evolution lies: turning abundance into contextual fluency and adaptive clarity.
I’ll expand this thought in a separate reflection.
Your point truly captures the heart of it.
Saving Changes...
Luis BrancoCEO| Business Insight, Consultores de Gestão, LdªCarcavelos, Lisboa, Portugal
Oct 21, 2025 11:12 AM
Replying to Kiron Bondale
...
Agreed - while it is nice to provide guidance for helping the leaders of giga-projects succeed, there are orders of magnitude more small to medium-sized projects being run in companies at lower levels of maturity so the overall impact would likely be greater by focusing in such areas. And, it would go a long way towards reducing the perception that PMI is only interested in large, complex project management and might encourage more accidental PMs to join as members.
Kiron
Absolutely agree, Kiron Bondale, and that’s the paradox, isn’t it?
We now have a wealth of frameworks and resources, yet what many small and mid-sized projects still lack is translation - guidance that meets them where they are, not where theory assumes they should be.
Perhaps that’s where the next evolution lies: turning abundance into contextual fluency and adaptive clarity.
I’ll expand this thought in a separate reflection.
Your point truly captures the heart of it. Saving Changes...
Luis BrancoCEO| Business Insight, Consultores de Gestão, LdªCarcavelos, Lisboa, Portugal
From Governance to Guidance: The Next Leap in Project Management Maturity
A summary of a thoughtful exchange with Kiron Bondale, reflecting on how PMI’s evolution from prescriptive standards to adaptive guidance marks a pivotal shift in our profession.
True maturity is no longer a path from chaos to control, it’s contextual fluency: the ability to operate effectively whether structure is strong or fragile.
As project leaders, our challenge is not to hold more power, but to bring more clarity, especially in places where authority doesn’t formally exist.