The art of connecting: when listening becomes innovation
Innovation isn't born from code. It's born from understanding the problem so deeply that the solution becomes inevitable.
It all started by listening. Not in a meeting room, not in an innovation workshop, not in a presentation with pretty slides. It started in normal conversations — sitting with the people who run the processes day to day, asking simple things: what do you do first? what takes you the longest? what part frustrates you?
Most people who want to innovate start with the technology. They look for the model, the tool, the framework of the moment. I started the other way around. I started by listening.
Active listening as a tool for innovation
There's a huge difference between hearing and listening. Hearing is waiting for your turn to speak. Listening is understanding the other person's pain so well that you can describe it better than they can. When you reach that point, the solution shows up on its own.
In internal audit, every manual process has a story behind it. Someone designed it years ago with the tools they had. Someone else inherited it and added steps. Another person half-documented it. By the time it reaches you, it's a chain of decisions no one questions because "that's how it's done".
But when you sit down with the person who runs it and actually listen, you find the cracks. The 30 minutes she spends copying data from one system to another. The hour she spends formatting a report no one reads in full. The errors she fixes manually because the system doesn't catch them.
The most powerful innovation doesn't come from inventing something new. It comes from understanding something old so deeply that you can transform it.
Build the innovation, permission comes later
When I identified the first process I could automate, I didn't ask for authorization. I didn't present a business case. I didn't form a committee. I built it.
In my free time, in hours others used for something else, I started building the solution. A script that did in 15 minutes what took 3 days manually. Same quality. Zero errors. Repeatable infinitely.
When I presented it, I wasn't asking permission to innovate. I was showing a result. And that completely changes the conversation. It's no longer "can we try something new?". It's "this already works, do we scale it?".
That's the principle that has guided me: propose the innovation or build it yourself. Permission shows up when results speak.
From a script to 80,000 hours
What started with one process evolved into something much bigger. From individual scripts we moved to AI Agents that run entire audit workflows. Systems that extract, analyze, classify, and document — freeing more than 80,000 work-hours per year.
But none of that would exist without those first conversations. Without sitting down to listen. Without understanding the "why" before the "how".
Technical skills matter. Python, machine learning, data architecture — all of that is necessary. But it's the second half. The first half, the one that actually creates value, is the capacity to connect with the people who live the problem.
Innovation is an act of empathy
It sounds contradictory. Tech innovation is imagined as something cold, logical, lab-bound. But in practice, especially inside organizations, innovation is deeply human. You need to understand frustrations, aspirations, fears of change, legitimate resistances.
Every person who tells you their process is giving you a map. If you read it well, it shows you exactly where technology can multiply their capacity without replacing their judgment. That isn't done with an algorithm. It's done by listening.
If you want to innovate in your organization, don't start by looking for tools. Start by having conversations. The best technology solves problems that someone first took the time to understand.