Agile change management is a values-driven approach to organizational change rooted in the principles of the Agile Manifesto. It prioritizes co-creation, short feedback loops, and adaptive action over rigid plans, top-down directives, and compliance-based adoption models.
The term agile change management is widely used but rarely defined from first principles. Most interpretations treat it as a faster, more flexible version of traditional change management — applying agile methods (sprints, backlogs, retrospectives) to change programs.
That misses the point. The Agile Manifesto was not a process guide. It was a set of values and principles that guided how teams approached work. Agile change management applies those same values and principles to how organizations navigate change — not to make change management faster, but to make it more human, adaptive, and effective.
The framework on this site is drawn from Change Agility by Jason Little. It presents four values and twelve principles adapted from the Agile Manifesto specifically for change practitioners working inside and outside of software organizations.
Adapted from the Agile Manifesto, these four values guide how change agents think and act. As with the original manifesto: both sides have value — the left side is valued more.
Change affects people first. Before designing a process or selecting a tool, understand who is affected, how they interact, and what they need. When in doubt, get people together instead of creating another framework.
The equivalent of "working software" in change is a solution that actually solves the problem people are experiencing — not a plan, deck, or report that describes what a solution might look like. Show something real sooner.
Change is more likely to take hold when the people affected help shape it. Co-creation replaces the buy-in model — where change is designed by a few and sold to many — with a model where all parties build a shared understanding together.
Organizations are not machines. They are complex, adaptive systems. Plans are useful starting points, but the ability to respond to what is actually happening — rather than what was predicted — is the real capability change agents need to develop.
The four values are the foundation. The twelve principles are where practice is built. These principles guide how change agents translate values into decisions and actions in their specific context.
Change is a human experience. The people affected by change — not the stakeholders managing it — are the primary focus of every decision.
Even late in the process, changing direction is a signal of learning, not failure. Agile change agents treat a change to the plan as useful information, not a threat.
Frequent, small cycles of action and reflection surface problems earlier and reduce the cost of course correction. Long planning cycles defer learning to the worst possible moment.
Change rarely belongs to one team or department. Cross-functional collaboration reduces handoffs, surfaces competing priorities early, and creates shared ownership of outcomes.
People move toward change when they can connect it to something meaningful to them. Compliance-based approaches create the appearance of adoption without the substance of it.
Human-to-human interaction is the highest-bandwidth channel available to change agents. Technology supports; it does not replace the quality of direct conversation and in-person facilitation.
Measuring what is easy to measure is not the same as measuring what matters. Effective change metrics evolve as understanding of the change context deepens.
Organizations have a natural pace of change. Forcing change faster than the system can absorb it creates resistance, burnout, and surface-level compliance.
No single change methodology works in every context. An adaptable process is one that is deliberately shaped to fit the organization, the change, and the people involved.
The most effective approaches are often the simplest. Complexity in a change process is often a sign that the real problem has not been clearly understood.
When people help design the change they are being asked to adopt, resistance decreases and ownership increases. Co-authorship of the change is one of the most reliable levers available.
Regular retrospection — examining what is working, what is not, and why — is the engine of improvement. Without it, change processes calcify into routines that no longer serve their original purpose.
The Lean Change OS provides 136 Elements of Change — practical tools, models, and practices that express these values and principles in real change work. These six elements are core to an agile change approach.
A mental model for managing change work at three horizons — strategic direction (BIG), near-term priorities (NEXT), and immediate actions in progress (NOW). Replaces the Gantt chart with a living, pull-based view of change.
Explore this element →A pull-based change process that focuses effort on the NOW view. Work is pulled into action based on readiness and capacity — not pushed through a pre-set schedule. Reflects the agile principle of adapting to the pace of the system.
Explore this element →A physical or digital workspace that makes all change work visible to everyone involved. Supports cross-functional collaboration by giving teams a shared, real-time view of what is happening, what is next, and where blockers exist.
Explore this element →Visual canvases that serve as placeholders for structured conversations — not templates to fill in. Change Canvases help teams build shared understanding of the strategic context, team-level change, and individual impact.
Explore this element →The practice of running small, deliberate experiments to test assumptions about how change will land. Each experiment generates feedback that informs the next step — making the change process empirical rather than prescriptive.
Explore this element →Using feedback from real experiments — not surveys sent after the change is complete — as the primary input into how change plans evolve. Feedback is not validation; it is the mechanism by which the approach adapts.
Explore this element →Questions change practitioners commonly ask about agile change management.
Agile change management is a values-driven approach to organizational change that applies the core ideas of the Agile Manifesto to change practice. Rather than prescribing a fixed process, it focuses on four values — individuals and interactions, working solutions, co-creation, and responding to change — and 12 principles derived from those values. It was developed to help change agents build context-specific approaches rather than follow someone else's method.
The four values, adapted from the Agile Manifesto for a change context, are: (1) Individuals and interactions over processes and tools, (2) Working solutions over comprehensive documentation, (3) Co-creation over contract negotiation, and (4) Responding to change over following a plan. Both sides have value — the left side is valued more.
The 12 principles are: (1) Mind the People, (2) Welcome Change, (3) Short Feedback Loops, (4) Cross-Functional Collaboration, (5) Intrinsic Motivation, (6) Touch over Technology, (7) Adaptable Metrics, (8) Adapting to the Pace, (9) Adaptable Change Process, (10) Keep it Simple, (11) The People Who Write the Plan Don't Fight the Plan, and (12) Inspect and Adapt.
Traditional change management tends to create plans in isolation, assess readiness at scale, and execute those plans on a timeline. Agile change management co-creates the approach with those affected, runs short experiments, and adapts based on real feedback. The key difference is that agile change management treats change as an ongoing, iterative process rather than a project with a defined end state.
Lean Change Management is a specific methodology developed by Jason Little that provides a practical framework — the Insights-Options-Experiments cycle — for applying agile change principles. Agile change management is the broader philosophy rooted in the four values and 12 principles. Lean Change Management is how you put those values and principles into practice in a real organizational context.
No. While the Agile Manifesto originated in software development, the values and principles it contains are context-independent. The Change Agility framework explicitly adapts these ideas for any type of organizational change — marketing teams, HR transformations, operational restructuring, and enterprise-scale initiatives. The principles are universally applicable when interpreted for the specific context at hand.
Go deeper on the values, principles, and practice of agile change management with self-paced courses from Jason Little.
Explore the 4 values, 12 principles, and practical tools for applying agile thinking to organizational change. Includes exercises to build your own change manifesto.
View on UdemyThe practitioner-level course covering the full Lean Change methodology — Insights, Options, Experiments — alongside the elements and canvases used in real change work.
Explore the Course