How we work

Discover, Design, Enable

One approach, applied consistently across every area we work in. The subject matter changes. The method does not.

Why the sequence matters

Most transformation work fails at one of two points, and both are avoidable.

It fails at the start when the problem is assumed rather than understood, so effort is spent solving something that was never the constraint. It fails at the end when a sound recommendation is handed over and nothing happens, because nobody worked out how it would actually be delivered.

Discover, Design and Enable exist to close both gaps. Understand before recommending. Make the recommendation executable before calling it finished.

This is a working sequence, not a proprietary methodology. It is deliberately simple because the difficulty lies in doing it honestly, not in naming it.

The three stages

1

Discover

Understand the business, the outcomes you want, and what is standing between where you are today and where you want to be.

We look across customers, people, processes, information and technology to uncover constraints, dependencies and opportunities.

2

Design

Determine what should change and what matters most.

We turn discovery into clear priorities, practical operating and process improvements, capability requirements and informed technology decisions.

3

Enable

Turn recommendations into something executable.

We help shape solutions, define implementation roadmaps and provide the expertise needed to move from recommendation to change.

Discover

Understand the business rather than assume the solution.

We explore the outcomes you want, how work actually gets done, where performance is constrained and which of those constraints genuinely matter. That spans customers, people, processes, information, systems and the operating model around them.

Discovery is finished when we can say what is holding performance back and where change would create the most value, with evidence rather than assertion.

Design

Determine what should change and what matters most.

Depending on the engagement this can include operating-model changes, process and customer-journey redesign, capability requirements, technology options, architecture decisions and a prioritised roadmap.

The objective is not a long list of recommendations. It is a defensible answer to what should change and why, with the trade-offs made explicit rather than hidden.

  • Evidence rather than assumptions
  • Business outcomes rather than technology outputs
  • Practical trade-offs rather than idealised designs
  • Clear priorities rather than wish-lists
  • Solutions that can realistically be implemented

Enable

Turn recommendations into something executable.

We help shape solutions, define implementation roadmaps, make the architecture decisions that implementation depends on, and provide the expertise to move from recommendation to change.

Enable does not assume every engagement becomes a large implementation programme. The level of support should fit the scale of the problem and what the organisation can absorb. Sometimes the most useful thing we do is make your own team's delivery possible.

A recommendation nobody can act on is not a result. It is a document.

What this looks like in practice

The same method, applied to different subject matter.

In Cloud, Discover establishes what the estate costs and delivers, Design determines which changes are worth making and what they affect, and Enable puts them into effect with governance that holds afterwards.

In AI Automation, Discover establishes how work actually happens, Design determines what the work should look like, and Enable implements the automation, integration or AI capability that supports it.

Same sequence. Different evidence, different decisions, different delivery.

Start with the problem, not the solution

The most useful first conversation is usually a description of what is happening in the business, not a specification of what you think you need.

Discuss your challenge