I did not set out to create a methodology. That was never the plan.
When I started out in transformation, I did what most people do. I learned the frameworks. I got the certifications. I understood Agile, Lean, PRINCE2, SAFe, and all the rest. And I went into organisations and tried to apply them.
Some of it worked. A lot of it did not. And over time I started to notice a pattern in what was failing, and it was not the organisations.
The frameworks were telling people how they should work. Nobody was asking how they actually worked. Nobody was asking what was already working well and should be protected. Nobody was starting with the organisation as it actually was rather than as the framework assumed it to be. And organisations were being asked to throw away decades of operational knowledge and replace it with a methodology designed somewhere else, for someone else, in a completely different context.
I watched good teams get worse after transformation. Not because they were resistant. Because they were being asked to abandon the parts of their way of working that were genuinely effective, alongside the parts that needed to change. Nobody had taken the time to tell the difference.
That is when I started building EWoW.
"Every framework I had ever been trained in told organisations how they should work. None of them started by asking how they actually worked. That gap is why EWoW exists."
What makes EWoW different
The thing that separates EWoW from every other framework I have encountered is this: it does not dictate how people work.
That sounds simple. It is not common.
Most methodologies, even the ones that claim to be flexible, arrive with a set of assumptions about how teams should be structured, how planning should work, how decisions should be made, and what good delivery looks like. They are designed to be applied consistently. The idea is that if everyone follows the same approach, you get alignment and predictability.
What you actually get, in most cases, is compliance theatre. People go through the motions of the new way of working while quietly continuing to do the things that actually get the work done. The methodology is adopted on paper. The organisation continues to operate the way it always has, just with more meetings.
EWoW works differently because it starts by understanding what is already there. Not to preserve everything. Not to avoid change. But because sustainable transformation has to be built on honest foundations. You cannot design a strategy for where an organisation needs to go if you do not properly understand where it actually is.
EWoW blends traditional and evolved approaches. Where something is working well in the existing way of working, we keep it and build around it. Where something needs to change, we bring in the methods and practices that fit that specific problem in that specific context. Agile where agility is genuinely needed. Traditional governance where structure and compliance are non-negotiable. Lean where waste and efficiency are the core challenge. The blend is different every time because every organisation is different every time.
And critically, teams are not forced to work the same way as each other. A programme board and a software engineering team and a contracts function do not have the same needs. Asking them all to operate identically is not alignment. It is uniformity, and those two things are not the same.
How it starts: the 30-60-90
The process I use to build every EWoW strategy begins with what I call the 30-60-90. It is not a rigid timeline. Depending on the size and complexity of the organisation, the 30 might take 30 days or considerably longer. The number represents a sequence, not a deadline.
The 30 is where I listen. Really listen. It starts with an online survey sent across the organisation, asking questions about how people actually work. Not what the process says. What they actually do. How planning happens in practice, how long things take, what the hours look like, where the friction is, what people wish they could change. The survey gives me data. Patterns emerge that I can analyse and use to validate the strategy we will eventually build. But the survey alone is not enough. Data tells you what. People tell you why. So alongside the survey, I conduct face-to-face interviews. Individual conversations, structured enough to cover the ground I need to cover, open enough for people to say the things they would never write in a form. The interviews are where people open up. Where I hear about the governance meeting that everyone knows is useless but nobody has the authority to cancel. Where I hear about the reporting process that takes three days every month and nobody reads the output. Where I hear about the team that has quietly developed a workaround that is genuinely more effective than the official process. The 30 ends with a clear picture of the current state. Not a sanitised version. The real one.
The 60 is where we act on the improvements we can make immediately, without waiting for a full strategy to be designed and approved. They matter for two reasons. First, because some of the things holding the organisation back are genuinely simple to fix and there is no reason to wait. Second, because quick wins build trust. When people see that the process they always hated has been simplified, or the report nobody read has been discontinued, they start to believe that this transformation is actually going to be different. That credibility is worth more than any strategy document.
The 90 is the strategy build. By this point I have the evidence, I have the trust, and I have a clear picture of where the organisation is and what it needs. The EWoW strategy is built around that reality. It is specific to this organisation, this programme, this set of challenges. It borrows from every methodology I have learned over twenty years, taking what fits and leaving what does not. It does not look like anyone else's transformation strategy because no other organisation has the same starting point.
"When I go back to leadership with recommendations I am not asking them to trust my instinct. I am showing them evidence drawn from their own people about what is actually happening and why."
Why it works
EWoW works because people recognise themselves in it.
When a team sees a strategy that has been built around how they actually work, that respects the things they do well and focuses change on the things that genuinely need to change, they engage with it differently. They do not feel like something is being done to them. They feel like they have been heard.
And that matters because they were heard. The 30-60-90 process involves everyone. Not just leadership. Not just the people in the room when the strategy gets signed off. Every level, every role, across the whole programme or organisation. The person managing contracts has the same opportunity to speak as the Chief Engineer. The team lead on the ground has the same voice as the Director. The survey goes to all of them. The interviews go to all of them. The strategy that comes out at the end is built from all of that, not just from the view at the top.
This changes the nature of the change itself. People are not being asked to adopt something that was designed without them. They are part of the design. They contributed to it. And when implementation begins, they recognise their own experience in the strategy, because their experience shaped it.
That is not a soft outcome. That is the single most important factor in whether transformation sticks. People do not resist change because they are obstinate. They resist change that does not make sense in the context of their actual working reality. When the change makes sense, when it is visibly built on an honest understanding of where they are, the resistance largely disappears.
I have watched organisations that had failed two previous transformation attempts succeed with EWoW. Not because EWoW is magic. Because this time, somebody actually listened first. And that somebody listened to everyone, not just the people with the most senior job titles.
EWoW also scales. Because it is not strict, because it does not require every team to work in the same way or every organisation to follow the same sequence, it can grow with the programme or organisation it is embedded in. A small team and a global enterprise can both run EWoW because EWoW adapts to the size, the complexity, and the maturity of where it is being applied. It is not a framework that only works when conditions are perfect. It is built for the messy, complicated, real-world environments where most transformation actually happens.
What it is not
EWoW is not a product. It is not a certification programme. It is not a methodology that can be picked up by someone who has read a book and applied to any organisation.
It is a way of thinking about transformation that I developed over twenty years of doing the work in some of the most complex organisations I have encountered. It is embedded in every engagement I lead. And because it is tailored every time, it looks different every time.
Which is exactly the point.
Curious what EWoW would look like in your organisation?
Every EWoW engagement starts with listening. If you want to understand what that would look like in your context, get in touch.
Get in touch
20+ years delivering transformation across defence, NHS, financial services and enterprise. Creator of EWoW. Available for Head of Transformation, Director of Transformation and senior consulting engagements across the UK.