Twenty years across real organisations. The same problems, appearing in different industries, at different scales, with different names, but the same structural gap underneath.
This page explains what Sabrina C E Noto observed, why those observations led to the creation of EWoW, and what EWoW stands for today. It is not a sales page. It is the honest account of why a different approach was necessary.
I spent the first part of my career inside organisations, not advising them from the outside. I worked in telecoms, starting as a network engineer and moving into leadership over time. I understood systems. I understood how decisions made at the top took weeks or months to reach the people doing the actual work. And I understood, long before I had the language for it, that the way most organisations were structured was actively working against them.
When I made the decision to change direction in 2013, I had already spent years watching a pattern repeat. Leadership would set a direction. Months later, the teams executing the work would have a different understanding of it, or no understanding of it at all. Strategy and delivery were operating in separate realities. Not because the people were incompetent. Not because the leadership was disengaged. Because nothing in the organisation's structure was designed to connect the two.
I saw it in telecoms. I saw it in financial services, in public sector programmes, in enterprise software organisations running 40 teams across multiple locations. The sectors were different. The leadership teams were different. The language was different. But the structural problem was always the same.
The gap between what leadership decided and what organisations delivered was not a people problem. It was an architecture problem. And nobody was designing the architecture.
That observation, repeated across two decades and eight sectors, is the reason EWoW exists.
When I began working directly with organisations on transformation, something else became clear. Transformation was happening everywhere. Programmes were being launched. Frameworks were being adopted. Consultants were being hired, embedded, and eventually replaced by the next consultants with a slightly different methodology.
And yet, the underlying problems remained. Teams were still misaligned. Strategy was still not reaching delivery. Leaders were still making decisions based on information that was weeks out of date. The language had changed. Organisations were now talking about agility, value streams, OKRs, and product thinking. But the structural gap was as wide as it had ever been.
The transformation was real in the sense that things had changed. New processes existed. New ceremonies were running. New job titles had been created. But the change had not reached the operating model — the actual way the organisation made decisions, allocated resources, planned work, and connected leadership intent to delivery reality.
Transformation had become something organisations performed rather than something they underwent. The performance was convincing enough to satisfy a board review. It was not changing how the organisation actually operated.
I saw this in organisations that had spent years and significant budgets on transformation programmes. The slide decks were sophisticated. The language was current. The results were missing.
This was not a failure of effort. It was a failure of approach. And the approach was failing because it was addressing the wrong problem.
Let me be precise about this, because it is easy to misread. Frameworks are not wrong. SAFe, Scrum, Lean, Kanban: each of these contains genuine thinking about how work can be organised more effectively. The problem is not in the frameworks themselves. The problem is in how they are applied.
Frameworks are applied to organisations. They arrive from the outside with a prescribed structure, a defined set of roles, a sequence of ceremonies, and an assumption that the organisation will adapt to fit the framework. In some cases this works. In most cases it does not, because the framework does not start from an understanding of how the organisation actually operates.
The organisations I worked with were not blank pages. They carried years of embedded culture, informal networks, established authority structures, and institutional knowledge that no diagnostic tool or org chart captured. When a framework was applied without understanding those things, it encountered resistance. Not because people were obstructive, but because the framework was asking the organisation to become something it had not been designed to become.
The failure was not in the people who resisted. It was in the assumption that an organisation could be transformed by applying a framework to it, rather than evolving it from within.
There was something else. Most frameworks operate at one altitude. They address team-level delivery, or they address portfolio-level governance, or they address culture. Very few — arguably none — were designed to operate coherently across all four levels simultaneously: leadership, programme, function, and team. The gap between those levels was where transformation consistently stalled.
Middle management — the layer between strategy and delivery — was being asked to translate frameworks they had not chosen, to teams they were responsible for, in service of a strategic direction they had not been part of setting. The transformation asked a great deal of middle management and gave them very little structural support for what it was asking.
That is not a people problem. It is an architecture problem.
After years of watching frameworks fail to close the gap, the question I kept returning to was a simple one. What would actually work?
Not what should work in theory. Not what the framework said should happen. What actually produced lasting change in organisations that were genuinely complex — organisations with regulatory constraints, with political realities, with histories that mattered, with people who had seen three transformation programmes and were understandably sceptical of the fourth.
The answer that kept emerging from the evidence was not another framework. It was an operating model: a complete architecture for how the organisation makes decisions, allocates resources, connects leadership to delivery, and sustains that connection over time without depending on external support to maintain it.
The organisations that changed and stayed changed had several things in common. They had genuine clarity at leadership level about what they were trying to achieve and why. They had a governance architecture that made decisions faster rather than slower. They had a planning rhythm that connected strategic intent to delivery work every quarter rather than annually. They had real-time visibility of what was actually happening across the organisation. And they had invested in building the human and cultural conditions that made the operating model sustainable.
It was never one of those things in isolation. It was all of them, operating simultaneously, connected to each other. The organisations that had all six were the ones that held. The organisations that had three or four were the ones that regressed when the external support left.
What organisations needed was not transformation imposed from outside. They needed evolution designed from within — starting from an honest assessment of the current state, preserving what was already working, and building the architecture that closed the structural gap between strategy and delivery.
They needed something that fit the organisation rather than an organisation that had been reshaped to fit a framework. And they needed it to be designed to make itself unnecessary, building capability inside the organisation rather than creating a permanent dependency on external expertise.
EWoW was not created in a workshop or a design sprint. It was built incrementally, across real engagements, in environments where the methodology had to work because the consequences of it not working were visible and costly.
I did not set out to create a named methodology. I set out to solve the problem in front of me, every time, for every organisation. Over time, the patterns of what worked began to consolidate. The six layers that consistently needed to be addressed. The sequence that consistently produced lasting change. The conditions that consistently determined whether the change held or reversed. The human factors that no operating model document ever captured but that determined everything.
I formalised those patterns into EWoW — Evolved Ways of Working — and founded Direct Agility in 2013 to deliver it commercially. But EWoW itself is older than Direct Agility. The thinking behind it was being built long before it had a name.
EWoW is not a framework I was trained in. It is the distillation of twenty years of watching what works when organisations genuinely try to change — and what always, without exception, gets in the way.
The name matters. Evolved Ways of Working. Not transformed. Not disrupted. Not reinvented. Evolved. The word is deliberate. Evolution starts from what exists. It preserves what functions. It changes what needs to change. It does not assume the current state is wrong — it asks what the current state needs to become, and designs the path from here to there.
That distinction — between transformation imposed from outside and evolution designed from within — is the philosophical foundation of everything EWoW is and does.
EWoW today is a complete adaptive transformation operating system. Six interconnected layers — Strategic Alignment, Leadership and Governance, Planning and Coordination, Delivery Execution, Visibility and Intelligence, and Human and Cultural Systems — designed to operate simultaneously rather than sequentially.
It is applied through Direct Agility, the organisation I founded to deliver it commercially. Every EWoW engagement begins with a structured diagnostic: an honest assessment of the current operating state, what is working, what is fragile, and where the structural gaps are. The operating design that follows is assembled around the specific organisation. Nothing is prescribed. Everything is chosen because it fits.
EWoW stands for several things I consider non-negotiable.
No operating design before the organisation is understood. We map how you actually work, not how the org chart says you should, before recommending anything.
The goal of every engagement is to make external support unnecessary. The operating architecture is transferred to the organisation, with the internal capability to run it, sustain it, and continue evolving it independently. That is not a risk to the commercial model. It is the commercial model.
What success looks like is defined before anything starts. Tracked throughout. Reported honestly at the end, whatever the result. An engagement that produces mixed results is reported accurately. Ambiguity is not EWoW.
The operating model that fails because the people inside it do not feel safe to speak, do not understand why the change is necessary, or do not have the structural conditions to adopt new ways of working: that operating model will not hold. Human and cultural systems are Layer 6 in the EWoW model. Not the last thing to think about. The layer that determines whether everything else works.
The vision for EWoW is not to become a large consultancy. It is to become a recognised operating system: named, documented, independently deployable, and adopted by organisations as the architecture through which they evolve.
The organisations I have worked with that have fully embedded EWoW are still running it, years after the engagement ended. They have adapted it to their changing contexts. They have trained internal people to facilitate it. They have made it their own. That is what I mean by an operating system rather than a framework. It becomes part of how the organisation operates, not something that was done to it once and then replaced by the next programme.
The future of EWoW is one where it can be licensed, certified, and deployed by organisations independently of Direct Agility. Where internal practitioners are trained and qualified to run it. Where the IP is recognised and protected as the original work it is, not derivative of any other methodology, not licensed from any other framework, but created from evidence and built from the inside of real organisations under real pressure.
Organisations that operate by design, not by default.
That is what EWoW is working toward. Not the growth of a consultancy. The evolution of how organisations work.
If you are reading this because something is not working — a transformation programme that has not landed, a gap between what your leadership decides and what your organisation delivers, a change that reversed when the external support left — that is the problem EWoW was built to solve.
It started with an observation. It became an operating system. And it is still being built.
The About EWoW page explains the methodology. The Operating Model page presents the architecture. If you are ready to talk, start with a discovery call.