About Donovan Crewe
I’m a technology leader, consultant, and builder focused on what happens when software engineering, artificial intelligence, and organisational knowledge start working as one system.
I currently serve as Chief Technology Officer at Lumenalta, where I help shape the company’s technology strategy and the evolution of AI-native engineering across a global engineering organisation. My work sits at the intersection of technology strategy, software engineering, data, artificial intelligence, and the practical challenge of turning new technology into capabilities that organisations can actually use.
I’ve spent my career building technology and helping organisations navigate periods of significant technological change. Today, much of my focus is on a more fundamental shift: AI is changing not simply how we write software, but how engineering organisations think, learn, and operate.
AI-Native Engineering
I believe the next generation of engineering organisations will be defined by their ability to combine human expertise, AI agents, organisational knowledge, and persistent context into systems that continuously improve.
That idea has led me to develop my thinking around Engineering Intelligence: the collective capability of an engineering organisation to continuously solve problems, learn from outcomes, and improve through the combined intelligence of people, AI, and organisational knowledge.
My work explores what that means in practice.
How should engineering organisations operate when agents can perform meaningful portions of software delivery? How do we preserve context instead of repeatedly recreating it? How do we measure whether engineers are actually becoming more capable with AI? How should organisations approach evaluation, governance, architecture, and technical strategy when the underlying economics of software development are changing?
I’m particularly interested in the space between the technology and the operating model. The models matter, but the systems built around them matter more.
Building Systems, Not Just Solutions
I’m most interested in building systems that create emergent behaviour rather than simply automating individual workflows.
That philosophy influences how I approach technology strategy and product development. The goal is not simply to make one process faster. It is to create an environment where knowledge compounds, feedback loops improve outcomes, and people and machines become more effective together.
This has shaped work across AI-native delivery, modern data platforms, agentic engineering, developer tooling, organisational intelligence, and software architecture.
I also enjoy taking ideas from theory into something tangible. I’ve worked on and explored products and platforms involving AI agents, engineering intelligence, knowledge systems, developer experience, data, and automation.
Beyond the Technology
Technology is only one part of the problem.
The interesting work happens where technology meets people, organisations, economics, and culture. I’m interested in how companies should change their structures, processes, skills, and expectations as the capabilities of AI evolve.
That means I spend as much time thinking about strategy and organisational design as I do about architecture and implementation.
I write and speak about these ideas because I believe we are still early in one of the most significant changes the software industry has experienced. There is an opportunity to build engineering organisations that are fundamentally different from those of the last twenty years.
Outside of Work
Away from technology, I’m a competitive cyclist and spend a considerable amount of time riding road, gravel, and racing.
Cycling provides a useful counterbalance to technology. Progress is measurable, feedback is immediate, and there is nowhere to hide from the result.
It has also reinforced something I bring back into my professional life: meaningful performance rarely comes from a single intervention. It comes from building a system, measuring it, learning from it, and continuously improving it.
That is probably the simplest way to describe how I approach both technology and life.
Build the system. Measure what happens. Learn. Improve. Repeat.