After a few years away from writing, I came back to this blog with a lot to say.
Over the last few weeks I have published a series of posts exploring the ideas I find myself thinking about most — the role of technology leadership, what creates adaptive organisations, and how the rise of AI is changing the questions we need to ask.
This post is a guide to that series.
The ideas connect, so I have ordered them in a way that builds on the previous piece. You can read them in any order, but the thread runs from the purpose of technology leadership through to the foundations that make it possible.
Where this started
The post that restarted the blog. Why I came back, what changed in my thinking over the years, and why the questions facing technology leaders today feel fundamentally different from those I was writing about when I started.
The big ideas
The role of the CTO is not to deliver technology. It is to create strategic options.
The question I find myself asking most often is not “what are we building?” but “what does this enable us to do next?” This post introduces the idea of strategic options and the equation at the centre of how I think about technology leadership:
Strategic Options = Adaptive Capacity – Operational Gravity
The future of software engineering is not a tooling problem. It is an organisational design problem.
AI is changing software development, but the organisations that benefit most will not simply be those that adopt new tools fastest. They will be those that have redesigned themselves to take advantage of them. The bottleneck is moving — and it is moving into organisational design.
The foundations
Technology excellence is not a destination. It is a discipline.
Engineering excellence is not about perfection or speed. It is about creating technology foundations that allow an organisation to keep evolving. Every technical decision either increases or decreases future options.
Platform engineering is not about platforms. It is about leverage.
The highest leverage thing a technology organisation can do is reduce the friction that stops teams doing their best work. Platform engineering, done well, is not a technology capability. It is an organisational capability.
Moving fast requires more than speed.
Quality and speed are not in tension. Quality is what creates sustainable speed. When teams move quickly without strong foundations, they accumulate operational gravity that makes every future change harder.
The people and culture
Technical skills make engineers effective. Core skills make them impactful.
The engineers who create the most impact are not always the most technically gifted. They are the ones who combine technical depth with curiosity, empathy, judgement, and the ability to understand the problem they are solving.
Agile was never about the ceremonies. It was about building adaptive organisations.
Many organisations adopt the practices without adopting the mindset. Stand-ups, backlogs, and retrospectives are not the point. The point is creating organisations that can learn, adapt, and respond to change.
Diversity is not a metric. It is a source of organisational strength.
Diverse teams are not simply a representation goal. They are one of the strongest capabilities an organisation can develop. Different perspectives create different questions, and often the quality of the questions determines the quality of the solution.
The thread
All of these ideas connect back to a single question:
How do we build organisations that are capable of taking advantage of the opportunities that technology creates?
The answer, I believe, lies not in the tools we adopt, but in the foundations we build — the cultures we create, the practices we sustain, and the organisational designs that allow people and technology to work together effectively.
There is more to come.