Enhancing PDCA for Continuous Improvement

The Plan-Do-Check-Act (PDCA) cycle serves as a foundational framework for structured, data-driven continuous improvement. However, to maximize its impact, integrate complementary methodologies at each stage of the cycle. This article explores how you can enhance PDCA with Root Cause Analysis, Agile Execution, Visual Management, Standard Work, and Kaizen Events, all supported by Gemba Walks to ensure alignment with operational realities.


Plan: Identifying and Addressing the Right Causes

Many improvement initiatives fail not because of poor execution, but because they target symptoms rather than root causes. The Plan phase is critical in ensuring that the right problems are being addressed.

  • Utilize Root Cause Analysis techniques like the 5 Whys and Fishbone Diagrams to uncover the fundamental issues rather than applying quick fixes.
  • Involve cross-functional teams in problem identification to ensure diverse perspectives and deeper insights.
  • Clearly define success criteria and key performance indicators (KPIs) to measure the impact of changes.

Personal Experience: In the adoption of a new digital tool, a constant flow of tickets were raised for additional reports. The root cause was not that reports were missing, but people did not trust the data and tried to get reports to show this. Creating more reports is therefor not the solution, building trust in the data is.


Do: Implementing Fast, Iterative Improvements Using Agile

Traditional improvement initiatives often fail due to long implementation cycles that do not adapt to emerging insights. In the Do phase, an Agile approach enables teams to execute improvements iteratively, ensuring quick learning and adaptation.

  • Break down solutions into small, incremental changes rather than large-scale, disruptive overhauls.
  • Use short sprints to test hypotheses, gather feedback, and refine the approach dynamically.
  • Foster a culture of empowerment by enabling frontline employees to take ownership of improvements within their domain.

Personal Experience: Especially shortly after Go Live, people experience all kinds of issues in working with the new system. Logging the issues for the next big release might be tempting from a program perspective, but you lose both the momentum in adopting the solution as well as the business/process performance will lag behind.


Check: Leveraging Daily and Visual Management

Without structured reflection and analysis, even well-intentioned improvement efforts risk failure. The Check phase ensures that the changes implemented are having the desired effect and allows for course corrections.

  • Implement Daily Management Routines, such as stand-up meetings, to assess progress and identify real-time roadblocks.
  • Utilize Visual Management Tools like performance dashboards and Kanban boards to provide clear visibility into key metrics.
  • Conduct regular reviews to assess whether improvements align with strategic objectives.

Personal Experience: Daily management in combination with clear, trustworthy dashboards is one of the most impactful concepts to drive the adoption, performance, and engagement of the teams. It fosters fast feedback and helps to accelerate the PDCA cycle.


Act: Standardizing or Pivoting Based on Results

The final phase of the PDCA cycle ensures that improvements either become standard practice or trigger deeper exploration through structured problem-solving.

  • If the improvement proves effective, incorporate it into Standard Work to sustain the gains.
  • If the problem persists, go deeper by organizing Kaizen Events—intensive, collaborative workshops aimed at breakthrough improvements.
  • Ensure knowledge sharing so that lessons learned from one cycle inform future improvements across the organization.

Personal Experience: Evaluating what works and does not work can be done in different ways, but the important thing is that action is taken—to either sustain and spread the working solution or pivot. When the improvement did not work, it likely requires more analysis and review, and the Kaizen approach can really help here.


The Role of Gemba Walks: Ensuring Alignment with Reality

Supporting this entire PDCA cycle is the practice of Gemba Walks, where leaders go to the actual workplace (Gemba) to observe, engage with employees, and understand challenges firsthand. This prevents a disconnect between strategy and execution, ensuring that improvement efforts are grounded in operational realities.

  • Ask open-ended questions to frontline employees to uncover hidden inefficiencies.
  • Reinforce a culture where continuous improvement is not top-down but co-created with those closest to the work.
  • Identify systemic barriers that require leadership intervention to remove.

Personal Experience: By going to the Gemba, leaders both get a better understanding of what is really happening and show commitment to their teams in leading the transition.


Conclusion: Continuous Improvement as a Leadership Imperative

PDCA, when enhanced with Root Cause Analysis, Agile Execution, Visual Management, Standard Work, Kaizen Events, and Gemba Walks, becomes a powerful engine for continuous improvement. Transformation leaders must champion this approach, ensuring that improvement is not a one-time initiative but a deeply embedded organizational capability.

Which Project Management Methodology to Use: Waterfall, Agile, or Both?

1. Introduction

In an era of rapid technological change and market disruptions, organizations must execute projects with both precision and adaptability. Digital transformation initiatives, IT modernizations, and enterprise-wide projects require structured governance to ensure alignment with business goals while maintaining agility to respond to evolving needs. However, choosing between Traditional Waterfall (PMBOK) and Agile (Scrum/SAFe) is not always straightforward.

While Waterfall offers predictability, governance, and risk control, Agile provides speed, flexibility, and iterative value delivery. The reality is that many organizations do not need to choose one over the other but rather combine them strategically. This article explores the strengths and weaknesses of both methodologies, when to apply each, and how a hybrid approach can leverage the best of both worlds.

2. Why You Need a Strong Project Management Setup

Project failure rates remain alarmingly high, with studies indicating that up to 70% of digital transformation initiatives fail due to poor execution, misaligned priorities, and resistance to change. A well-structured Project Management (PM) framework is essential to prevent these failures, ensuring that projects are not only delivered on time and within budget but also drive real business value.

At the core of any successful transformation is clear ownership, structured governance, and a balance between control and agility. Large-scale projects often face a paradox—executives and stakeholders demand predictability and structured planning, while operational teams require flexibility to iterate and adapt. Without the right project management setup, organizations risk falling into two extremes: either too rigid, leading to slow execution and missed opportunities, or too unstructured, resulting in chaotic implementations and wasted resources.

Finding the right project management approach is about more than just process—it’s about aligning methodologies with the business context, organizational culture, and project complexity. For some initiatives, a Traditional Waterfall (PMBOK) approach provides the necessary structure and risk mitigation, while for others, Agile (Scrum & SAFe) offers the speed and adaptability required in fast-moving environments. In many cases, a hybrid model that blends both methodologies delivers the optimal balance.

3. Choosing the Right Approach: Traditional Waterfall (PMBOK) vs. Agile (Scrum, SAFe)

A. The Case for Traditional Waterfall (PMBOK)

Some projects demand a highly structured approach with well-defined requirements, strict regulatory compliance, and minimal scope for change. This is where Waterfall methodologies, based on PMI’s PMBOK framework, excel. Waterfall is most effective in industries where predictability, formal approvals, and rigorous documentation are essential, such as large IT infrastructure deployments, ERP implementations, regulatory projects, and government initiatives.

Waterfall project management operates in a linear, sequential process, with clear stages: Initiation, Planning, Execution, Monitoring & Controlling, and Closing. This structure ensures that risk is carefully managed upfront, scope creep is minimized, and accountability is enforced at every stage. Executives often favor Waterfall because it provides detailed planning, resource forecasting, and cost predictability, making it easier to report progress to stakeholders and investors. However, its rigidity can become a drawback in environments where requirements frequently change or when teams need faster iterations.

B. The Case for Agile (Scrum & SAFe)

Unlike Waterfall, Agile methodologies like Scrum and SAFe are designed for projects with evolving requirements, high collaboration needs, and rapid innovation cycles. Agile breaks work into short, iterative cycles (Sprints) where teams continuously deliver value, receive feedback, and adapt.

Agile thrives in environments where customer needs shift rapidly—such as software development, digital product innovation, and emerging technologies. Teams operate in cross-functional units, fostering collaboration between developers, designers, business leaders, and end-users. The key advantage of Agile is its ability to respond to change quickly, ensuring that projects deliver what users actually need, rather than what was initially planned months ago.

For enterprises managing multiple Agile teams, SAFe (Scaled Agile Framework) provides a structured way to scale Agile across large organizations, ensuring alignment across teams while maintaining flexibility at the execution level.

4. Why Not Both? Leveraging a Hybrid Approach

Many organizations struggle with a pure Waterfall or Agile approach because no single methodology fits every project. The solution? A hybrid model that blends both methodologies strategically. This allows businesses to maintain the structured governance of Waterfall while embedding Agile’s flexibility where it matters most.

A. When to Combine Waterfall & Agile

  1. Enterprise Digital Transformation – Waterfall for strategic planning, Agile for implementation.
  2. IT Modernization – Waterfall for infrastructure, Agile for application development.
  3. Mergers & Acquisitions – Waterfall for integration planning, Agile for transition teams.
  4. Regulated Industries – Waterfall for compliance, Agile for innovation efforts.

B. Structuring a Hybrid Approach

AspectTraditional Waterfall (PMBOK)Agile (Scrum/SAFe)
PlanningLong-term roadmap & milestonesIterative backlog prioritization
ExecutionSequential phases (Design → Build → Test)Continuous delivery in sprints
GovernanceStrong documentation & risk controlAgile leadership & adaptive governance
MeasurementScope, cost, time adherenceValue delivery, customer feedback

By combining Waterfall’s governance with Agile’s iterative execution, organizations can reduce risk, optimize delivery speed, and improve project outcomes.

5. Key Takeaways for Executives

  • No single methodology is universally best—Waterfall excels in structured, risk-heavy environments, while Agile thrives in fast-changing ones.
  • For predictable, well-defined projects, PMBOK (Waterfall) ensures control.
  • For innovation-driven or fast-moving projects, Scrum/SAFe enable adaptability.
  • Hybrid models offer the best of both worlds, integrating structure with agility.
  • Project governance should be tailored to business needs rather than rigidly following a single methodology.

By adopting a balanced approach, organizations can drive digital transformation efficiently while mitigating risks.