_edited.png){kind=small}
Simplifying complexity in capital-intensive programmes.
Not by removing things — most of the complexity is real — but by working out which parts carry weight, and making those unmistakable. Across process, reporting and decisions, for leaders in data centres, infrastructure and energy.
Founded by Carol Mota. Nine years inside Google's data centre programme, latterly designing its delivery operating model for EMEA.
IN PRACTICE
What this involves
-
Process definition and standardisation across functions
-
Standard operating procedures, templates and deliverable catalogues
-
Executive and board reporting structure, and cadence design
-
Gap analysis between what a programme believes it has and what it actually has
-
Decision rights, escalation paths and governance that survives multi-site scale
-
Board packs, leadership updates, investor and bid material — rebuilt around the decision they exist to serve
-
Strategy translated into something teams can align behind and act on
Simplification gets mistaken for compression — the same material, shorter. That version fails, because the hard part was never length. A programme carrying real complexity has hundreds of true things in it, and only a handful change what anyone does next.
WHERE THE WEIGHT SITS
PROCESS
How work actually gets done.
UNSETTLED
Tribal knowledge. Handoffs that depend on who happens to be in the room.
SETTLED
Defined ownership and repeatable handoffs across functions.
REPORTING
What leadership actually sees.
UNSETTLED
A monthly reconstruction exercise that evidences activity.
SETTLED
Status, dependencies and slippage in one place, supporting a decision.
DECISIONS
Who decides, and on what basis.
UNSETTLED
Blurred authority. Exposure accepted without anyone deciding to accept it.
SETTLED
Decision rights that hold at scale, and material a room can act on in the meeting.
Three surfaces, and the same question on each: what actually carries weight here, and can anyone point to it? Sometimes nobody has decided. More often it was decided, and never written down — or written down in a form nobody can act on. An engagement might be one surface. At full scope it's all three together, as a delivery operating model: designed, embedded, and handed over.
THE WORK PRODUCT
If the important thing doesn't look important, it isn't clear yet.
Everything we produce is designed — not decorated. Designed in the sense that the visual hierarchy matches the decision hierarchy: what carries weight is what your eye lands on first, and what doesn't is out of the way.
This isn't presentation polish. A governance model nobody can read isn't a governance model. Reporting that takes twenty minutes to interpret has already failed as a control. When everything on the page looks equally important, the complexity has been documented rather than simplified.
Deliverables are built to be understood at the speed a senior room actually reads — in the meeting, not after it.
AT FULL SCOPE
Built to hand over, not to make itself necessary.
When all three are addressed together, that's a delivery operating model — one delivery system across functions rather than five parallel ones.
We design it, embed it alongside the teams who will run it, and hand it over. Handover is a contractual deliverable, with a tapering role by design.
An external partner with a defined exit serves a programme better than a role whose purpose becomes its own continuation.
METHOD
01
Clarify
Establish what's actually true, what's actually being decided, and what's noise. Usually this means mapping the process as it runs rather than as it is documented.
02
Structure
Build the process, the reporting or the model that carries it — designed with the people who will use it, against how the programme actually operates.
03
Embed
Put it in the hands of the people who run it, and make sure it holds without us. Handover is planned from the start, not negotiated at the end.
Three stages. The third is the one most engagements skip.
Most engagements stop after the second stage. The deliverable lands, the room agrees, and six months later the programme has drifted back because nothing was ever transferred to the people doing the work. A model that has to be enforced has already failed.
RECENT ENGAGEMENTS
A selection of recent work, anonymised.
REPORTING
North American hyperscale developer
Rebuilt a VP's leadership update, cutting meeting time by 60% across a team running a billion-dollar build programme.
PROCESS
North American data centre operator
A 54-slide legacy library distilled into a 17-archetype system, giving a fast-scaling operator a standardised communication infrastructure the whole team can use.
DECISIONS
FTSE 250 transformation
A 35-page strategy distilled into a 12-slide narrative used to align nine teams across a complex cross-functional programme.
DECISIONS
Data centre construction consultancy
Redesigned a capability statement that secured a shortlist for a major APAC infrastructure long-term agreement.
When we're the right partner.
We work with leaders in data centres, infrastructure and energy — usually at the point where the programme has outgrown the systems built for an earlier version of it.
The complexity in these programmes is real, not theatrical. Deciding what carries weight takes someone who knows what the weight is.
If you need volume output or a large agency team, we're not the right fit. If you need one senior person who will think hard about your problem and get it right, we are.