Technology Leadership Coaching

Your technology leader, stronger in the seat you gave them.

A leader who makes the unpopular call and brings the organization with them anyway: the kind of appointment that looks obvious in hindsight.

Engagement

Ongoing. Runs until the goals set at the start are met, with a call in between whenever a decision will not wait.

When people call us

The IT director you promoted is still the one fixing the outages, AI has landed on someone without the authority to match, or the steering committee keeps sending the hard question to its next meeting.

Who we coach

01

The leader you just appointed

Hired in, a new CIO or IT director inherits a list of what went wrong under the last one, and is expected to have read it. Promoted from within, they helped build what they now have to change, and someone on their team wanted the job.

02

Whoever is carrying AI

Answerable for AI the business adopted before anyone asked IT. The work is deciding who owns what before an incident decides it, then ending the bets that will not pay and bringing along the people who fear the ones that will.

03

The sponsor of your biggest program

Usually a COO or VP, rarely a technologist. Sponsoring an ERP or ETRM replacement looks ceremonial at kickoff and turns out to be the job. The calls that decide it come at predictable points, and the coaching lands just before each one.

04

The first to hold a new role

Product owners, PMO leads and Centre of Excellence heads, in titles that changed before the decisions did. Colleagues still take their requests to whoever used to say yes. A new operating model is a drawing until the people in it start deciding differently.

05

The leader who takes over from us

When our fractional CIO mandate ends in a permanent hire, we can stay on as the new leader's coach. We know why each call was made and have no stake in keeping it. The agenda is theirs, including the parts they decide to undo.

06

The team around your leader

Some questions keep coming back because they belong to the whole leadership team, not to one person in it. What the company will and will not do with AI is the obvious one. We run the session that settles it, then follow up one to one so it stays settled.

Advisory work on the same ground

More of our work

Fractional AI advisor — financial services

A role the company had never had: which AI tools to use, where they belonged, and how to bring people along on them. Read the work

Moving to product-centric IT

IT was organized around projects, and the business needed more continuity than projects give. We defined the products, designed long-lived teams around them, moved the funding and took the organization through the change. Teams now stay with what they build. Read the work

PMO and stage-gate delivery

One consistent way to govern projects from approval to delivery, with gates that say what each stage requires and a forum that runs the cycle. Projects now start only once approved, and problems surface while there is still time to act. Read the work

You chose the person leading your technology, or put someone’s name on the program the business is betting on. Their success is now partly yours. You are also the last person who can coach them, and the last person they want watching them struggle. We coach them on the work in front of them, so you can back them without standing over them.

The job is the curriculum

Sessions start from whatever is stuck: the pilot everyone likes and nobody can justify, or the vendor who keeps missing dates because they know nobody will switch. Stuck decisions rarely look like failure. They look like caution, which is why they last.

We work each one through until your leader knows what they think and why. Then they make the call, in their own name. We never speak for them, to you or to their vendors. If the answer turns out to be a project rather than a decision, we say so, and your leader chooses who does it.

Not every leadership problem is the leader’s

A new IT director buried in escalations may be doing the job well, inside an operating model that sends everything upward. An AI lead blamed for tools nobody approved has an ownership gap, not a skills gap.

We treat people, process, information and technology as one system, and the leader is part of it. We bring our own models where they earn a place: engage–plan–build–operate to find where decisions stall, and our AI governance and implementation framework when nobody has written the rules for AI. When the problem turns out to be structural, your leader hears that plainly, and walks into the executive meeting with the case for fixing it already made.

The decision is the easy half

Every technology decision is a decision about how other people will work, and it only counts once they do. Most of what goes wrong after a good call is people hearing about it late and second-hand.

Change management runs through all our work, and bringing AI and new technology into how people work is a specialty. In coaching it becomes your leader’s own habit: knowing who has to hear it first, and hear it from them, and what to say when a conversation about AI turns into one about jobs. For a sponsor, it means being in the room where a program is really decided, at design sign-off and the go-live decision, with their peers on side.

With AI it starts closer to home. People take their lead from a leader who uses it on their own work, not from a memo about it.

When coaching is the wrong bet

If the seat is empty, or the job will not wait for anyone to grow into it, that is a fractional CIO. If the program itself needs an independent read, that is delivery assurance. And if the real question is whether your leader is the right person, coaching is the wrong cover for it.

Coaching also fails when it is done to someone. Your leader has to want it, and you have to want them to succeed more than you want a report. So we talk to them before anyone agrees to anything.

Start with a 45-minute briefing.

No pitch. Bring the decision you are stuck on and we will tell you what we would do about it, including when that is nothing.