Frequently Asked Questions

You do own it. That's not negotiable, and we wouldn't want it any other way.

What we provide is something most organisations don't have internally: the perspective and mandate to redesign the operating model while standing outside it. Your internal teams have deep capability, but they're working within the system that needs redesigning. That creates a structural dilemma. They understand the business intimately, but they lack the position to make enterprise-level calls about how decision rights should work, where accountability should sit, or how governance needs to change.

We work alongside your people, embedded in the organisation, making those structural calls until your teams have the clarity and confidence to make them independently. Then we step back. The goal isn't to create dependency. It's to build the internal capability that makes us unnecessary. In our experience, ownership isn't threatened by external partnership. It's enabled by it when the partnership is structured to transfer capability, not protect expertise.

Yes, if you're navigating genuine enterprise complexity.

We've worked across quite different organisational contexts: PE portfolio companies under compressed timelines where precision and pace both matter intensely; distributed multinationals that need operating models working coherently across regions without losing local responsiveness; complex matrix structures where the org chart stopped reflecting how decisions actually happen years ago. The common pattern we see is this: when the structure doesn't match the complexity, AI doesn't resolve the friction. It amplifies it.

The work is relevant when structural clarity has become the constraint, not strategy or capability or capital. If the question your executive team keeps revisiting is "why can't we move faster when the path seems clear?" the answer is usually structural. That's the gap we're experienced in addressing.

Diagnosis, alignment, and design. In that order, and with discipline.

We start by working directly with your executive team to understand where decisions stall, where accountability blurs, and where the current structure creates friction that slows everything down. This isn't exhaustive analysis for its own sake. It's structured inquiry with the people who live the problem daily. What we're after is clarity on the gap between where you are structurally and where AI-enabled execution requires you to be.

Once that's clear, we align your executives on what the target operating model needs to look like and what decisions are required to get there. Then we establish who has the authority to make structural calls, and we build the transition plan. The sequence is consistent. The pace depends on your context, your complexity, and how ready your executives are to make structural decisions. In our experience, speed comes from focus and early resolution of the hard questions, not from deferring them.

More at the start, less as clarity builds. That's the pattern we see consistently.

Early on, we need regular time with your executive team. This is where the structural decisions get made: who owns what, where decision rights sit, how governance will actually work. Executive involvement here is essential because these aren't questions that can be delegated. We also spend time one-on-one with your functional and regional leaders, understanding how the current structure is experienced at the coalface.

As the structure becomes clearer and your teams start executing within it, the time requirement shifts. You move from active design to governance and oversight. We run working sessions with your teams in parallel, and executive time becomes less frequent but more focused. The front-loaded investment reflects something we've learned over many years: the structural choices made early determine nearly everything that follows. Getting those right, with the right people in the room, is what makes pace sustainable later.

We design the structure. You execute within it.

We configure the enterprise architecture: operating model, decision rights, governance. These are the structural conditions that determine whether execution across your organisation functions coherently or fragments into competing initiatives. Your teams do the execution work: process design, technology implementation, change delivery, all the detailed work that makes transformation real.

Think of it as designing the building versus fitting it out. You don't need us running projects or managing workstreams. What you need is the structural clarity that allows your capable people to execute without constantly fighting the organisation. Where your internal capability is strong, we make sure the structure enables it. Where capability needs to be built, we build it with your people, not for them. We've found that the organisations that get lasting value are the ones where we transfer capability deliberately, not the ones where we stay longest.

It works because we're providing something different from what your teams do, not something better.

Your transformation teams are typically strong on delivery. They know how to run projects, manage workstreams, and drive execution. What they often don't have is the mandate to redesign the structures they're working within. Functional leaders control resources. Regional leaders control execution. Your transformation teams are expected to orchestrate across that complexity without the authority to change how decision rights work or how governance functions.

We operate at a different level. We make the structural calls that create clarity for everyone else. That's not competing with your teams. It's removing the structural ambiguity that makes their work harder than it needs to be. What we've seen across many organisations is that external support structured this way doesn't undermine internal ownership. It strengthens it by giving your people a coherent structure to work within rather than asking them to navigate around one that doesn't fit anymore.

You'll see it in how your executives operate, and you'll see it relatively early.

Three things tend to show up when the structural design is landing. First, your executives stop cycling through the same unresolved questions about who owns what, where accountability sits, and how decisions should work. They start executing within a structure they've agreed to. Second, cross-functional decisions start moving faster, not because someone forced agreement but because the framework for making those decisions is clearer. Third, your internal teams reference the operating model in their day-to-day work rather than working around it or treating it as a compliance exercise.

These aren't things you measure at the end. They surface as the work progresses, and they tell you whether the structural design is taking hold. If you're still debating fundamental questions about authority and accountability well into the engagement, something hasn't worked. If decisions are cleaner and execution is crisper, it has. The measure isn't how elegant the design looks. It's whether your organisation can use it.

Four things shift, and they shift structurally rather than culturally.

Your operating model moves from something implicit, known only to insiders, to something explicit that people can actually execute against. Not documented for compliance, but designed so your people can make decisions without constantly escalating. Decision rights move from overlapping and contested to clear enough that conflicts can be resolved through structure rather than negotiation every time. Governance moves from reactive intervention to something structured, where you're managing AI deployment, risk, and performance through defined authority rather than ad hoc.

Perhaps most importantly, your internal capability shifts. The people who were dependent on external support to make structural calls become confident making those calls themselves. They understand the design logic, not just the outputs. What we've learned is that the real measure of success isn't how long we stay. It's whether your organisation operates more coherently after we leave than it did before we arrived, and whether your people have the capability to sustain that without us.

Executive willingness to make structural decisions. That's the binding constraint in our experience.

If your executives are prepared to clarify decision rights, resolve overlapping accountabilities, and commit to governance that constrains as well as enables, the work succeeds. If they want transformation without structural trade-offs, it stalls. The constraint is rarely capability or capital. It's the willingness to make decisions that redistribute authority, simplify governance, and hold people accountable to structures that work differently from what they're used to.

Structural change asks executives to give up ambiguity that protects optionality. That's uncomfortable. The organisations where this succeeds are led by executives who recognise that speed at scale requires clear structure, not endless flexibility. The ones where it stalls are led by executives who want the benefits of both and end up with neither. We can bring expertise, experience, and perspective. What we can't bring is the executive commitment to make decisions that change how authority actually works. That has to come from you.