Less Prescription, More Judgment: The Next Evolution of Project Management

Thank you for your thoughtful contribution — I fully agree that viewing projects as isolated delivery mechanisms is too narrow. Your point that the solution is the real unit of value, and that enterprise architecture provides the integrative context, is critical.
Where I believe our perspectives converge is here: when we elevate the discussion from “project execution” to “enterprise value enablement,” the language naturally shifts. We stop speaking only about processes and start speaking about capabilities, governance, and intentional design.
In that sense, principles do not disappear — they become embedded within architecture, operating models, and decision frameworks. Projects then operate inside that system rather than trying to define it on their own.
Your reference to the business analyst role is also essential. In complex environments, the BA becomes a strategic connector: translating strategy into capabilities, capabilities into requirements, and requirements into delivery outcomes. When BA and PM collaborate inside an architectural frame, the organization is far better positioned to deliver sustainable, scalable solutions.
So, perhaps the real evolution is not “project vs. solution,” but the maturity to orchestrate architecture, business analysis, and project management as complementary disciplines — each necessary, none sufficient alone.
Thank you again — this is exactly the type of discussion our profession needs.

iron — thank you for weighing in.
You are absolutely right to call out that this thinking is not new, and that Disciplined Agile has been advocating “context counts” long before the PMBOK Guide evolved in that direction. In many ways, what we are seeing now is less a revolution and more an overdue convergence: project management, business analysis, enterprise architecture, and agile delivery gradually recognizing they are interdependent lenses on the same value problem.
What I find encouraging is that these ideas are finally moving from specialized communities into the mainstream body of knowledge. That shift matters, because when context-driven approaches become standard practice rather than niche guidance, organizations are better positioned to make disciplined choices instead of applying methods mechanically.
So I appreciate your reminder — it is important to recognize the lineage of these concepts. Building on that foundation, the opportunity now is to deepen the conversation on how leaders actually operationalize “context counts” in complex, real-world environments.
Thanks again for the thoughtful contribution.

You are welcome. On the other side Kiron Bondale hit the nail referring to DA. I am aligned with the original DA, not with the "customization" done by the PMI. On the other side, it is not a matter of principles. The same misunderstanding was created inside Agile for example. It is a matter of understand that organizations are open and adaptable systems that needs to answer to changes in the environment by reacting (Lean) or anticipating (Agile) those changes in order to survive. So, it is a matter of enterprise architecture where principles are just a component. The problem is when organizations that aims to create standards contributes to general confusion just trying to find ways to work things to its advantage jeopardizing the work of lot of people that perform roles related to the discipline.