Two enterprise transformations. Different sectors, different scales, different starting points. The same structural problem — and the same operating architecture to close it.
All client details are anonymised. The outcomes are not. These are the specific, measurable results of applying the EWoW operating system in environments where transformation had to work.
Three large-scale engineering and software programmes, spanning Land, Air, and Sea domains, were running simultaneously within a highly regulated environment. Each programme had its own delivery teams, its own planning rhythms, and its own reporting structure. At portfolio level, leadership was managing three separate realities.
Strategic direction was set at the top. By the time it reached the teams doing the work, it had been filtered, translated, and in some cases lost entirely. The gap was not a failure of intent. It was a failure of architecture. There was no operating design connecting leadership decisions to delivery reality across all three programmes at once.
Dependencies between Land, Air, and Sea workstreams were managed informally and reactively. Cross-programme risks surfaced late, when they surfaced at all. Portfolio visibility depended on manually compiled status reports that were out of date by the time they reached leadership. Decisions were being made on incomplete information, under time pressure, with real contractual consequences.
The challenge was not that the organisation lacked capable people. It had exceptional engineers and experienced programme leaders. The challenge was that the architecture connecting them did not exist.
— Sabrina C E Noto, reflecting on the engagementComplexity in this environment was not incidental. It was the operating condition. Any operating design had to function within it. Not simplify it away.
Land, Air, and Sea programmes shared dependencies but operated under different technical disciplines, different stakeholder environments, and different delivery rhythms. Coordination across all three required a shared operating architecture. Not a coordination meeting.
A highly regulated environment with obligations that could not be reduced or worked around. Every governance design had to provide genuine control, not the appearance of it. The challenge was creating governance that enabled delivery pace within those constraints.
Governance processes that had accumulated over time without being designed as a coherent system. Not broken, but not functioning as an enabling architecture. Redesigning without disrupting ongoing programme delivery required precision.
Customer milestones with contractual weight. International customer and partner groups with different visibility requirements. Leadership needing accurate, real-time information shareable across organisational and national boundaries.
Each of the three programmes was at a different point in its maturity. One team was experienced with structured delivery; another was transitioning from a traditional project model; the third was building capability from a lower base. The operating design had to work across all three simultaneously.
This was not a transformation programme in an environment where delay means a missed internal target. Schedule slippage carried contractual, commercial, and strategic consequences. The operating architecture had to work. From the start.
The operating design EWoW introduced was not a set of processes. It was a connected architecture across all six layers, from strategic alignment at portfolio level to team operating models at delivery level. The changes are described here in terms of what became possible, not what was installed.
For the first time, portfolio leadership could see the delivery health of all three programmes, Land, Air, and Sea, from a single live view. Not a compiled report. A real-time architecture built in Jira with BigPicture and Advanced Roadmaps, flowing bottom-up from team boards to the portfolio dashboard continuously.
OKRs were designed to translate customer milestones into team-level goals, creating a direct, verifiable line from contractual commitments to the work planned in each sprint. Teams understood why their work mattered strategically. Leadership could trace delivery activity back to strategic intent.
Big Room Planning, introduced across all three programmes simultaneously, created the first shared quarterly view of interdependencies between Land, Air, and Sea workstreams. Dependencies that had previously surfaced as programme risks were now surfaced as planning inputs, addressed in the room rather than escalated six weeks later.
The existing governance architecture was mapped to distinguish between controls that provided genuine oversight and processes that provided its appearance. The result was a governance model that maintained the rigour the environment required, while removing the overhead that had been adding weeks to every significant decision.
The operating design was built to transfer. Internal leads were developed to run Big Room Planning, the LPM cadence, and the delivery intelligence layer without external support. By the end of the engagement, 75% of the consultancy function had been replaced by internal capability. Deliberately and measurably.
The EWoW engagement was not designed as a set of workstreams. It was designed as an integrated operating architecture: six layers, all activated simultaneously, each one connected to the others. The five pillars below describe the strategic intent of each component of the design.
LPM was introduced at portfolio level to connect investment decisions to delivery reality in real time. Bi-weekly portfolio reviews gave leadership an accurate view of cross-programme health, surfacing risks and reallocating capacity before issues became programme-level problems. The governance architecture was designed to enable pace, not obstruct it.
Strategic goals were translated into Objectives and Key Results at portfolio level, then cascaded to programme and team level. For the first time, teams could trace their daily work to a specific customer commitment. Leadership could verify that delivery activity was aligned to strategic intent. Not just moving.
Quarterly Big Room Planning was introduced across all three programmes together, bringing programme leads, engineering disciplines, and delivery teams from Land, Air, and Sea into the same planning event. Cross-programme dependencies were surfaced, committed, and tracked. The quarterly rhythm became the mechanism through which the three programmes operated as a coordinated portfolio.
A Jira data architecture was designed to flow delivery information bottom-up: from team sprint boards through engineering dashboards to a single portfolio view for leadership. The architecture was built around the three-programme structure, with BigPicture providing cross-programme visibility and Advanced Roadmaps providing strategic timeline alignment. Leadership stopped waiting for status reports. They had continuous, accurate visibility.
These outcomes were measured at the close of the engagement and independently reported by programme leadership. They are stated precisely, not as approximations, because precision is what distinguishes a measurable operating transformation from a consulting engagement that reports activity.
A second EWoW engagement in a different sector, at a different scale, with a different structural challenge. The same fundamental problem at its core.
An international organisation operating across three countries had a planning problem that went deeper than the planning process. Annual planning cycles were creating organisations that could not respond to the environment they were operating in. By the time a plan reached the teams executing it, the assumptions it was built on had changed. Teams were working to plans that were already out of date. Leadership lacked the architecture to correct course.
EWoW designed the shift from annual to quarterly planning across all three countries simultaneously. Big Room Planning events at international portfolio level connected local team delivery to portfolio-level goals for the first time. Internal facilitators were developed to run the quarterly planning cycle independently. The organisation sustained the operating model without ongoing external support after the engagement ended.
The shift from annual to quarterly planning is not a process change. It is an architectural one. The organisation had to build the connective tissue between strategic intent and delivery reality, and then trust it enough to operate at a quarterly cadence.
— Sabrina C E NotoIn both engagements, the problem was not a lack of capability. It was a lack of operating architecture. EWoW closes that gap and builds the internal capability to keep it closed.
Both engagements began with a structured organisational diagnostic. No operating design was proposed before the evidence was gathered.
Strategy, governance, planning, delivery, visibility, and human systems were activated together — not sequentially. The gap closes at every level at once, or it does not close.
In both cases, the engagement was designed to make itself unnecessary. The operating architecture was transferred to internal capability, sustained independently after EWoW left.
Every EWoW engagement begins with a structured conversation about your specific situation. No pre-formed recommendations. An honest assessment of whether EWoW is the right operating architecture for it.