That belief has shaped how I approach technology and problem-solving. I’m less interested in adding systems simply because they’re new or impressive. What interests me is understanding where work becomes unnecessarily difficult—and finding a practical way to make it simpler.
Most technology problems aren’t really technology problems. They’re usually people, process or communication problems that technology can help resolve.
That’s why I begin by asking questions.
What are people trying to accomplish? Where are they losing time? What information do they repeatedly search for? Which tasks depend on one person remembering to do something? What frustrates everyone but has gradually become accepted as “just how it works”?
The answers often reveal opportunities that aren’t visible from a technical specification alone.
Sometimes the solution is a new application. Sometimes it’s an automation connecting two existing systems. It might be a dashboard that turns scattered information into something useful or a small change to a workflow that removes hours of repetitive work.
And sometimes the best answer is to leave the technology alone.
I’ve spent more than two decades working across enterprise IT, digital transformation, automation and product development. One lesson has remained consistent: complexity is easy to add and difficult to remove.
A successful solution shouldn’t require people to understand everything happening behind it. It should feel natural, dependable and almost unremarkable. People should notice that their work has become easier—not that another piece of software has arrived.
AI is opening an especially interesting chapter in this story. It allows individuals and small teams to explore ideas, build prototypes and deliver useful systems at a speed that previously required significantly larger resources.
But AI doesn’t replace judgment. Producing something quickly is not the same as producing the right thing. You still need to understand the problem, question assumptions and make decisions about what should—and shouldn’t—be built.
My approach is therefore straightforward: listen carefully, understand the real problem and use the simplest technology capable of solving it well.
The best technology doesn’t need to demand attention.
It quietly makes things better.