For a long time, I imagined inventions as moments of sudden brilliance.
Someone thinks deeply, connects a few ideas, and suddenly has a breakthrough.
The more I learn and build, the less I think innovation works that way.
I’m starting to believe that many useful ideas come from interacting with a problem repeatedly and deeply enough to see things that were not obvious at first.
Innovation Starts With Curiosity
A problem usually begins with a simple question:
Why is this done this way?
Then another question appears.
Then another.
You read. You experiment. You make mistakes. You discover something new and go back to the original problem with a different perspective.
Over time, the problem changes in your mind.
You understand it differently.
And that is where new ideas can begin.
Building Changes the Way You Think
I have experienced this while building my AI Underwriter.
I did not start with a complete system or a perfect blueprint.
The project evolved as I interacted with the problem.
An underwriting question led me to explore alternative data. That led to telematics and rent-payment behaviour. Explainability raised questions about how model decisions should be communicated. Then came questions around audit trails, model governance, and the role of local AI.
I learned that building something can expose questions that reading alone would never reveal.
That has become one of the lessons I value most from the project.
Innovation Often Happens Between Fields
Another thing I have noticed is that innovation does not always come from one subject.
Sometimes it comes from combining things that already exist.
In my case, actuarial science gives me the risk perspective. Data science gives me ways to investigate and evaluate data. Programming allows me to turn ideas into working systems. AI and explainability introduce new ways of interacting with those systems.
The interesting part is what happens at the intersection.
That is where a familiar problem can start looking different.
The Sacrifice Is Mostly Attention
Innovation also requires something people do not always talk about: attention.
Learning a difficult concept takes time.
Debugging takes time.
Failed experiments take time.
Building and rebuilding takes time.
You have to spend more time with a problem than you normally would if you want to understand it deeply.
That does not mean sacrificing everything else in life. It means being willing to give a problem enough attention for your understanding to move beyond the surface.
For me, that has been one of the biggest lessons from building.
What I Have Learned
I used to think the important part was having a great idea.
Now I think the more important question is:
How deeply are you interacting with the problem?
The more you learn, build, test, question, and reflect, the more likely you are to notice connections that were invisible at the beginning.
My AI Underwriter is still unfinished, but that is part of the point.
Every new problem has taught me something that has changed the system.
And every change to the system has changed how I understand the problem.
The Lesson I'm Taking Forward
Maybe invention is not always a sudden moment of genius.
Maybe sometimes it is simply the result of curiosity sustained long enough to become understanding.
You start with a problem.
You keep interacting with it.
You learn something.
You build.
You fail.
You improve.
And somewhere along the way, you may create something that did not exist when you started.
That is the idea of innovation I am beginning to believe in — and it is one I am learning through building my own systems.