Capability-Driven Transformation Framework (Preview)
I’ve been developing an approach to transformation that I haven’t formally documented until now. What follows is an early working version, intentionally high level, that will be refined and continue to evolve over the next few months. It will also be supported by additional articles that explore different aspects in more detail.
Over the past decade, across different organizations and transformations, I’ve applied a consistent way of thinking about change. It isn’t centered on a set of activities, and it doesn’t treat change as a linear process. Instead, it focuses on the conditions that need to exist for change to actually take hold.
This reflects patterns I’ve seen consistently across transformations, regardless of industry, function, or scale. I’m now codifying that into what I’m calling the Capability-Driven Transformation Framework. What you’re seeing here is an early preview.
A Systemic Perspective on Change
This approach is systemic, not systematic.
It looks at change through multiple perspectives, starting at the enterprise level, moving through business functions, into teams, and down to individuals. Each layer operates within the same system, but interprets and applies change differently. That variation isn’t noise, it’s one of the primary reasons execution begins to diverge.
Most approaches assume these layers respond uniformly. In practice, they don’t.
Not Another Step-by-Step Formula
Unlike some of what’s out there, this does not present itself as a magic elixir that will solve every change challenge through a step-by-step formula.
It’s a way to understand how change actually moves through an organization, where it tends to break down, and what conditions need to be in place for it to hold.
A methodology is not a one-size-fits-all solution, and it shouldn’t be imposed at the onset. Selecting, adapting, or crafting a methodology should be based on how the change is being understood and what problem is actually being addressed. Imposing one upfront is similar to going to a surgeon and telling them what procedure to perform and how to perform it without a proper diagnosis. The procedure might be valid, but without understanding the underlying condition, there’s no reason to expect it to lead to the right outcome.
When someone only has a hammer, everything starts to look like a nail. The same applies here. Relying on a single methodology narrows how the problem is approached. Effective change leadership requires a broader toolkit, knowing when to use different approaches and how to combine them based on context.
Grounded in Existing Practice
The framework draws from established multidisciplinary theories, frameworks, models, methodologies, and tools, integrating them into a more coherent way of understanding and enabling transformational change. It draws on multiple disciplines, including behavioral science, organizational theory, learning, systems thinking, and meaning and culture, because transformational change does not operate within a single domain.
Most approaches focus on what to do. Far fewer also focus on the conditions required for it to work. That’s one of the gaps this is designed to address.
Recommended by LinkedIn
Observed Patterns in Transformation
A few ideas sit underneath this, and they show up consistently across transformation efforts.
*As disruption accelerates, particularly with AI, tools like future-oriented competency modeling become increasingly important, and capability forecasting deserves renewed attention.
Core Focus Areas
At its core, this work focuses on alignment, capability, adoption, and integration.
Introducing SCALE
One of the central components of this framework is a model I’ll be sharing in more detail called SCALE.
It outlines how transformation adoption progresses across levels, from stability and risk through growth and evolution, and where breakdowns tend to occur.
What This Is, and What It Isn’t
I’m still working through how to best document and package this.
What I can say is this: the concepts and constructs aren’t new. This is an evolution, a way to make sense of existing approaches, adapt them to context, synthesize hybrids where needed, and understand why they sometimes fall short.
What Comes Next
There’s more behind this than what fits in a single article.
I’m working on documenting it in a way that does it justice, with the ultimate goal of collaborating with the broader community to evolve it as an open source framework, supported by tools that are built and shared openly.
More to come.
#BusinessTransformation #ChangeManagement #SystemicThinking #CapabilityBuilding #StrategicAlignment #TransformationFramework #AITransformation #OpenSourceChange
1/3 - Charles Haywood, I appreciate this, and I agree with you. I struggled a bit with how to introduce this. There are a few different entry points. I could have started with the underlying theories it’s built on, or led with some of the tools associated with the framework to make things more practical and tangible, and then built up from there. I’m working off a spectrum that runs from theory, to framework, to model, to methodology, to process, to diagnostics, and down to tools. I felt deciding where to enter that spectrum wasn’t straightforward, because where you enter it shapes how the work is understood. The goal is to frame this so that it's as practical as possible, it's not an academic piece, but I want to show that the foundation is sound.
2/3 - Charles Haywood, the intent is for this to distill into a model that is simple to grasp, while still being grounded in a more complex underlying engine that determines how it actually works. Some people will only care about the model, others will want to understand what’s behind it. Part of this is also making sure the pedigree is visible, which theories and approaches it's built on, because for some that matters, and for others it won’t, but it should be there for those who are looking for it. The outcome should be a practical, useful, hands on model that is easy to grasp and apply, while still having enough depth to be adapted in a way that remains robust and effective, provided the person using it understands its intricacies, constraints, and limitations. It is not meant to be a magic elixir.
3/3 - Charles Haywood, the other piece I want to make clearer is the focus. The focus is systemic, progressing from organizational core competencies through functional competencies that enable strategy, down to team and individual competencies, instead of treating each layer as separate. I’ll explain in more detail in the next article. The goal is to make it usable at multiple levels depending on how deeply someone wants to engage with it. Your comment helped me realize that I need to provide a bit more context. I’ll expand on the genesis of the framework and the thinking behind it in the next piece, especially why I decided to frame it this way. Appreciate you taking the time to write your comment, great stuff! Thank you!
Allen, I like where this is headed. The framing is thoughtful, and I especially appreciate the effort to move beyond linear, activity-based views of change and toward the conditions that allow transformation to actually take hold across a system. The focus on interpretation, capability, adoption, and integration feels directionally right to me, and it is clear there is a lot of serious thinking behind it. As a work in progress, my sense is that the next refinement may be less about adding more and more about simplifying what is already here. The ideas are strong, but at the moment they are still fairly concept-dense. For those of us who spend a lot of time thinking about change this way, that may not be much of a barrier. For a broader audience, though, I am not sure the practical value will be immediately apparent. I found myself wanting a plainer explanation of what this framework helps someone see, diagnose, or do differently. A concrete example or two would probably go a long way. Overall, there is something genuinely promising taking shape here. The foundation is strong. I would say keep refining it in a way that makes the value easier for others to recognize and apply. There is a lot here worth developing.