Founding CTOs, CTOs and heads of engineering
Coaching and supporting CTOs and heads of engineering
In short
I routinely coach and mentor founding CTOs, established CTOs and heads of engineering. The role changes every time the company does, and few technology leaders have someone to think with. I can also work alongside you as a peer, add leadership capacity, or take ownership of a difficult initiative.
You might recognise this
- You were the first engineer, and now you lead a team of teams.
- You are new in post and want an experienced peer to think with.
- An initiative matters too much to delegate, and you do not have the hours.
- You are learning to present technology to a board or investors.
How we might work together
Examples, not packages. They often overlap within one relationship, and we shape the work together.
See the examples
- Coaching and mentoring
- Confidential one-to-one conversations, at a rhythm that suits you.
- A trusted peer
- Testing strategy, organisation design and hard people decisions before you act.
- Taking on part of the load
- Owning one initiative, or running part of the organisation for a while, with you in charge of technology.
- Working with your engineers
- Helping your managers and engineers change how work gets done, alongside you, and developing the ones coming up behind them.
Relevant experience
- Took over technical leadership at Festicket from the founding CTO after a structured handover Read the case study
- Led engineering managers, DevOps and engineers across GMT−8 to GMT+8 as CTO at Remo Read the case study
- Part of the leadership trio for BBC News and World Service engineering Read the case study
- Coached and developed emerging engineers on the BBC’s year-long placement scheme for software engineering students, almost all of whom joined the BBC after completing their degrees; many now hold senior engineering positions at leading UK tech companies Read the case study
How we start
We start with a focused look at what you’re trying to achieve, what’s getting in the way, and how I could help. From there, we agree whether there’s a useful role for me and what it should involve.
- Understanding the business and what you are trying to achieve
- Meeting the people who matter to the work
- Looking at enough evidence to see where I could be useful
- Deciding together whether an ongoing role makes sense, and what it should be
Questions
Does bringing you in mean our CTO is failing?
No. It usually means the CTO has more priorities than hours, or wants a peer to think with. The remit is agreed with them, and they stay in charge of technology.
Is coaching confidential?
Yes. What we discuss stays between us unless you choose to share it.
Further reading
How do I choose a coach or mentor for a CTO or head of engineering?
Choose someone whose experience fits the decisions you face and with whom you can speak candidly. Discuss a real challenge, how they would work with you, and what remains confidential. Agree whether you need reflection, practical mentoring or direct organisational support, and how you will judge whether the relationship is useful. Read the full answer
How can we improve developer experience and remove delivery bottlenecks?
Find where engineers wait, repeat manual work or struggle to get reliable feedback. Follow a small change from idea to production and improve the biggest source of friction first. Developer experience includes tools, environments and CI/CD, but also clear priorities, useful reviews and access to the people who can make decisions. Read the full answer
How should a CEO and CTO resolve disagreements about technology priorities?
Start by identifying the shared business objective and the assumptions behind each position. Separate facts, risks and preferences, then compare realistic options and agree who owns the decision. A useful conversation makes the tradeoff explicit; it does not require either person to pretend the cost or uncertainty has disappeared. Read the full answer