This is the transcript of my keynote address at TechiesHaven’s TCDP 2.0 in Liverpool, on 14 November, 2026:
Good morning, everyone. Let me start by sharing a personal story some of you might find familiar.
There is something rather peculiar about moving house in the United Kingdom. We live in a country where you can transfer money across continents in seconds, order almost anything to your doorstep, and speak to someone on the other side of the world as though they were sitting across from you.
But try moving from one house to another, and you'll discover that modern civilization still expects you to remember a surprising number of things. You have to notify your council, contact your energy supplier, arrange your broadband, redirect your post, update your driving licence, and somehow remember the dozen other things you didn't realise you needed to do until it was too late.
I know this because I recently moved house myself. And somewhere in the middle of that experience, I began wondering why there wasn't a simpler way to navigate the entire process.
So I started building one.
It's a small digital product called Move Simple, which helps people plan and manage their move, with guidance tailored to their circumstances. Now, the interesting thing about this story isn't the product itself. It's how I was able to build it.
I'm not a software engineer by profession. My work has largely been in product management, design and the rather peculiar discipline of using language to make complex digital experiences easier for people to understand.
But with the help of AI and modern development tools, I could take an idea, describe what I wanted to accomplish, and begin turning it into working software.There was plenty of trial and error. There still is. And yet, the fact that I could do this at all struck me as rather extraordinary.
Five or ten years ago, the distance between having an idea and building a functioning digital product was considerably greater for someone with my particular background. Today, that distance is shrinking.
Which brings me to a question that I think everyone in this room should be thinking about.
If technology is making it easier for more people to create things, what exactly will make us valuable?
It's a particularly interesting question for those of you hoping to begin careers in technology. And I suspect the answer requires us to think about technology a little differently.
A brief history of making things better
Peter Thiel, in his book Zero to One, offers a definition of technology that I find quite useful.
Technology, he argues, is any new and better way of doing things. It's a wonderfully expansive definition. It means that technology isn't limited to computers, artificial intelligence, or the devices we carry around in our pockets. It is, fundamentally, about finding better ways of accomplishing things. And once you begin looking at the world through that lens, you start noticing something interesting about the history of human progress.
I’ll now share three brief stories that encapsulate this point.
1. Consider Johannes Gutenberg.
In the middle of the fifteenth century, books in Europe were expensive and difficult to reproduce. Gutenberg, who had experience working with metals, developed a printing system that made the reproduction of written material substantially more efficient.
He wasn't the first person in history to think of printing. Techniques for printing had existed in East Asia long before his time. But Gutenberg brought together materials, mechanical processes and existing ideas in a way that helped transform the production of books in Europe. And the consequences would extend far beyond the printing workshop. Knowledge could circulate more widely. Ideas could travel further. Religious and scientific arguments could be reproduced, challenged and debated on a scale previously difficult to imagine.
What interests me about Gutenberg is the combination of practical knowledge and imagination. He understood something about the materials he worked with. But he also recognised what those materials could make possible.
Now, travel forward a few centuries.
2. Florence Nightingale is working with an altogether different problem.
British soldiers are dying in large numbers during the Crimean War. Nightingale begins studying the evidence and finds that disease and preventable illness account for an extraordinary proportion of those deaths.
But identifying the problem is only part of her achievement. She also understands that evidence must be communicated in a form that people can grasp. And so she uses statistics and visual diagrams to make the scale of preventable deaths apparent to people who could influence policy.
I've always found that aspect of her work fascinating. Here was someone using numbers, visual communication and an understanding of human behaviour to help change how institutions responded to suffering. Today, we might describe parts of that work as data analytics, information design or evidence-based policymaking. Nightingale didn't need any of those contemporary job titles to do it. She had a problem she was determined to understand, and she brought her knowledge to bear upon it.
3. Then there's Tim Berners-Lee.
In 1989, while working at CERN, he was trying to solve a problem that many organisations still struggle with today: how do you make information easier to share between people working with different computers and systems? His work became the World Wide Web. But there is another detail in this story that deserves attention.
In 1993, CERN made the underlying Web software freely available.That decision meant that others could adopt it, improve upon it, and build things that Berners-Lee himself could scarcely have anticipated. Without his work, much of our modern digital economy — social media, online shopping, internet banking, etc — would almost certainly not exist.
Think about these three people for a moment. A metalworker. A nurse. A computer scientist. Different centuries, different disciplines, different problems. It would be difficult to imagine a conventional career framework that adequately connects all three. And yet, their stories share an important feature. Each encountered a limitation in the world as they knew it. Each drew upon existing knowledge and tools to imagine an alternative. And each contributed to changing what other people could do.
I think there's something instructive in that. Perhaps we have become so accustomed to thinking about technology in terms of job titles and technical competencies that we occasionally lose sight of its purpose.
Technology has always been about extending human possibility. The tools are important, certainly. But the tools are not the whole story.
The peculiar opportunity before us
I studied physics and engineering. Since then, my career has taken me through oil and gas, financial technology, energy, software, and now business travel. I've worked in product management, content design and other disciplines that sit somewhere between technology, business and human behaviour.
I couldn't have predicted that trajectory when I began. In retrospect, however, there's a thread running through it. I've always been interested in understanding how things work, particularly things that appear unnecessarily complicated, and finding ways to make them more intelligible. And I suspect that curiosity has been more useful to me than any single tool I've learnt.
This is partly why I find the current moment in artificial intelligence so exciting.The tools available to us are beginning to remove some of the practical constraints that once separated an idea from its execution. You no longer have to possess every technical skill required to begin exploring an idea. You can ask questions, generate prototypes, experiment, make mistakes, and try again.
That doesn't mean everyone suddenly has the same opportunities. Access to education, computing resources, capital and reliable infrastructure remains profoundly unequal. Nor does it mean technical expertise has become unnecessary. Anyone who has spent enough time working with AI will know that these systems can produce answers that are impressively presented and completely wrong. They can write software with hidden faults. They can invent facts. They can produce beautiful interfaces that are practically unusable. And they can do all of this with remarkable confidence.
So the ability to produce something is not, by itself, evidence that you know what you're doing. In fact, I would argue that as producing things becomes easier, knowing what is worth producing becomes more important.
Which brings me to something I've been reflecting on lately.
Let there be
There is a familiar passage in the first chapter of Genesis. The world is described as being without form. And God begins to create.
"Let there be light."
And there is light.
It's a remarkable account, particularly the relationship between intention and creation. Something is conceived, spoken, and brought into existence. I find myself returning to that passage when I consider what generative AI now makes possible.
Of course, there is an enormous distinction between divine creation and what we do with machines. We are working with existing knowledge, systems and materials. The comparison is an analogy, not an equivalence. But there is something fascinating about the fact that human language itself has become such a powerful interface for making things. We describe what we want, and increasingly sophisticated systems help us produce it. Not perfectly. Not always reliably. But often with astonishing results.
And yet, the part of Genesis that most interests me comes after the act of creation. It is the recurring observation:
"And God saw that it was good."
I've been thinking about the significance of those words. There is the intention to create. There is the creation itself. And then there is an assessment. Is it good?
It's that final question I want us to consider.
Because in the enthusiasm surrounding artificial intelligence, we are spending an enormous amount of time thinking about what machines can produce. We spend rather less time considering how we will determine whether those things are any good. And by good, I don't simply mean aesthetically pleasing or technically impressive. I mean useful. Accurate. Responsible. Appropriate to the problem. Good for the people who must live with the consequences.
A machine might generate a perfectly convincing answer to the wrong question. It might produce software that works beautifully in a demonstration but fails the moment a real person tries to use it. And it might help us build something that, on closer examination, nobody particularly needs. Someone still has to exercise judgement. Someone has to ask whether the problem is worth solving, whether the solution is appropriate, and whether what has been produced actually improves anything.
That responsibility remains ours.
Where do you fit in?
So, what does this mean for someone standing at the beginning of a technology career? I would suggest three things.
1. The first is to take your curiosity seriously.
Don't limit your interest to the latest tools or the technical skills currently attracting the highest salaries. Be curious about the world. Why does a particular service work so poorly? Why is a certain process unnecessarily expensive? Why do people struggle to understand something that experts consider straightforward? Learn to notice problems. And when something interests you, resist the temptation to stop at the first explanation.
2. The second is to develop a sound understanding of your chosen discipline.
If you want to be a software engineer, study programming. If you're interested in design, study design. If you want to work with data, understand statistics, evidence and the ways numbers can mislead. Learn the fundamentals.
There's a temptation, particularly now, to confuse having access to knowledge with actually possessing it. They’re not the same thing. A person who understands the underlying principles of a discipline is better equipped to ask useful questions, recognise errors and make informed decisions. AI can accelerate your learning. It shouldn't replace the learning itself.
3. And finally, cultivate judgement and taste.
I use the word taste deliberately.
We normally associate it with art, literature, music or design. But taste is also the ability to recognise quality, to perceive when something is missing, and to know when an apparently impressive solution isn't quite right. It develops through exposure to good work, through practice, through failure, and through learning to distinguish your personal preferences from what a situation actually requires.
Judgement also requires humility.
You must be willing to test your assumptions, listen to people who know more than you do, and discover that, sometimes, something you worked hard to create isn't particularly useful. Those experiences are not distractions from becoming proficient. They're part of how proficiency is developed. And I suspect that in an age when machines can generate enormous quantities of material, people who have developed the ability to recognise and produce work of genuine value will remain indispensable.
One small invitation
Let me leave you with a practical suggestion.
Sometime in the next week, find a problem worth your attention. Not necessarily a grand problem. It doesn't have to involve curing a disease or inventing the next great social network. It might be something frustrating in your workplace. Something your parents struggle with. A process in your community that wastes everyone's time.
Try to understand it properly. Talk to the people experiencing it. Then use whatever tools you have available to explore a solution. Build a small version. Show it to somebody. See what happens. You may discover that your idea doesn't work. That's useful information too. Because the habit you're developing is not merely the ability to operate technology.
You're learning to observe, to reason, to experiment, and to exercise judgement.mAnd you can begin doing that long before anyone gives you a job in technology.
Closing
I began by asking what will make us valuable in a world where creating things is becoming easier. I don't think there's a single answer. The technology landscape will continue to change. Some of the skills we prize today will become less scarce. New disciplines will emerge, and familiar professions will change in ways we cannot yet fully anticipate.
But I think we can say something about the qualities that will help us navigate those changes.
1. Curiosity.
2. An understanding of how things work.
3. The ability to recognise meaningful problems.
4. And the judgement to decide what should be done about them.
When I think about Gutenberg, Nightingale and Berners-Lee, I'm reminded that technological progress has never belonged exclusively to people who knew how to operate the most sophisticated tools of their age. It has also belonged to people who could see possibilities that others had overlooked. People who were willing to learn enough to make those possibilities real.
So, as you consider your place in technology, don't think only about the role you hope to occupy or the tools you hope to master. Think about the problems you might one day help solve. There are plenty of them. And for perhaps the first time in our history, the distance between imagining a solution and attempting to build one is becoming remarkably short for a growing number of people.
That is an extraordinary opportunity. But it is also a responsibility. Because the question before us is no longer simply what we have the power to create. It is whether we have developed the wisdom to recognise what is worth creating. And whether, having created it, we can step back, examine our work, and say, with some confidence:
"It is good."
Thank you.