Transformation consulting

Some work needs shaping before it needs delivering

I help organisations make sense of important work that is still unclear, cross-functional or difficult to contain within a standard project brief. The immediate need may look like strategy, process, data, technology or delivery, but the real challenge is often working out how those pieces need to come together — and then helping make it happen.

When to involve me

The work is important, but the answer is not yet obvious

I am typically brought into work where the organisation knows that something needs to change, but the problem, scope or pathway is not yet sufficiently clear.

Different teams may hold different versions of the issue, the proposed technology may be driving the conversation, or a project may have accumulated so much activity that the intended outcome has become difficult to see. These situations do not always need a larger delivery team. They often need someone who can step across the boundaries, ask the difficult questions, connect the different perspectives, create a shared basis for action — and then help carry it through.

  • A strategic idea needs turning into a programme
  • A project has stalled or become too broad
  • Business and technology teams are not aligned
  • Several initiatives need sequencing
  • A vendor solution needs grounding in the operating context

Start with good

Start with what good looks like, not the inherited scope

A project can be very well organised and still deliver the wrong thing.

Before expanding the task list or documenting detailed requirements, I help the organisation clarify the outcome it is actually trying to create, who needs to benefit, what constraints genuinely matter and how the important trade-offs will be made. This does not mean waiting for perfect certainty. It means creating enough shared direction that decisions about scope, technology, sequencing and investment can be tested against something more meaningful than the momentum of the existing project.

Step 1
Desired outcome
→
Step 2
Decisions & trade-offs
→
Step 3
Scope & pathway
→
Step 4
Delivery

An integrated view

Bring the business, process, data and technology view together

Complex change becomes harder when each discipline solves its own part of the problem in isolation.

A process can be redesigned without accounting for the data needed to run it, a technology solution can be selected without clarity about the operating model it needs to support, and a programme can be sequenced around project convenience rather than business value. My role is to hold those views together long enough to understand the dependencies and make the important design choices visible. Depending on the work, that can draw on any of the areas below.

  • Discovery and framing

    Understanding the problem, defining good, and creating a shared basis for the decisions that follow.

  • Process and operating model

    Clarifying how work should flow, where accountability sits and what must support it.

  • Data and technology

    Translating technology opportunities into business outcomes and implementable design, including data flows and identity.

  • Roadmaps and project resets

    Reframing work that has stalled or grown too broad, and sequencing initiatives around value.

  • Facilitation and alignment

    Bringing the right people together and making difficult decisions visible.

  • Delivery and implementation

    Staying hands-on to help turn the decisions into a working result.

Phasing and roadmap

Sequence the work so learning and value build over time

A roadmap should do more than place a collection of projects on a timeline.

It should show why the work is sequenced in that order, what each phase enables, which decisions need to be made before further commitment, and how the organisation can learn without losing momentum. I help break broad transformation ambitions into deliberate stages that create useful outcomes along the way — separating foundational work from visible delivery, identifying what can be piloted, showing how dependencies build, and making clear where the end state still needs to evolve as the organisation learns.

How engagements start

You can start small, and stay in control of the commitment

Most work begins with a focused, bounded first step — enough to create clarity and decide together whether to go further. You are not signing up to an open-ended programme to get started.

Focused discovery

A short, bounded piece of work to understand and frame the problem and recommend a sensible next step. Often days to a few weeks.

Shaping engagement

Turn an unclear ambition into a defined, sequenced pathway with the key decisions framed. Typically a few weeks.

Advisory & delivery

Ongoing, hands-on support alongside a team — shaping the work and helping deliver it, at a cadence that suits. Scaled to need.

Outcomes

Help make the change actually happen

The value of an engagement is not the volume of documentation produced, and it is not advice handed over at the door. It is whether the organisation is genuinely further forward — clearer on the problem, decided on what matters, and moving.

I do not just create slide decks and walk away. I stay involved to help turn decisions into a working result. Depending on the work, that can mean a strategic briefing, discovery pack, target operating model, process and system design, roadmap, programme structure, or a facilitated series — but always in service of a real change landing, not a document being filed.

Discuss your challenge

Bring me the messy version

You do not need to reduce the challenge to a neat statement before making contact. Working out what the problem really is, what sits inside or outside the work and what type of support will help can be part of the first conversation. Email or call — whatever is easiest.