Speed is one of the most common measures we use when we talk about technology organisations.
How quickly can we deliver?
How often can we release?
How much can we accomplish in a given period of time?
These are important questions. Organisations need the ability to respond quickly, adapt to change, and deliver value to customers.
But I think we sometimes misunderstand what creates speed.
There is a common belief that quality and speed exist in tension. That improving quality means adding more steps, more effort, or more time.
Over many years working with engineering teams, I have found the opposite.
Quality is what creates sustainable speed.
When teams move quickly without strong foundations, they often create friction that appears later.
A shortcut becomes technical debt.
A rushed decision becomes architectural complexity.
A manual process becomes a dependency.
A small problem becomes a larger operational issue.
The immediate delivery may look faster, but the organisation slowly accumulates what I think of as operational gravity.
Over time, that gravity makes every future change harder.
The team spends more time understanding existing complexity and less time creating new value.
This is why engineering excellence matters.
Practices like automated testing, continuous delivery, good architecture, observability, and clean code are sometimes seen as slowing teams down.
But these practices are not about perfection.
They are about reducing uncertainty.
A well-designed system is easier to change.
A reliable deployment process makes releases less risky.
A clear architecture makes decisions easier.
A good engineering culture helps teams solve problems faster.
The investment in quality today creates the capacity to move faster tomorrow.
The strongest engineering organisations I have worked with are not the ones that try to eliminate all structure.
They are the ones that build the right foundations so teams can move with confidence.
They create platforms that remove unnecessary friction.
They automate repetitive work.
They make good practices the easiest path.
They give teams autonomy while ensuring that teams have the capabilities they need to make good decisions.
The result is not slower delivery.
The result is sustainable speed.
This becomes even more important as AI changes software development.
AI will accelerate parts of the development process. It will help teams generate, understand, and modify software faster.
But if the foundations are weak, AI can also accelerate complexity.
More code does not automatically create more value.
More output does not automatically create better outcomes.
The organisations that benefit most from AI will be those that combine speed with strong engineering foundations.
The goal of technology organisations should not be to move fast at any cost.
It should be to build the capability to continuously adapt.
That requires speed.
But it also requires quality.
Because quality is not the opposite of speed.
Quality is the engine that makes speed possible.