Change is a natural part of any organization. People move on, technology advances, and new challenges arise. At the same time, markets shift, customer expectations evolve, and competition increases. If your organization isn't delivering the results you expect, it might be time to rethink your approach.
Agile Frameworks as a Starting Point
Agile frameworks offer a way to navigate these challenges. They provide ideas and solutions that can help teams work more effectively. But the real question is: Is your framework evolving with your organization, or is it holding you back?
There are two types of frameworks:
- Generative frameworks grow with your organization, continuously adapting to new challenges.
- Rigid frameworks impose solutions without considering the specific context.
Even the most detailed framework can become obsolete if it doesn’t evolve alongside your organization’s needs.
Patterns Over Prescriptions
Rather than enforcing a fixed set of rules, effective Agile frameworks offer patterns—flexible building blocks that help teams address challenges in their own way. These patterns provide guidance, but they don’t dictate a single “correct” approach. This is why I appreciate A Scrum Book (which I co-authored). It presents patterns—not rigid processes—that teams can apply based on their specific challenges.
Take the Daily Scrum, for example. Do you need it? That depends. If you don’t have the problem that a Daily Scrum is meant to solve, then forcing it doesn’t make sense. Agile is about thinking critically, not following rules blindly. (Yes, as a PST I should not be be saying this, but it is true none the less ;) )
This mindset brings us to a bigger question—not just about specific team practices, but about how we think about the organization design as a whole.
More Examples of generative approaches
- Creating Agile Organizations (CAO): This approach provides org design principles, guides and axioms for agile org design to evolve your framework.
- Lean Thinking: Focuses on continuous improvement rather than a fixed set of rules.
From Adoption to Evolution
The message today is simple: Frameworks often fail because they don’t align with your organization’s specific needs. The failure is in the customization part.
Instead of asking:
"How can I adopt Framework X?"
A better question is:
"How can I evolve my framework to meet my organization’s changing needs?"
Which leads us to another question: How do you create a framework that truly fits your organization?
The Creating Agile Organizations Approach
Rather than prescribing a one-size-fits-all solution, the Creating Agile Organizations approach focuses on designing an Agile framework that fits your organization’s unique context.
Key Elements of This Approach
- Axioms Organization Design core truths that guide your decisions.
- Principles High-level guidelines for decision-making.
- Design Guidelines Science backed practical recommendations to make informed organizations design decisions.
Context First, Framework Second
Avoid applying any rigid Agile framework. Instead, take a step back and first understand your organizational context—your challenges, team dynamics, and goals. Only then should you apply principles and guidelines to build a framework that truly supports your needs.
By accepting that your Agile framework as something evolutionary, rather than something fixed, you keep it effective and relevant in a changing world.
Key Takeaways
A strong Agile framework isn’t about following rules—it’s about continuously adapting to your organization’s unique and changing needs.
- Assess Your Current Framework – Identify what’s working and what’s not.
- Understand Your Context – Look at your organization design(process, structure, rewards, people), market, and challenges.
- Define Your Desired Capabilities – What capabilities do you need to solve your problems and keep competitive?
- Apply Relevant Patterns and Guidelines – Use guides, axioms, and principles from Creating Agile Organizationsand A Scrum Book to shape your framework and develop the desired capabilities.
- Experiment and Iterate – Make small changes, measure their impact, and adjust as needed.
- Keep Evolving – As things keep changing, reassess desired capabilities and redesign accordingly.
By following these steps, you ensure that your Agile framework remains dynamic, relevant, and in sync with your organization’s needs.