Veterans do not arrive in civilian organisations as newcomers to projectised work. They arrived having already spent years operating within mission-driven systems that demand clarity of intent, disciplined execution, continuous risk assessment, and learning under pressure. The challenge for workforce development is therefore not how to teach veterans project management from scratch, but how to translate what they already know into a shared professional language that organisations can recognise and trust. 

This essay draws on observed practice within veteran-focused project management initiatives, including VPMMA, to explore why veterans integrate quickly into project and Agile environments, how iterative delivery thinking aligns with military experience, and why international standards such as ISO 45001, ISO 31000, and ISO 9001 provide a useful bridge rather than a new hurdle. 

Projectised Work as a Continuation of Service 

To anyone familiar with modern project delivery, the defining features of projectised work are clear. Teams form around a purpose, operate within time and resource limits, coordinate across functional boundaries, and adapt plans as conditions evolve. Success is judged by outcomes rather than effort, and learning is expected to feed back into future work. 

For veterans, this description is immediately recognisable. Military service is structured around missions that combine planning, execution, coordination, and adjustment. Objectives are explicit. Constraints are real. Risk is present and must be managed continuously rather than reviewed retrospectively. Decisions are taken with incomplete information, often by those closest to the work, guided by intent rather than detailed instruction. 

When veterans enter civilian project environments, they are not encountering a new way of working. They are encountering a new vocabulary. 

What We See in Practice: Learning, Trust, and Networks 

Across veteran mentoring and training pathways, including those supported by VPMMA, several patterns consistently emerge. Veterans tend to engage quickly with project management concepts, not because the material is simple, but because it resonates with prior experience—planning frameworks, delivery cycles, and governance discussions often prompt recognition rather than confusion. 

This recognition has a practical effect. Veterans build confidence early because they are not being asked to abandon their professional identity. Instead, they are learning how to express it differently. Recognition accelerates learning and reduces the hesitation that can accompany mid-career transitions. 

Equally important is the way veterans operate within teams. Military service emphasises trust as an operational requirement. Team members rely on one another not only for performance but for safety and well-being. This experience carries over into civilian settings, where veterans often become stabilising presences within project teams. They communicate clearly, follow through on commitments, and support collective success without needing formal authority. 

Perhaps most significantly, veterans are comfortable operating through lateral networks. Military operations depend on coordination across units, roles, and organisations, often without direct command relationships. Veterans, therefore, adapt well to Agile teams, communities of practice, and matrixed delivery structures where influence is earned through contribution. From a workforce development perspective, this means veterans strengthen not just individual capability but the connective tissue of delivery systems. Iterative Thinking as a Familiar Discipline 

Iterative delivery is sometimes presented as a distinctly civilian innovation, associated with Agile methods and modern product development. In practice, the underlying logic is familiar to anyone with operational experience. Iteration is simply disciplined learning applied over time. 

Military planning and execution are inherently iterative. Initial plans establish direction, but they are continuously adjusted based on feedback from the field. Information flows rapidly, decisions are revisited as conditions change, and learning is captured through structured reviews. The goal is not adherence to an original plan, but effective movement towards the intended outcome. 

Thinking like this aligns closely with contemporary projects and Agile thinking, where short feedback cycles, incremental delivery, and continuous improvement are valued. Veterans often grasp these ideas quickly because they reflect how work has already been done. What they require is not persuasion, but translation. 

Standards as Shared Language, Not New Burdens 

International standards are often introduced to practitioners as external requirements or compliance mechanisms. For veterans, they can serve a different purpose. Standards such as ISO 45001, ISO 31000, and ISO 9001 articulate ways of working that mirror military practice, providing a civilian governance framework for familiar disciplines. 

ISO 45001 emphasises leadership responsibility for safety, proactive hazard identification, and learning from incidents. Veterans are accustomed to systematic safety management and clear accountability for risk. ISO 31000 frames risk as uncertainty affecting objectives, encouraging structured assessment and adaptive response, which reflects how military planning treats risk as integral to decision-making rather than something to be eliminated. ISO 9001 focuses on process clarity, consistency, feedback, and improvement, all of which are embedded in standard operating procedures and after-action reviews. 

Seen through this lens, standards do not represent a departure from military experience. They provide a way to describe that experience in terms of organisations that already recognise and value. 

The Language Barrier That Still Matters 

Despite this strong alignment, veterans often encounter difficulty when first engaging with civilian project management environments. This difficulty rarely stems from a lack of capability. It stems from language. 

Military roles are rich in responsibility and complexity, but their titles do not map neatly onto civilian job descriptions. Project management terminology can feel abstract or overly formal, while military language may be unfamiliar to hiring managers and colleagues. Without an explicit translation layer, valuable experience can remain hidden in plain sight. 

Workforce development efforts have the greatest leverage. When veterans are supported in learning the civilian language of projects, and when organisations are supported in understanding military experience through that language, integration becomes significantly smoother. 

Translation as an Enabler of Inclusion and Delivery 

Translation does not require simplifying or diminishing either domain. It requires recognising equivalence. When veterans learn that a mission is understood as a project, that the commander’s intent resembles a project vision, or that an after-action review is recognised as a retrospective, they gain confidence in articulating their experience. When project managers learn to hear military terms as indicators of governance, coordination, and risk management, they gain access to a deeper pool of capability. 

At VPMMA, the use of simple translation tools has repeatedly shortened onboarding time and improved mutual understanding. Veterans are better able to describe what they have done, and project teams are better able to see how that experience fits their needs. This shared language supports both individual development and organisational performance. 

Workforce Development Implications 

For organisations grappling with skills shortages, complex delivery, and an increasing reliance on project-based work, veterans represent a valuable, often underutilised talent pool. The evidence from practice suggests that effective veteran workforce development programmes focus less on retraining and more on articulation. 

Workforce development involves treating certifications as shared language rather than gatekeeping mechanisms, valuing networked capability alongside individual competence, and recognising that much of what is sought in modern project environments is already present in military experience. When programmes are designed with these principles in mind, veterans integrate quickly and contribute meaningfully to delivery outcomes. 

Conclusion

Veterans bring with them experience in structured execution, adaptive decision-making, and collaborative delivery within complex systems. Project management frameworks, iterative delivery approaches, and international standards provide a common language for expressing that experience within civilian organisations. 

A focus on translation, shared understanding, and networked capability enhances workforce development initiatives and supports veterans in continuing to do what they already do well, while helping organisations deliver projects more effectively in an increasingly projectised economy. 

Appendix A: Annotated References 

Project Management Institute. A Guide to the Project Management Body of Knowledge (PMBOK® Guide), 8th Edition. 
Provides a principles-based view of project governance aligned with adaptive delivery and continuous learning. 

International Organisation for Standardisation. ISO 45001: Occupational Health and Safety Management Systems. 
Articulates leadership-led approaches to safety and risk prevention consistent with military operational practice. 

International Organisation for Standardisation. ISO 31000: Risk Management – Guidelines. 
Frames risk as uncertainty affecting objectives, aligning closely with mission planning and decision-making. 

International Organisation for Standardisation. ISO 9001: Quality Management Systems. 
Emphasises process discipline, feedback, and continuous improvement as organisational capabilities. 

Appendix B: Language Bridge for Veterans and Project Teams 

Military and project management language often describe the same practices using different terms.  

Making these connections explicit reduces friction and improves collaboration. 

• Mission aligns with project or initiative. 
• Commander’s intent aligns with the vision or objectives. 
• Operations orders align with project plans. 
• After-action reviews align with retrospectives or lessons learned. 
• Threat assessments align with risk identification and analysis. 
• Logistics aligns with resource management. 
• The chain of command aligns with governance structures. 
• Battle rhythm aligns with delivery cadence. 

Appendix C: Discussion Prompts for Project Teams 

• How does continuous monitoring in military contexts compare with assurance practices in your organisation? 
•  Where do you see ISO-style thinking already present in veteran experience? 
•  How might delivery improve if experience were assessed primarily through outcomes rather than role labels? 

The post Veterans and Project Management: Building Capability for a Projectised Workforce  appeared first on Institute of Project Management.

Correctional facilities are resource-intensive and socially consequential institutions. Traditional approaches often emphasise containment and cost control, leading to underperformance in rehabilitative outcomes and environmental responsibilities.

This paper introduces an integrated framework to transform correctional facilities into regenerative, health-centred, and resilient environments by aligning WELL and LEED building standards with Agile governance practices under a P5 (People, Planet, Prosperity, Process, Product) lens. ¹ It articulates design interventions (renewables, water reuse, waste valorisation), AI-enabled building management systems, and governance mechanisms (cross-functional Agile teams, KPI-driven iterative cycles) to achieve measurable environmental, operational, and social benefits. Rather than presenting primary empirical findings, this manuscript provides a practical implementation roadmap and evaluation methodology suitable for policy makers, infrastructure planners, and project leaders operating in constrained environments. No speculative numeric claims are included. 

1. Introduction 

Correctional facilities represent a nexus of infrastructure, governance, social justice, and environmental stewardship. These institutions have substantial energy, water, and waste footprints while simultaneously shaping human well-being and societal reintegration outcomes. 

This manuscript argues that regenerative design, when coupled with Agile governance and structured through the P5 framework, can reorient correctional facilities from static containment assets to dynamic platforms for rehabilitation, skills development, and environmental performance. WELL and LEED standards provide technical performance and occupant health metrics; Agile and Green Project Management practices translate these standards into operational routines and measurable outcomes. ²

This manuscript is presented as a conceptual and design-oriented framework intended to support policymakers, infrastructure planners, and correctional authorities in pilot planning and evaluation, rather than to report primary empirical findings. 

2. Background 

2.1 Sustainability and the Built Environment 

LEED and WELL standards offer complementary metrics for environmental performance and occupant health. LEED focuses on energy efficiency, water use, material selection, and emissions, while WELL emphasises occupant health through air, water, nourishment, lighting, and comfort. Interventions relevant to correctional contexts include: 

• High-performance envelope systems 

• Renewable energy integration (PV, microgrids, battery storage) 

• Greywater reuse and rainwater harvesting 

• Natural daylighting and circadian lighting 

• Biophilic therapeutic spaces ³

These standards enable environmental, health, and comfort improvements when thoughtfully applied. 

2.2 Governance and Leadership 

Governance innovations, particularly Agile practices adapted to public institutions, support decentralised decision-making, iterative implementation, and stakeholder engagement. ⁴ Agile methods such as sprints, retrospectives, and KPI dashboards align operational processes with sustainability and rehabilitation goals. ⁵

2.3 Rationale for Integration 

Design without operational alignment can result in underutilised systems and missed outcomes. Conversely, governance without supportive infrastructure limits impact. ⁶ Integrating technical design with governance practices ensures that sustainability intentions become daily operational realities. ⁷

2.4 Regenerative Practice Beyond Correctional Facilities: Climate Change and Indigenous Communities 

Regenerative approaches extend beyond correctional and built environment contexts. Climate change research with Indigenous communities illustrates how regenerative principles operate across ecological, cultural, and sensory systems. ⁸ For example, in Nigeria’s Niger Delta, saltwater intrusion has changed the taste and smell of freshwater, disrupting fishing, agriculture, and trust in environmental signals.⁹

Adaptation strategies combine traditional ecological knowledge with participatory research and community monitoring, grounded in reciprocity and long-term stewardship. These cases show that regeneration is about restoring relationships between people, place, and process, offering insights directly relevant to correctional facilities. ¹⁰¹¹

Taken together, insights from correctional infrastructure and Indigenous climate adaptation highlight that regeneration operates through layered systems in which environment, governance, technology, and human experience continuously interact. These cross-domain lessons inform the integrated conceptual model presented next, translating regenerative principles into an operational framework applicable to correctional facilities. 

3. Integrated Conceptual Model 

3.1 Framework Overview 

The proposed model is layered and cyclical, connecting: 

Built Environment → AI-Enabled Building Management Systems (BMS) → Programs & Vocational Training → Agile Governance 

These layers operate across the correctional lifecycle: Intake → Custody → Programs → Reentry. The P5 framework translates strategic sustainability and social goals into operational requirements at each layer. 

FIGURE 1: Integrated conceptual model — layers, lifecycle stages, and P5 mapping. 

3.2 Operational Layers 

• Design & Infrastructure: WELL- and LEED-aligned building systems, resilient energy and water infrastructure, biophilic spaces. 

• AI & BMS: Predictive maintenance, microgrid optimisation, indoor environmental quality monitoring. 

• Programs & Vocational: Green-collar training, horticulture therapy, restorative justice activities . 

• Governance & Operations: Cross-functional Agile teams, KPI dashboards, stakeholder steering committees. 

3.3 Practical Vignette 

A pilot housing unit installs solar PV, battery storage, and environmental sensors. An Agile team runs four-week sprints consisting of baseline monitoring, staff and participant training, BMS optimisation, and outcome assessment to inform upscaling decisions. 

4. P5 Mapping for Correctional Facilities 

5. Design and Technical Considerations 

5.1 Energy and Resilience 

Resilient renewable energy systems with battery storage support critical loads and enhance operational continuity. AI-driven BMS enable load shifting, demand response, and predictive control strategies. ¹² 

FIGURE 2: Microgrid and BMS integration diagram. 

5.2 Water and Waste 

Greywater reuse systems and rainwater harvesting reduce potable water use, while on-site composting and anaerobic digestion support waste valorisation and vocational training. ¹³ 

5.3 Indoor Environmental Quality (IEQ) 

Continuous monitoring of CO₂, PM₂.₅, and VOCs, along with demand-controlled ventilation and circadian lighting, enhances IEQ and supports well-being. ¹⁴ 

6. Programs, Training, and Rehabilitation 

Accredited green-skills curricula (e.g., solar installation, HVAC maintenance), horticulture therapy, and restorative programs create structured pathways to reintegration. Formal partnerships with employers and community services enhance employment outcomes.¹⁵ 

7. AI, Data Governance, and Ethics 

AI applications in correctional environments require stringent ethical safeguards: 

• Privacy by design 

• Data minimisation 

• Human-in-the-loop decision protocols 

• Transparent algorithmic reporting 

• Independent audits  

8. Key Performance Indicators (KPIs) 

• Environmental: energy use reduction, potable water reduction, waste diversion rate.

• Social: program participation rates, well-being score improvements, recidivism tracking.

• Operational: mean time between failures, reactive maintenance cost reductions, AI false-positive rates.

• Governance: sprint completion rate, percentage of KPIs achieving targets, stakeholder satisfaction.

9. Evaluation Strategy and Research Design 

A structured evaluation protocol leveraging interrupted time series analysis and quasi-experimental pre/post comparisons is proposed. Administrative and operational datasets, combined with qualitative interviews, provide robust evidence of impact without necessitating direct facility access. ¹⁶

10. Conclusion 

By aligning regenerative design, AI-enabled operations, and Agile governance under a P5 lens, correctional facilities can evolve into health-centered, resilient systems that support rehabilitation and reintegration. Insights from Indigenous climate adaptation further reinforce regeneration as a cross-domain practice rooted in relationship, sensory awareness, and long-term stewardship.

References

1. GPM Global. (2025). The GPM P5 Standard for Sustainability in Project Management ︎
2. Booz Allen. (2026). Agile Transformation. ︎
3. Söderlund, J., & Newman, P. (2017). Improving Mental Health in Prisons Through Biophilic Design. ︎
4. Al-Shamsi, I. R., & Shannaq, B. (2024). Leveraging clustering techniques to drive sustainable economic innovation in the India–Gulf interchange. Cogent Social Sciences. ︎
5. Booz Allen (2026). ︎
6. UNICRI. (2025). Green Prisons: A Guide to Creating Environmentally Sustainable Prisons. ︎
7. GPM Global. (2025). Sustainable Project Management; The PMI-GPM Practice Guide. ︎
8. Smith, L. T. (2012). Decolonising Methodologies: Research and Indigenous Peoples (2nd ed.). London: Zed Books.  ︎
9. Olaniyan, O. (2017). Sustainable Development of Ibadan: Past, Present and Future. Centre for Sustainable Development, University of Ibadan. ︎
10. Garcia, E. J., & Vale, B. (2017). Unravelling sustainability and resilience in the built environment. Routledge. ︎
11. Smith (2012). ︎
12. EMHIC. (2026). Building JARA: A judgment-free AI companion for youth and young adults who use substances or alcohol. ︎
13. Sustainability in Prisons Project. (2024). 2024 Annual Report. ︎
14. Söderlund & Newman (2017) ︎
15. Sustainability in Prisons Project. (2024). ︎
16. UNICRI (2025). ︎

Appendix A. Technical Parameters and Checklists 

A.1 Engineering Parameter Table (rules of thumb & engineering references) 

• PV_kW_per_bed: Photovoltaic system sizing based on regional solar irradiance, security load profiles, and per-capita energy demand benchmarks for correctional facilities. 

• Battery_kWh_per_critical_load: Battery storage capacity calculated to sustain identified critical loads (security systems, healthcare units, data centres) for a minimum of 8–24 hours during grid outage scenarios. 

• Battery_roundtrip_efficiency: Expected round-trip efficiency (typically 85–92%) used for lifecycle cost analysis and operational energy modelling. 

• Critical_load_fraction: Proportion of total facility electrical demand classified as critical, typically ranging between 35–55% depending on security level and healthcare services. 

• PV tilt/azimuth: Optimised according to latitude and seasonal load priorities to maximise annual and winter-period energy yield. 

• Inverter capacity margin: Minimum 10–15% oversizing to accommodate peak loads and system degradation. 

• Indoor Air Quality (IAQ) thresholds: CO₂ < 800 ppm; PM₂.₅ < 12 µg/m³; VOCs compliant with WELL v2 standards. 

• Ventilation rates: Demand-controlled ventilation aligned with ASHRAE 62.1 and WELL Air concepts. 

• Circadian lighting specifications: Day–night lighting cycles with melanopic lux targets supporting sleep regulation and psychological well-being. 

• Sensor sampling interval: Environmental sensors operating at 5–15 minute intervals for real-time monitoring and AI-driven optimisation. 

• BMS data retention: Minimum 24–36 months of operational data stored for performance auditing, predictive analytics, and compliance reporting. 

These parameters are provided as engineering reference values to support pilot design, feasibility studies, and post-occupancy evaluation rather than prescriptive specifications. 

Appendix A — Table A 

LEED / WELL Checklist and Evidence Requirements 

The post Regenerative Correctional Facilities: Sustainable Rehabilitation  appeared first on Institute of Project Management.

Chaos theory, first articulated in the 1960s by meteorologist Edward Lorenz, emerged from the study of nonlinear systems such as weather patterns, ecosystems, and financial markets. It demonstrates that systems governed by simple rules can still produce behaviour that is unpredictable and highly sensitive to initial conditions — a concept famously known as the “butterfly effect.” 

In the context of project management, chaos theory offers powerful insights into why projects — even well-managed ones — can veer off course, and how leaders can design systems that are more resilient, adaptive, and capable of thriving amid uncertainty. 

The Butterfly Effect in Project Management 

Large-scale transformations — whether digital, organisational, or cultural — are inherently complex. They involve multiple stakeholders, systems, and feedback loops that amplify small changes. Consider a scenario in which a minor adjustment in project scope triggers cascading effects: resource allocation shifts, delivery timelines compress, dependencies move, team morale fluctuates, and expenses increase. What initially appeared benign can evolve into a project-wide disruption. 

This phenomenon mirrors the butterfly effect. In projects, sensitivity to initial conditions means that even small misalignments — such as an underestimated task, a delayed decision, or a misinterpreted requirement — can produce outcomes far removed from what was originally intended. 

For complex projects, this implies that disruption and uncertainty should not be viewed solely as risks to mitigate, but also as opportunities for adaptation and evolution. When a project team encounters unexpected challenges — such as regulatory shifts, technological breakthroughs, or sudden market changes — these events can catalyse creative problem-solving and lead to outcomes superior to the original plan. 

In complex systems, intervention itself alters behaviour. Each decision reshapes the environment in which future decisions are made — a form of self-reinforcing feedback that drives unpredictability. This explains why even comprehensive risk registers often fail to anticipate the most consequential events. 

Leadership in such environments requires comfort with ambiguity and the confidence to act without complete information. Instead of enforcing predictability, effective leaders cultivate clarity of purpose — a shared vision and guiding principles that maintain alignment even as plans evolve. 

As global transformation accelerates — driven by artificial intelligence, digital ecosystems, and socio-economic interdependencies — project managers must evolve into adaptive architects who design structures capable of learning, evolving, and thriving amid constant change. 

Ultimately, managing complex projects in an age of uncertainty requires a mindset shift: from predicting a single future to preparing for multiple futures; from controlling variables to cultivating adaptability; and from rigid execution to dynamic evolution. 

Chaos theory reminds us that even within apparent disorder, there is an underlying structure waiting to emerge — if we know how to recognise it, nurture it, and allow it to develop. 

The post Lessons from Chaos Theory: Managing Uncertainty in Complex Projects  appeared first on Institute of Project Management.

In project and quality management, the GEMBA walk remains one of the most underutilised yet strong tools for promoting meaningful improvement. Rooted in the Japanese term Gemba, meaning “the actual place,” a GEMBA walk involves leaders stepping away from their desks to observe work where it happens on the shop floor, in the service area, or at the project site. It’s a chance to see processes in action, engage with frontline staff, and collect insights that rarely surface in reports.  

But beyond the operational lens lies a deeper opportunity: the human lens. When leaders observe not just tasks, but behaviours, emotions, and mindsets, they begin to understand the psychological drivers that shape quality outcomes. This article studies how GEMBA walks, when considered with empathy and curiosity, can reveal the emotional flows of performance, and how these findings can be harnessed to build a culture of sustainable, people-led improvement.  

Reframing GEMBA—From Observation to Empathy  

GEMBA walks have long been used to review processes, spot errors, and ensure teams are following the rules. In many organisations, they’re seen as a way to monitor performance and tick off compliance boxes. But when GEMBA walks, it focuses only on systems and outputs; it misses something important—the people behind the work.  

A human-centred GEMBA walk looks beyond tasks and tools. It pays attention to how people behave, interact, and feel. Leaders who walk with sympathy notice more than just broken steps in a process; they pick up on body language, tone of voice, and emotional signs. Is someone rushed, disengaged, or quietly solving problems no one else sees? Such cues tell us a lot about the culture of quality.  

Active listening plays a key role. Asking open questions, displaying genuine interest, and giving space for honest feedback assists in building trust. When people are listened to, they’re more likely to share ideas, raise concerns, and take ownership of improvement.  

This is where understanding leadership becomes a lever for quality. It’s not about being soft; it’s about staying present, curious, and responsive. Leaders who connect with their teams during GEMBA walks help shift the mindset from “follow the rules” to “make it better.”  

Behavioural Signals of Quality Culture  

One of the most valuable aspects of a GEMBA walk is the insight gained simply by observing how people behave. Everyday actions, how someone responds to a challenge, interacts with colleagues, or chooses to take initiative rather than wait for instruction, can speak volumes about a team’s quality culture.  

A strong culture tends to show up through ownership, curiosity, and an authentic drive to improve. You’ll notice people asking considered questions, offering ideas, or quietly resolving matters before they escalate. In contrast, a weaker culture may appear as avoidance, finger-pointing, or doing just enough to get by. Crucially, these behaviours are rarely random; they’re determined by how people feel. Confidence promotes action, while fear often leads to silence. Motivation drives progress, whereas burnout leads to disengagement.  

During a GEMBA walk, such signals appear in real time. For instance, a trainer who improvises a workaround might be demonstrating resourcefulness, but it could also highlight gaps in process clarity or support. Likewise, a worker who avoids eye contact may be feeling overwhelmed or disconnected. These delicate signals are easy to overlook unless leaders are fully present and attuned.  

When leaders take the time to visit the workplace and speak with staff during a GEMBA walk, something important happens. When individuals feel genuinely seen and heard, the dynamic alters from being observed to being valued, and this change can deeply influence engagement, trust, and the impulse to contribute.  

By recognising these behaviours and linking them to emotional states, leaders gain a deeper understanding of what’s happening beneath the surface. It’s not about passing judgment, it’s about learning. GEMBA walks offer a rare chance to observe the human side of quality and to respond with consideration, clarity, and meaningful support.  

Mindset Shifts Through Frontline Engagement  

Rather than merely following instructions, employees start to take genuine ownership of their work. They move from passive compliance to active engagement, contributing ideas and seeking improvements. This transformation in mindset rarely stems from formal meetings or written reports; instead, it grows through routine interactions. A brief conversation, a thoughtful question, or a moment of sincere recognition can ignite confidence and inspire motivation.  

Recognition plays a vital role in promoting ongoing improvement. When people feel their efforts are genuinely noticed, they’re more likely to stay motivated and keep striving for better outcomes. Curiosity is equally important. Leaders who ask open, considered questions show they’re interested in understanding, not simply ticking boxes. This procedure helps build trust.  

When participants feel safe to speak up without fear of criticism or blame, they’re far more likely to share ideas, raise concerns, and take part in significant change. This sense of psychological safety, combined with daily moments of recognition and sincere engagement, supports building trust across teams. Over time, these tiny interactions create momentum. People begin to believe that their input matters, and that improvement is something they can influence, not just something handed down from above. Together, these parts develop a culture where improvement is not enforced, yet embraced.  

GEMBA walks, when done with empathy and openness, help unlock this potential and remind us that quality isn’t just about systems; it’s about people, and surely people thrive when they feel respected, supported, and involved.  

Sustaining Improvement Through Emotional Intelligence  

Sustaining improvement isn’t just about systems and checklists; it’s about people. Emotional intelligence, or EQ, plays a key role in how leaders connect with their teams during GEMBA walks. When leaders express empathy, listen carefully, and answer thoughtfully, they create an environment where assurance can grow, and improvement becomes part of the culture.  

One way to build EQ is via reflective questioning: instead of jumping to conclusions, leaders can ask open questions like “What’s working well here?” or “What would make this easier for you?” These kinds of questions display genuine interest and invite honest feedback. Paying attention to body language is just as important.  

A quiet tone, crossed arms, or moments of hesitation can all signal stress or uncertainty, slight signs that won’t appear in a report but carry real weight. That’s why follow-through is so important. When leaders respond to what they hear, even in small, practical ways, it sends a clear message: feedback is appreciated, and change is not only possible but taken seriously. This can establish trust and encourage people to keep sharing openly.  

Emotionally intelligent GEMBA walks help teams build resilience by forming an environment where people feel safe to speak up, take initiative, and learn from their mistakes. Over time, this encourages self-correcting behaviours; teams don’t wait to be told what to do; instead, they start improving things because they genuinely care.  

What’s powerful is how naturally this approach fits with quality frameworks like PDCA and DMAIC. During the “Check” phase, for example, leaders aren’t just tracking performance, they’re also paying close attention to the emotional atmosphere. Then, in the “Act” phase, they respond in ways that support their people, not just the process. By weaving emotional intelligence into these cycles, improvement becomes more human, more meaningful, and ultimately leads to lasting change.  

Conclusion  

At its heart, a GEMBA walk is much more than a routine check; it opens an insight into the human side of quality. By stepping directly into the workplace and engaging with people face-to-face, leaders obtain insights that no dashboard or report can capture. It’s in these day-to-day moments, observing how teams interact, listening to their concerns, and noticing what’s left unvoiced, that the real story of quality comes to life.  

Ultimately, sustaining quality means recognising that systems and tools alone aren’t enough; it’s the people behind them who drive real change. That’s why GEMBA walks shouldn’t just be another item on the calendar. Instead, they can become a habit of connection, a regular practice of learning, and a clear signal that each voice counts.  

When leaders approach these walks with empathy, curiosity, and emotional acuity, they do more than inspect; they connect. This creates trust, encourages openness, and creates room for meaningful improvement. In turn, this kind of leadership doesn’t just solve problems; it strengthens the entire culture and empowers people to take real ownership of their work.  

Let every walk be a step toward deeper trust, richer insight, and lasting improvement. 

The post The Human Lens of Quality: GEMBA Walks & Continuous Improvement   appeared first on Institute of Project Management.

Learning lessons on project management is essential for both personal and organisational growth.   

Studying both good and bad experiences will help improve future performance, avoid repeated mistakes, and strengthen team collaboration.  Namely: 

• Continuous Improvement – Learning lessons enables project teams to analyse what worked well and what did not, fostering a culture of continuous improvement and helping them refine their processes and methods for future projects. Over time, this leads to greater efficiency, better planning, and more consistent project success. What worked well and what did not.  Learning lessons creates a culture of continuous improvement, helping teams refine their processes and methods for future projects. Over time, this leads to greater efficiency, better planning, and more consistent project success. 

• Avoiding repeating the same mistakes – By documenting and reviewing lessons learned, teams can identify the root causes of problems or failures, helping ensure that the same errors are not repeated, saving time, money, and resources on future projects. 

• Knowledge Sharing – Lessons learned sessions help transfer knowledge between team members, especially when staff turnover occurs.  New or less experienced team members can benefit from the insights of others, enhancing the team’s overall capability. 

• Improving Risk Management – Lessons learned often reveal unforeseen risks and how they were handled, thereby improving future risk identification and mitigation, making the organisation more resilient and better prepared. 

• Strengthening Communication and Collaboration – Reflecting on project outcomes encourages open dialogue about successes and challenges.  This transparency fosters trust, teamwork, and a culture of accountability. 

• Enhancing Decision-Making – Historical lessons provide valuable data that can inform better decision-making in future projects. Managers can use this information to set realistic timelines, budgets, and resource plans. 

• Organisational Learning and Maturity – Consistent application of lessons learned contributes to organisational project management maturity.  It helps develop standard practices, templates, and frameworks that improve overall project delivery. National project management maturity.  It helps develop standard practices, templates, and frameworks that improve overall project delivery. 

And this learning approach is particularly important for global mega projects. 

So, what is a Global Mega Project? 

Global Mega projects have long been seen as the ultimate expression of human ambition and national progress.  They often symbolise a country’s aspirations for modernisation, economic expansion, and global influence.  

Furthermore, they are large-scale, complex undertakings that will take a long time to implement (often measured in decades)—for example, airports, bridges, dams, and transportation systems. However, history shows that these projects are double-edged swords—for example, airports, bridges, dams, and transportation systems. However, history shows that these projects are double-edged swords.  

While they can bring enormous social and economic benefits, they are also prone to risks such as high levels of complexity, financial overruns, political interference, and environmental degradation.  

Therefore, examining the lessons from mega (both the good and the bad), we can understand how ambition and pragmatism must coexist for success.) lessons from mega, we can understand how ambition and pragmatism must coexist for success. 

The Promise of Global Mega Projects

These projects can be engines of technological advancement, economic growth, and national pride. When executed well, they have the power to reshape societies and create long-term benefits that outweigh their costs. 

Innovation and Technological Advancement

One of the most positive outcomes of mega projects is the drive toward innovation. These projects push engineers, scientists, and architects to solve unprecedented challenges.  

A prime example is the Burj Khalifa in Dubai, the tallest building in the world. Its construction required pioneering solutions to manage wind resistance and ensure stability on Dubai’s sandy foundations.  

Similarly, France’s Millau Viaduct, the tallest bridge in the world, represents a masterpiece of design and engineering precision, combining functionality with aesthetic elegance. 

Another example is the Channel Tunnel (or “The Chunnel”), which connects the United Kingdom and France. Completed in 1994, it required advanced tunnelling technology and international cooperation between two nations with different engineering standards. The result was not only a remarkable technical feat but also a symbol of European integration.

These projects show that ambition, when matched with innovation, can push human capability forward and create technologies that benefit other industries as well. 

Economic Growth and Connectivity 

Successful mega projects can act as catalysts for economic transformation.  

Japan’s Shinkansen high-speed rail network, launched in 1964, is one of the best examples. It revolutionised travel, drastically cutting journey times and linking previously isolated regions. Beyond convenience, it spurred economic growth, encouraged domestic tourism, and reduced regional inequality. It encouraged travelling, drastically cutting journey times and linking previously isolated regions. Beyond convenience, it spurred economic growth, encouraged domestic tourism, and reduced regional inequality. 

In China, the Beijing–Shanghai High-Speed Railway has had a similar effect, carrying over 200 million passengers annually and boosting economic integration along its corridor. ¹ Likewise, the Hong Kong-Zhuhai-Macao Bridge, the world’s longest sea-crossing, has improved trade and tourism links among the three major cities, promoting long-term regional cooperation. 

These examples highlight how mega projects, when carefully planned and aligned with economic goals, can enhance productivity, job creation, and trade. 

National Prestige and Symbolism 

Mega projects often serve as powerful symbols of progress and identity.  

The Panama Canal expansion project, completed in 2016, not only increased the canal’s capacity but also re-established Panama’s central role in global trade. The project turned a national asset into a modern engineering marvel, elevating Panama’s global profile. 

Similarly, the Three Gorges Dam in China—one of the largest hydropower projects in the world—represents both technological prowess and national ambition. Though controversial, it underscores the scale of China’s engineering capability and determination to harness renewable energy. 

What are the Pitfalls of Mega Projects? 

Despite their promise, mega projects are notoriously prone to failure. Studies show that nearly 90% of mega projects exceed their budgets or schedules, and many fail to deliver expected benefits. The reasons are complex: over-optimism, political pressures, and inadequate planning often lead to costly mistakes. 

Cost Overruns and Financial Risk 

Perhaps the most consistent challenge is financial overrun.  It is not uncommon for projects to overspend many times over their original budget. 

The Boston “Big Dig”, originally estimated at $2.8 billion, ended up costing more than $14.6 billion (or over five times its initial budget). ² Often, mismanagement, design changes, and unforeseen geological conditions contributed to these spiralling costs. 

Similarly, Scotland’s Edinburgh Tram Project faced major budget inflation and delays due to contractual disputes and poor coordination. ³ What began as a project to enhance urban transport became a financial strain on taxpayers. 

Even the Sydney Opera House, now an architectural icon, experienced this problem. Initially budgeted at $7 million, it ultimately cost over $100 million and took 14 years to complete, rather than 4. While it eventually became a source of national pride, its troubled construction serves as a reminder that innovation must be paired with realistic cost control. ⁴

Delays and Management Failures 

Large-scale projects require immense coordination among contractors, governments, and stakeholders. When management fails, delays are inevitable.  

The Berlin Brandenburg Airport is a textbook example.  It was meant to open in 2011 but did not begin operations until 2020 due to technical flaws, design errors, and bureaucratic inefficiency. ⁵

Such delays not only inflate costs but also damage public confidence and can create a sense of national embarrassment. The lesson here is clear: strong leadership, effective communication, and independent oversight are critical to keeping mega projects on track. 

Social and Environmental Costs 

Mega projects often disrupt communities and ecosystems.  

The Three Gorges Dam, while producing vast amounts of hydropower, forced the relocation of more than a million people and flooded archaeological sites. ⁶

Similarly, Brazil’s Belo Monte Dam caused deforestation and displaced indigenous communities in the Amazon, raising ethical concerns about the human price of development. ⁷

Infrastructure projects, such as highways and urban redevelopment, can entail social costs. For example, in the U.S., mid-20th-century highway projects often destroyed neighbourhoods, disproportionately affecting marginalised communities. 

Over-ambition and Political Pressure 

Sometimes, mega projects are conceived more for political prestige (or pride) than any real practical benefit.  

North Korea’s Ryugyong Hotel, standing empty for decades, reflects how over-ambition and lack of feasibility can lead to wasted resources.  

Similarly, Spain’s Ciudad Real Airport, built at enormous cost but largely unused, shows how projects disconnected from genuine demand become “white elephants.” 

Political leaders often champion these ventures as legacy projects, leading to rushed decisions and inflated expectations. When political agendas override technical assessments, the result is often failure. 

So, what lessons (both good and bad) can be learnt from Global Mega Projects? 

The history of these projects teaches us that success depends on a careful balance between ambition and realism, speed and sustainability, innovation and accountability.  

To achieve this balance, several lessons stand out: 

• Be realistic regarding what can be done:  Massive transformative change sounds great, but it is challenging, especially if the change takes many years to be implemented.  Therefore, it is much better to focus on a series of smaller changes which will (a) be easier, less risky and cheaper to implement so that (b) benefits will be provided to the relevant stakeholders.  Also, delivering projects in smaller ‘chunks will build confidence that changes can be delivered. 

• Integrate Long-Term Planning: Mega projects should fit into broader national development strategies, ensuring they meet real needs rather than short-term political goals. 

• Enhance Transparency and Oversight: Independent audits and public accountability can help detect early warning signs of failure. 

• Adopt Flexible Management Models: Given their complexity, mega projects must adapt to changing circumstances rather than rigidly follow outdated plans. 

• Prioritise Sustainability and Inclusion: Environmental and social considerations should be integral, not afterthoughts. 

• Encourage International Collaboration: Cross-border projects such as the Channel Tunnel and the International Space Station demonstrate how cooperation can yield shared benefits and drive innovation. Cross-border projects like the Channel Tunnel and the International Space Station demonstrate how cooperation can yield shared benefits and drive innovation. 

Conclusion

Global Mega projects represent the pinnacle of human ambition—namely, monuments to progress, creativity, and determination.  

From the soaring Burj Khalifa to the vast Three Gorges Dam, they show what humanity can achieve when it dreams boldly.  

Yet the same projects also remind us of the consequences of overreach, such as financial strain, environmental damage, and social displacement. 

The ultimate lesson from mega projects is not to avoid ambition, but to discipline it.  

Success requires vision tempered with pragmatism, transparency, and respect for both people and the planet.  

When these principles guide planning and execution, mega projects can truly transform societies, therefore leaving legacies of progress rather than monuments to hubris. 

References

1. Andaman Partners. (2025). China: The High-Speed Rail Superpower. ︎
2. Sandock, S. R. (2008). Digging Deeper. PM Network. ︎
3. Campbell, K.. (2023). ‘Litany of avoidable failures’ in Edinburgh tram project. BBC. ︎
4. Burke, M.. (2025). ‘It stirred the people to breathless wonder and scalding abuse’: The tumultuous history of the Sydney Opera House. BBC. ︎
5. Gulcroft, W.N. (2020), Berlin’s new airport: A story of failure and embarrassment, DW. ︎
6. Wilmsen, B. (2020). After the Deluge: A longitudinal study of resettlement at the Three Gorges Dam. World Development. ︎
7. Ribeiro H.M., Morato J.R. (2020), “Social environmental injustices against indigenous peoples: the Belo Monte dam”. Disaster Prevention and Management: An International Journal. ︎

The post Lessons from Global Mega Projects appeared first on Institute of Project Management.

It is viewed as the “police station”, a place where bureaucracy thrives, where forms must be filled out in triplicate, and where creativity goes to die. PMO leaders tell me they are strategic partners, but when I look at their calendars, they spend 80% of their week chasing updates and only 20% actually using the data. 

They are experts at reporting yesterday’s weather. They can tell you exactly why it rained last Tuesday, but they have no idea if a hurricane is hitting next week. 

This model is broken. It is expensive, it is slow, and in a digital world, it is obsolete. 

We are entering the era of the Algorithmic PMO. This isn’t about buying new software to make inefficient processes faster. It is about a fundamental shift in mindset. We are moving from Descriptive Analytics (reporting history) to Predictive Foresight (changing the future). 

The “Watermelon” Problem 

Most companies are drowning in data but starving for wisdom. You have project schedules, risk logs, budget reports, and thousands of emails. Yet, you rely on a human being to tell you whether a project is on track. 

The problem with humans is that we lie. 

We don’t lie out of malice; we lie out of optimism. Project Managers want to please stakeholders. They mark a project status as “Green” until the very last moment when the deadline looms and it suddenly turns “Red”. 

We call these “Watermelon Projects”: green on the outside but deep red on the inside. 

Artificial Intelligence (AI) doesn’t care about feelings. It doesn’t care about office politics. When you connect Machine Learning to your systems, the Algorithmic PMO stops asking people how they feel and starts looking at the evidence. 

Is the code output slowing down? Has the tone in the team’s Slack channel turned negative? Have similar projects with this vendor historically been late? The algorithm spots the rot inside the watermelon weeks before a human is willing to admit it. 

Three Ways to Stop Being an Administrator and Start Being a Leader 

If you want to move from administrative oversight to strategic leadership, you need to leverage AI in three specific areas. 

1. The Smoke Detector (Predictive Risk) 

Stop treating governance like a toll booth. Traditional governance is static: you reach a milestone, you fill out a form, and you pass the gate. 

AI allows for real-time governance. By analysing past performance, the system can assign a “Confidence Score” to every project in your portfolio. 

Imagine a project manager reports everything is fine, but the algorithm gives the project a 42% confidence score because resource turnover is high. Now you have something real to talk about. You stop asking, “Is the formatting on this report correct?” and you start asking, “Why does the data say we are crashing?” 

That is the difference between a bureaucrat and a strategist. 

2. Stop Playing Tetris with People (Smart Resource Matching) 

Resource management is usually a disaster. It is a game of Tetris played in Excel. We look for the first person with an empty slot and plug them in. 

But availability is not the same as capability. Just because someone is free does not mean they are the right fit. 

AI-driven tools dig deeper. The system might flag that while “Engineer A” is free right now, “Engineer B” has successfully delivered this exact type of task three times before. The data might suggest it is actually smarter to wait a week for the expert than to assign the rookie immediately. 

We need to stop obsessing over “utilisation rates” (keeping people busy) and start obsessing over “throughput” (getting things done). 

3. Institutional Memory on Demand 

The biggest waste of money in project management is the “Lessons Learned” document. 

You know the drill. You finish a project, you hold a meeting, you write down what went wrong, and you file it away in a folder that nobody ever opens again. Two years later, a new team makes the exact same mistakes. 

Generative AI changes this. Instead of searching through dusty digital archives, a Project Manager can simply query the system like a colleague: 

“I’m kicking off a hospital cloud migration. Based on our history, what usually goes wrong?” 

The system synthesises your actual history. It might warn you: 

“In our last three similar projects, data privacy approvals delayed the schedule by an average of four weeks. Plan for that buffer.” 

That is not just data retrieval; that is wisdom on tap. 

The Human Element: Elevate or Evaporate 

There is a fear that AI will replace the Project Manager. 

Let me be clear: if your value to the organisation is updating spreadsheets, chasing timesheets, and taking meeting minutes, then yes, AI will replace you. And it should. The machine does it better, faster, and cheaper. 

But AI is terrible at leadership. It cannot negotiate with a difficult stakeholder. It cannot motivate a burnt-out team. It cannot navigate complex political landscapes. 

As AI takes over the routine work, the role of the PMO professional elevates. We stop being “spreadsheet mechanics” and become Strategic Advisors. 

Instead of spending four hours building a report, you spend four hours debating strategy. 

Instead of chasing updates, you coach teams on how to mitigate the risks the AI identifies. 

The Verdict 

The window for “wait and see” is closing. You cannot manage billion-pound portfolios with gut feelings and static Excel sheets. 

Do not rush out to buy the most expensive AI tool tomorrow. Start by fixing your thinking. Stop acting like a librarian of project artefacts and start acting like a pilot of strategic outcomes. 

The Algorithmic PMO is not about replacing human judgment; it is about scaling it. It allows us to stop staring at the rear-view mirror and finally keep our eyes on the road ahead. 

The post The Algorithmic PMO: Stop Looking in the Rearview Mirror  appeared first on Institute of Project Management.

Scaling Agentic AI is a program challenge as much as an engineering challenge. If your pilots stall in “pilot purgatory”, this article offers a simple operating model project and program leaders can use to align delivery, governance, adoption, and measurable outcomes — so value survives beyond the demo. 

Executive Abstract 

The transition from traditional software to Agentic AI represents a fundamental shift in how enterprises operate. While Generative AI pilots are easy to launch, they are notoriously difficult to scale, often trapping organisations in “Pilot Purgatory.” This article argues that successful Agentic transformation requires more than new tools; it demands a new Operating Model. The Agentic AI Operating Model establishes a dual-engine framework — the REMAP Loop (Technical Strategy) and the ADOPT Loop (Human Capability) — secured by a GRC-Net (Governance) and measured by the ISTA Scorecard. This model empowers Program Managers to evolve from task trackers to architects of a hybrid human-digital workforce. 

I. The Agentic Gap: Why Traditional PM Fails 

For the last decade, Program Management has optimised for the deterministic. In traditional software development, input A always leads to output B. Governance gates are static, and success is measured by “on time, on budget.” 

Agentic AI shatters this paradigm. Agents are probabilistic; they can “reason,” take autonomous actions, and occasionally hallucinate. Managing an Agent is less like managing a software tool and more like managing a junior employee. 

The result is the “Agentic Gap” — the chasm between a successful demo and a production-ready enterprise capability. As reported by The Wall Street Journal, nearly 70% of companies remain stuck in “Pilot Purgatory” because they fail to anticipate the structural and cultural shifts required for scale.¹ To bridge this gap, the Agentic AI Operating Model synchronises technical re-architecture with human adaptation. 

II. The Strategic Engines 

To build enterprise capability, two strategic loops must spin simultaneously: one for technology, and one for people. 

Fig 1. The Agentic AI Operating Model 

A. The Technical Engine: The REMAP Loop 

Legacy infrastructure was built for rigid databases and clear logic paths. Agentic AI, however, requires semantic understanding and flexible data access. To bridge this gap, organisations must move beyond standard cloud migrations to a semantic re-architecture. 

Drawing on established cloud migration planning practices that begin with application dispositioning and target-state decisions,² the REMAP Loop shifts the focus from where systems run to what they mean and enable: 

• R – Review: Audit current data accessibility and API granularity. 

• E – Evaluate: Identify “context gaps” where Agents will fail due to missing information. 

• M – Map: Design the “Agentic Layer”—semantic search, vector databases, and tool definitions. 

• A – Architect: Build the orchestration layer (e.g., LangChain, AutoGen) and memory systems. 

• P – Plan: Define the technical roadmap for “Agent Tooling” rollout. 

B. The Human Engine: The ADOPT Loop 

Table 1. ADKAR vs ADOPT 

For two decades, project leaders have relied on structured change-management approaches to move stakeholders from awareness to sustained adoption; PMI’s change management practice guidance provides a PM-aligned foundation for that work.³ It excels when the goal is compliance—getting a human to use a new software interface. However, Agentic AI is not a software update; it is a workforce update. Employees are not being asked to click buttons; they are being asked to manage “digital interns.” 

This shift requires a new framework. Where ADKAR focuses on usage, the ADOPT Loop focuses on supervision: 

• A – Awareness: Moving beyond “business need” to understanding the specific capabilities and “mental model” of the Agent to prevent misuse. 

• D – Desire: Addressing the “Fear of Replacement” directly. Workplace research shows employees are increasingly using AI at work—most commonly to consolidate information and generate ideas — especially when it reduces low-value, repetitive work rather than replacing core judgement.⁴  

• O – Optimisation: Re-engineering workflows to be AI-first. As Daugherty and Wilson note in human + Machine,⁵ the greatest value often sits in the ‘missing middle’—new processes that blend human judgment with machine speed. 

• P – Proficiency: Shifting training from ‘how to click’ to ‘how to verify.’ Field research from Harvard Business School suggests that without explicit training in supervising and validating AI outputs, knowledge workers can become over-reliant, accepting plausible but incorrect agent results.⁶ 

• T – Transformation: Embedding “Human-in-the-Loop” as a cultural standard rather than a temporary check. 

III. The Control Plane: GRC-Net & S2S 

Innovation cannot scale without safety. However, traditional “gate-based” governance is too slow for the velocity of AI. 

A. The Safety Layer: GRC-Net 

The ecosystem requires evolving from static gates to a dynamic GRC-Net (Governance, Risk, and Compliance Network)—a real-time monitoring layer that sits between the Agent and the Enterprise. 

Drawing on the NIST AI Risk Management Framework (AI RMF 1.0),⁷ the GRC-Net operationalises risk management into the runtime environment: 

• Map (Context): Enforces strict “Context Boundaries,” ensuring that Agents access only data relevant to their role. 

• Measure (Output): Actively scores Agent outputs for toxicity, bias, or hallucination before they reach the user. 

• Manage (Intervention): Provides an automated “Kill Switch” or “Human Handoff” if confidence scores drop below safety thresholds. 

B. The Execution Gate: S2S Protocol 

To avoid “Pilot Purgatory,” the S2S (Safe-to-Scale) Protocol acts as the final validation gate between a controlled pilot and broader production use. The goal is simple: ensure the Agent is not only impressive, but repeatable, governable, and safe under real operating conditions.  

S2S Gate — proceed only if you can answer “Yes” to all eight: 

• Clear Job-to-be-Done: Is the Agent’s scope stated as a single primary job (not a grab-bag of capabilities), with explicit exclusions? 

• Bounded Inputs/Outputs: Are the allowed inputs, expected outputs, and “no-go” outputs defined (including what the Agent must never do)? 

• Safety and Escalation: Is there a defined safety layer and an escalation path for situations that are uncertain, high-impact, or policy-sensitive? 

• Human Accountability: Is there a named owner responsible for outcomes, exceptions, and continuous improvement (not just uptime)? 

• Evidence of Reliability: Has the Agent demonstrated stable performance across representative scenarios, including edge cases and known failure modes? 

• Operational Readiness: Are monitoring, incident response, and rollback/disable procedures defined for the Agent’s workflow? 

• Adoption Readiness: Do users understand when to trust the Agent, when to verify, and when to override—with guidance that fits real workflow constraints? 

• Value Measurement: Is there an agreed set of value signals (time saved, error reduction, cycle-time improvement, risk reduction, user satisfaction) that will be reviewed on a cadence? 

How to use it: Run the S2S gate at each expansion step (pilot → limited rollout → broader rollout). If any answer is “No,” treat it as a design requirement—not a deployment hurdle to be worked around. The purpose of S2S is not bureaucracy; it is protecting delivery predictability as scope, users, and risk grow. 

IV. Measuring Value: The ISTA Scorecard 

Finally, how is success measured? Traditional ROI metrics (like headcount reduction) are often too blunt for Agentic AI, which often improves quality and capacity rather than just cutting costs. 

Table 2. Measuring ROI with the ISTA scorecard 

The ISTA Scorecard offers a solution, inspired by evidence-based software delivery performance research summarised in Accelerate, ⁸but adapted for AI velocity: 

• I – Impact: The tangible business value (e.g., hours returned to the business, revenue lift, or customer experience score). 

• S – Speed: The velocity of task completion. How much faster is the Human + Agent team compared to the human alone? 

• T – Tech-fit: Architectural health. Is the Agent reusing enterprise knowledge assets (reducing technical debt), or creating new data silos? 

• A – Alignment: Strategic adherence. Is the Agent working on high-value strategic tasks, or merely automating low-value noise? 

V. Conclusion: The New Capability 

The era of Agentic AI offers unprecedented opportunity, but it demands a sophisticated approach to execution. By implementing the REMAP and ADOPT loops, securing them with GRC-Net, and measuring them via ISTA, Program Managers can move beyond the “cool demo” phase. 

The role of the Program Manager is evolving. They are no longer just tracking tasks; they are the Chief Orchestrators of a new, hybrid workforce. 

References

1. The Wall Street Journal. (2024). Companies Had Fun Experimenting With AI. Now They Have to Show the Returns.  ︎
2. National Institute of Standards and Technology. (2012). SP 800-146: Cloud Computing Synopsis and Recommendations.  ︎
3. Project Management Institute. (2013). Managing Change in Organisations: A Practice Guide.  ︎
4. Gallup. (2025, December 14). AI Use at Work Rises.  ︎
5. Daugherty, P. R., & Wilson, H. J. (2018). Human + Machine: Reimagining Work in the Age of AI. Harvard Business Review Press.  ︎
6. Dell’Acqua, F., et al. (2023). Navigating the Jagged Technological Frontier: Field Experimental Evidence of the Effects of AI on Knowledge Worker Productivity and Quality. HBS Working Paper. ︎
7. National Institute of Standards and Technology. (2023). Artificial Intelligence Risk Management Framework (AI RMF 1.0).  ︎
8. Forsgren, N., Humble, J., & Kim, G. (2018). Accelerate: The Science of Lean Software and DevOps: Building and Scaling High-Performing Technology Organisations. IT Revolution Press ︎

The post The Agentic AI Enterprise Transformation Playbook  appeared first on Institute of Project Management.

This case study explores a two-year experimental initiative in which ChatGPT, a large language model developed by OpenAI, was positioned as an entirely autonomous project manager (PM) within a mid-sized software development firm. The core objective was to evaluate the sustainability of AI assuming traditional human project management responsibilities, including task delegation, stakeholder communication, risk mitigation, and timeline management. Over a period of twenty months, the AI managed six cross-functional projects of varying complexity. 

The article discusses the methodology, observed outcomes, success metrics, challenges, and implications of AI-driven project management. Findings suggest that while ChatGPT demonstrated competence in coordination and administrative functions, significant limitations remain in areas requiring emotional intelligence, adaptive leadership, and ethical judgement. 

1. Introduction 

Project management (PM) has traditionally been a human-centred discipline, balancing technical organisation with soft skills such as empathy, strategic vision, and negotiation. With the rapid advancement of artificial intelligence—particularly generative models such as ChatGPT—organisations are increasingly exploring the automation of roles once believed to require human intuition. 

A mid-sized software organisation based in Europe initiated an internal experiment to examine whether ChatGPT, integrated with productivity and communication tools, could function as a fully autonomous project manager. Over a two-year period, ChatGPT was embedded in six software development projects, ranging from internal tools to customer-facing platforms. This paper documents the experimental design, execution, and findings, contributing to the ongoing debate surrounding the role of AI in complex human workflows. 

2. Background and Related Work 

Project management encompasses planning, execution, team collaboration, and stakeholder engagement. The PMBOK Guide highlights essential project manager competencies across domains such as scope, time, quality, human resources, stakeholder management, risk, procurement, cost, integration, and communication. ¹

Recent studies highlight the growing presence of AI in project management functions. Machine learning-powered tools are widely used for risk prediction, schedule optimisation, and sentiment analysis. However, the concept of AI serving as a sole project manager remains largely theoretical. 

ChatGPT’s capabilities in natural language generation, decision support, and contextual understanding provide a foundation for experimentation with autonomous PM functionality. Nevertheless, previous research cautions against overestimating AI’s capacity to manage creativity, emotional intelligence, and ambiguity within team dynamics. 

3. Methodology 

3.1 Project Setup 

Six projects were selected across different departments, including a customer relationship management (CRM) tool, a mobile application for remote workers, a data visualisation dashboard, a cybersecurity upgrade, a SaaS onboarding automation module, and an internal HR portal. ² 

Each project involved a core team of developers, quality assurance personnel, and designers, with no human project manager assigned. ChatGPT, integrated via API with Jira, Google Workspace, Trello, and Slack, was responsible for full project management duties. 

3.2 Configuration of ChatGPT 

The AI was customised with domain-specific context and trained on internal project management guidelines. ³ Through prompt engineering, ChatGPT was instructed to create Gantt charts and timelines, assign and track tasks, moderate stand-up meetings via Slack, escalate blockers and scope creep, and communicate with stakeholders through drafted emails. 

3.3 Evaluation Criteria 

Project performance was evaluated using the following metrics: 

• Budget adherence 
• Timely delivery 
• Communication efficiency 
• Stakeholder satisfaction 

4. Results and Findings 

4.1 Strengths of AI Project Management 

ChatGPT effectively managed task delegation and tracking through Trello and Jira integrations. Deadlines were largely met, and workflow consistency was maintained. Additionally, the AI’s 24-hour responsiveness proved advantageous for distributed teams operating across different time zones. 

4.2 Challenges and Limitations 

In certain instances, ChatGPT misinterpreted ambiguous or domain-specific requests, resulting in misprioritised tasks or scheduling errors. These limitations highlighted the AI’s difficulty in handling unclear instructions and contextual nuance without human oversight. 

5. Discussion 

The experiment revealed that ChatGPT can successfully handle many transactional and administrative project management tasks with high accuracy and speed. When integrated with collaboration tools, it can maintain project momentum, provide timely updates, and reduce the cognitive load on technical team members. 

However, human project managers serve as mediators, visionaries, and motivators—roles that ChatGPT, despite its linguistic sophistication, cannot independently fulfil. The AI lacks the intuition required to navigate complex, unstructured ambiguity and interpersonal dynamics commonly encountered in real-world projects. 

6. Conclusion 

The two-year experiment demonstrates that ChatGPT, when properly configured and monitored, can autonomously perform several core project management functions. It excels in structured environments where consistency, timeliness, and clarity are paramount. 

The future of project management lies in hybrid models, where AI handles routine and scheduled PM functions while human leaders focus on strategic direction, high-stakes decision-making, and organisational culture. As AI models continue to evolve—particularly in contextual reasoning and emotional recognition—their role in project management may expand; however, collaboration with human judgement will remain essential. 

References 

1. Jariwala, M. (2024). Incorporating artificial intelligence into PMBOK 7th edition frameworks: A domain-specific investigation for optimising project management performance domains. International Journal of Trend in Scientific Research and Development.  ︎
2. Stefanov, T., Varbanova, S., Stefanova, M., & Ivanov, I. (2023). CRM systems as a necessary tool for managing commercial and production processes. TEM Journal.   ︎
3. Islam, M. R., Ahmed, M. U., Barua, S., & Begum, S. (2022). A systematic review of explainable artificial intelligence in terms of different application domains and tasks. Applied Sciences.   ︎

The post AI as a Project Manager: Can ChatGPT Replace Human PMs? A 2-Year Experiment  appeared first on Institute of Project Management.

This article argues that the Manifesto articulates an organisational state of being rather than a prescribed methodology. It demonstrates why no framework implemented dogmatically produces genuine agility. The prevailing approach to “agile transformation” mirrors the waterfall methodology it seeks to replace, explaining why 47% of transformations fail despite widespread adoptions¹. 

The Misunderstanding That Undermines Transformation

Organisations consistently misinterpret the foundational nature of the Agile Manifesto. While the document describes observable patterns in successful software development, companies implement it as prescriptive instructions ². 

The four values and twelve principles characterise what agility looks like when achieved. They don’t prescribe how to achieve it³. 

The process isn’t semantic wordplay. The distinction fundamentally shapes transformation outcomes. 

Teams that pursue agility as a state develop adaptive capabilities. Teams that follow “agile processes” create cargo cult implementations: superficial adoption of ceremonies without cultivating the underlying mindset⁴. 

The statistics reveal the cost of this misunderstanding: 

• 86% of software teams claim agile adoption⁵ 

• Only 42% report improved software quality⁶ 

• 31% admit to incomplete implementation⁷ 

Organisations mistake compliance with framework rules for achievement of agile capabilities. 

“Control without competence is chaos.” – L. David Marquet 

How Dogmatism Contradicts Core Values 

Rigid adherence to agile frameworks violates the first Manifesto value: individuals and interactions over processes and tools⁸ . 

When organisations mandate strict compliance with Scrum ceremonies, Kanban rules, or SAFe prescriptions regardless of team context, they prioritise process over people—the antithesis of agile thinking⁹. 

Consider Spotify’s widely imitated “Squad Model.” The framework achieved mythical status despite never being fully implemented at Spotify itself. 

As former Spotify employee Jeremiah Lee documented, “Even at the time we wrote it, we weren’t doing it. It was part ambition, part approximation”¹⁰. 

The model failed because it¹¹: 

• Assumed collaborative competencies that teams lacked 

• Created matrix management confusion 

• Optimised for autonomy at the expense of alignment 

Organisations copied Spotify’s structure without understanding its context, creating what agile coaches term “agile dogma”¹². 

Teams conducted stand-ups without real autonomy. They ran sprints while maintaining waterfall planning cycles. They implemented retrospectives without empowering people to act on insights¹³ . 

This pattern repeats across industries. The Scaled Agile Framework (SAFe), used by 37% of organisations¹⁴, often becomes a bureaucratic overlay rather than an agility enabler when implemented dogmatically. 

Teams follow prescribed roles, ceremonies, and artefacts, yet lack the adaptive capability that constitutes genuine agility. 

The Waterfall Transformation Paradox 

Perhaps the greatest irony in contemporary organisational practice: applying waterfall methodologies to agile transformation itself. 

Companies planning comprehensive “big bang” implementations¹⁵ create detailed roadmaps, establish fixed timelines, and treat transformation as a project with defined deliverables¹⁶. 

This approach contradicts agile principles at every level: 

Predictive Planning: Assumes organisational needs can be determined upfront 

Linear Progression: Follows sequential phases rather than iterative cycles 

Top-Down Imposition: Mandates change rather than enabling emergence 

Fixed Scope: Defines success metrics without continuous adaptation 

Research validates the consequences. Organisations attempting big-bang transformations report 40-60% higher failure rates than incremental approaches¹⁷ . 

When waterfall leadership drives agile adoption, failure rates approach 95%¹⁸. These leaders optimise for control and predictability—the opposite mindset required for agility. 

ING Bank’s successful transformation demonstrates the alternative. Rather than implementing frameworks across the organisation simultaneously, ING created 350 cross-functional squads over six months, allowing organic adaptation to context¹⁹ 

The results²⁰ 

• Product development cycles decreased from 18 months to 3-6 months 

• Mobile app satisfaction increased 20% 

The key: treating transformation as capability development, not process installation. 

Systems Thinking Reveals the Path Forward 

Systems theory illuminates why dogmatic implementation fails and prescribes the alternative. 

Organisations are complex adaptive systems. Outcomes emerge from interactions, feedback loops, and nonlinear dynamics²¹. Imposing linear frameworks on nonlinear realities creates dysfunction. 

Game Theory and Misaligned Incentives 

Game theory explains why misaligned incentives produce defensive structures. When teams lack shared visibility into system state, each function creates friction to avoid blame. 

Gates, approvals, and review boards proliferate not to manage risk but to distribute accountability²². Automation and transparency reshape this dynamic by creating shared truth and aligned incentives. 

Agency Theory and the Trust Gap 

Agency theory highlights the trust gap between leadership and delivery teams. This gap fuels status meetings, manual documentation, and process overhead: costly workarounds for a transparency deficit²³. 

Systems-based approaches replace episodic oversight with continuous observability. Trust is earned through demonstrated capability rather than imposed authority. 

Modern Compliance Validates the Approach 

Modern compliance practices exemplify this transformation. Organisations like Capital One reduced lead times 40-60% while improving audit outcomes by automating compliance into delivery pipelines rather than adding manual gates²⁴ 

The FDA now accepts automated validation reports for medical devices, citing improved reliability and traceability over manual processes. 

Compliance becomes a byproduct of delivery, not an afterthought. 

From Compliance to Capability

Organisations seeking genuine agility must abandon framework dogmatism and waterfall transformation approaches. The alternative requires fundamental shifts in thinking and practice: 

Start with Principles, Not Practices 

Focus on developing adaptive capabilities rather than implementing prescribed ceremonies. Teams need collaboration skills, technical practices, and feedback mechanisms. Not mandated meeting cadences. 

Apply Agile to Transformation Itself 

Begin with small experiments. Measure outcomes. Adapt based on learning. 

Treat transformation as continuous capability development rather than discrete project delivery. 

Optimise for Learning Over Control 

Create feedback loops at every level: team retrospectives, customer validation, strategic reviews. Empower teams to act on insights rather than merely collecting them. 

Build Systems That Enable Agility 

Invest in automation, observability, and tooling that supports rapid experimentation and deployment. Make agile practices easier than waterfall alternatives. 

The Opportunity 

The opportunity isn’t just to implement agile frameworks faster. It’s to cultivate organisational capabilities that transcend any single methodology. 

Companies achieving this transformation report 237% improvement in commercial performance when agility becomes a cultural capability rather than process compliance²⁵. 

As the FINRA 2024 Automation Guidelines note, “Controls should be as dynamic as the risks they mitigate”²⁶. 

Organisations embracing this principle treat agility as an emergent capability rather than a prescribed process. They consistently outperform those pursuing compliance with the framework. 

The Manifesto points toward a destination. The journey requires continuous adaptation, not rigid adherence to any single map. 

Organisations ready to move beyond framework dogma can begin with incremental experiments that build adaptive capability. The path to agility starts with treating the transformation itself as an agile endeavour: iterative, responsive, and continuously learning. 

REFERENCES 

1. Scrum Inc. (2021). Why do 47% of Agile Transformations Fail? ︎
2. Radix Web (2024). 42+ Most Important Agile Statistics for 2024. ︎
3. Agile Alliance (2025). 12 Principles Behind the Agile Manifesto.   ︎
4. Andy Burns (2024). Welcome to the Agile Cargo Cult. LinkedIn  ︎
5. eSpark Info (2025). Dive into 60+ Agile Statistics for 2025. ︎
6. Ibid ︎
7. Ibid ︎
8. Growing Agile Coaches (2025). Avoiding Agile Dogmatism: Balance Framework.   ︎
9. Scrum.org (2024). Ghosts of Agile Past: Dogma!   ︎
10. Jeremiah Lee (2020). Spotify’s Failed #SquadGoals. jeremiahlee.com  ︎
11. Agility11 (2020). Spotify Doesn’t Use the Spotify Model. ︎
12. Growing Scrum Masters (2025). Breaking Free From Agile Dogma and Rigid Practices.  ︎
13. Tomas Kejzlar (2017). Are you in a Cargo Cult? Skeptical Agile  ︎
14. eSpark Info (2025).  ︎
15. LitheSpeed (2025). Make your ‘Big Bang’ Agile Transformation ‘Agile’. ︎
16. The Value Hub (2023). Big bang Agile Transformation: too radical or good to go?   ︎
17. Miro (2025). Almost half of all Agile transformations fail.   ︎
18. Scrum Inc. (2021).  ︎
19. McKinsey & Company (2017). ING’s agile transformation. ︎
20. Agile Federation (2025). Transforming Banking: How ING’s Agile Revolution Redefined Success.   ︎
21. Managed Agile (2021). What is Systems Thinking and Why is it Important?   ︎
22. Martin Fowler (2006). Agile Imposition. martinfowler.com ︎
23. lbid ︎
24. Radix Web (2024). ︎
25. eSpark Info (2025).  ︎
26. FINRA (2024). 2024 Annual Regulatory Oversight Report.   ︎

The post Beyond Framework Dogma: Why the Agile Manifesto Describes a State, not a Process  appeared first on Institute of Project Management.