How I Work

Understand first. Then take responsibility.

Every transformation starts from a different position. Before deciding what needs to change, I work to understand the business, the technology, the people responsible for it and the pressures driving the transformation.

Discuss your technology challenge →

The first priority isn't a roadmap.

When I enter an organisation, I don't arrive with a predetermined transformation plan.

I spend time with senior management, technology leadership, engineering teams and other stakeholders who understand the situation.

  • Business direction
  • Technology landscape and architecture
  • Delivery and operational constraints
  • Security and regulatory risk
  • Team structure, ownership and capability
  • Suppliers and important dependencies

The purpose isn't to document everything. It's to understand enough to know where leadership attention is actually required.

  1. 01

    Understand

    Get close to the business and technology. Distinguish root problems from symptoms.

  2. 02

    Establish Control

    Clarify priorities, ownership, risk and visibility. Address immediate concerns.

  3. 03

    Transform

    Lead the changes the organisation actually needs rather than hand over a roadmap and step away.

  4. 04

    Strengthen

    Build internal leadership, ownership and engineering capability while making the change.

  5. 05

    Transition

    Move responsibility progressively into the organisation until external transformation leadership is less necessary.

Control before transformation theatre.

The early part of an engagement is deliberately weighted towards understanding and establishing control.

I would expect the organisation to progressively gain a clearer picture of its technology position, clearer priorities, greater delivery visibility, important decisions and a credible transformation direction.

Understand enough to make good decisions, establish control, then transform.

Hands-on doesn't mean doing everyone's job.

I operate as part of the technology leadership of the organisation, working with the CEO, board or senior management while remaining available to technical leaders and engineering teams where decisions need deeper technical involvement.

My role is to make sure the organisation has the leadership, decisions and ownership needed for its technology functions to succeed.

Advice matters. Accountability matters more.

Where a decision falls within my responsibility, I expect to take it. Where it belongs elsewhere, I expect to help the person responsible make it confidently.

Transformation needs decision-making, not an ever-growing list of recommendations.

Engagements are built around outcomes.

A Transformation CTO engagement starts with the change the organisation needs to achieve — not a predetermined number of days each week.

The scope, level of involvement and duration are shaped around the transformation, the starting position and the outcomes we agree need to be achieved.

The measure of the engagement is progress towards the agreed outcome — not time consumed.

With the organisation, not around it.

Existing knowledge matters. Existing teams matter. Lasting change requires people inside the organisation to understand why decisions are being made and ultimately own what comes next.

Need someone to lead the change?

You don't need to have the transformation fully defined before we speak. Start by telling me what's happening.

Discuss your technology challenge →