Frequently Asked Questions

Answers to top 10 questions from executives navigating enterprise transformation in the age of AI.

1.

Why bring in external support when we need to own this change ourselves?

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.

2.

Is this relevant for a PE portfolio company, distributed multinational, or complex matrix structure?

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.

3.

What does the first phase of work actually look like?

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.

4.

How much of my executive team's time does this require?

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.

5.

How do we work together on design and execution?

We work side by side, combining capabilities neither of us has alone.

You bring deep knowledge of your business, your markets, and what actually works in your organisation. We bring enterprise design capability: the perspective to see structural patterns across complexity and the mandate to make calls that reshape how decision rights and governance function. Together, that combination produces clarity and momentum that neither achieves independently.

The work is collaborative from the start. We're embedded with your teams, designing and executing together. When we're configuring operating models or resetting decision rights, your people are in the room making those calls with us. When execution accelerates, we're working alongside your teams to ensure the structure holds under pressure. Where your internal capability is strong, we amplify it by removing friction. Where it needs building, we develop it through the work itself.

What makes this partnership effective is precision about what each side contributes. We bring a capability most organisations use episodically but don't need permanently: enterprise-level structural design authority. You bring the organisational knowledge, the relationships, and the sustained execution capacity that makes transformation real. We work together until the capability transfers and your teams can operate the new structure independently. The goal isn't prolonged partnership. It's building something together that works long after we've stepped back.

6.

We have capable internal teams—how does this work alongside them without undermining ownership?

It strengthens their work by bringing capabilities they don't maintain internally.

We bring specialised transformation expertise built across decades: experience redesigning operating models across sectors, geographies, and different scales of complexity. We've seen the structural patterns that create friction and the design moves that resolve it. Our focus is transformation methodology—the how-to of planning, designing, and executing structural change for value.

We work alongside your teams, making the enterprise-level structural calls—operating model, decision rights, governance—while your people drive execution within that clarity. The outside perspective and specialised transformation know-how we bring, paired with your people's deep business knowledge and execution strength, produces results neither achieves independently. When done correctly, this doesn't undermine internal ownership. It strengthens it by removing the structural ambiguity that makes their work harder than it needs to be.

7.

How do we know if this is working?

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.

8.

What changes between start and finish of an engagement?

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.

9.

What determines whether this succeeds or stalls?

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.

10.

How do you work alongside other firms and advisors?

We work client-side, which changes the dynamic entirely.

Most transformation work involves multiple parties: your internal teams, technology implementers, specialist advisors, delivery partners. Our role is to sit on your side of that complexity, not add to it. We're embedded with your leadership team, helping you make sense of competing recommendations, resolve conflicts between workstreams, and ensure everyone is working to a coherent enterprise design.

We're not a large-scale delivery organisation, but we can manage one. We've orchestrated programs where dozens of specialist firms are contributing, and the client needs someone with enterprise-level authority ensuring it all connects. What matters isn't who does the work. It's whether the work produces a coherent outcome. When you're managing multiple advisors, technology partners, and implementation teams, someone needs to hold the structural logic. That's where we sit.

We've found this approach works because it's clear where accountability sits. Your other advisors bring deep capability in their domains. We ensure those capabilities serve a coherent enterprise design rather than optimising in isolation. The synergies come from clarity of purpose, not from everyone agreeing. When roles are clear and the transformation approach is coherent, multiple firms working together strengthens the outcome. When roles blur and coordination is weak, it creates friction. We've seen both, and we structure for the former.

Have a question that isn't answered here?

Start a conversation