Perspectives · Knowledge & Practice

Sustainability In Project Management Is Not a Niche. It Is a Knowledge Area.

Project management has always organized itself around types. There are project types — defined by scale, complexity, sector. There are delivery approaches — predictive, iterative, hybrid. There are tools that support analysis and execution. There are organizational functions that govern and coordinate. Each of these categories has a role in how projects are defined, resourced, and run. None of them carries sustainability inside it by default.

That distinction matters because sustainability is frequently sorted into one of those categories. It gets treated as a sector concern, a reporting obligation, or a specialty credential for people whose work happens to touch environmental or social factors. The data does not support that framing.

The gap between stated priority and operational integration is structural, not incidental. And it has a competence dimension. The same study — conducted by Ecosystm and commissioned by Kyndryl and Microsoft across 1,286 enterprise leaders in 20 countries — found that 46% of organizations classify as “legacy-centered,” meaning sustainability is treated as a side activity or compliance task, disconnected from daily operations.

Only 16% qualify as “integration-focused,” with sustainability embedded across strategy and people. The difference between those two groups is not intent. Integration-focused organizations run proactive sustainability initiatives at 72% versus 47% for others, and 76% accelerated their sustainability goals in the past year compared to 31% of the rest.

The knowledge required to work in this space includes impact assessment methods, materiality frameworks, lifecycle thinking, ESG disclosure requirements, stakeholder accountability structures, and the ability to connect project-level decisions to enterprise reporting obligations. These are not incidental skills. The barometer found that 48% of organizations identify lack of clear ROI and difficulty measuring impact as their primary barrier to execution. That is a measurement and governance competence problem, not a commitment problem.

The driver data is also worth examining. The top motivators for sustainability action in the 2025 study were reducing operational costs and improving efficiency (54%), meeting regulatory requirements and avoiding legal or reputational risk (45%), and meeting customer expectations (38%). Regulatory compliance has become more influential, not less — EU standards continue to extend globally through supply chain pressure and disclosure requirements, while US states like California enforce their own climate and disclosure laws.

Practitioners who cannot assess or respond to these requirements in the context of project decisions are not operating outside a niche. They are operating with a gap.

The PMI-GPM joint venture has formalized this through a certification structure, a competence standard, the P5 impact framework, and a practice guide — not as parallel sustainability content, but as infrastructure intended to sit within existing project management knowledge. The structure assumes practitioners working across project types, delivery approaches, and organizational functions require this knowledge. The data confirms why. The practitioner who cannot connect a project decision to a supply chain disclosure, a materiality assessment, or a Scope 3 accountability structure is missing knowledge that 85% of their clients and employers now treat as a strategic priority — whether or not it appears on a credential list.