Curiosity is a form of urgency.
It gives us a reason to move before we're forced to. It's easy to keep digging when something is obviously broken. It's harder when everything seems fine.
That's usually where we stop.
But "everything seems fine" isn't a very interesting place for a story to end. There's often more lurking beneath the surface for the people willing to ask one more question:
- What if there's a deeper problem to solve?
- What if I'm not actually blocked?
- What if there's another alternative?
- What if "good enough" is hiding something better?
The difference isn't necessarily working harder. It's being curious enough to keep pulling the thread.
When 'Good Enough' Becomes the End of the Story
In engineering, we spend a lot of time solving problems. We investigate failures, remove blockers, improve processes, and make decisions with incomplete information.
But there's an important distinction between solving the problem in front of us and understanding whether it's the right problem to solve.
A system might be working exactly as designed, but that doesn't mean it's serving its users well. A team might be consistently delivering work, but that doesn't mean they're working on the most valuable things. A process might have existed for years without anyone remembering why it was created in the first place.
None of these situations necessarily creates urgency. There's no incident to resolve, deadline to meet, or obvious failure demanding attention.
And that's precisely why they're easy to overlook.
We tend to treat urgency as something imposed on us by circumstances. Something breaks, someone complains, or a deadline approaches, and suddenly we have a reason to act.
Curiosity works in the opposite direction. It creates a reason to investigate before the consequences demand it.
Not every question needs to become a project, and not every working system needs to be reinvented. The point isn't to challenge everything indiscriminately. It's to recognize that the absence of an obvious problem isn't proof that there's nothing left to discover.
The Stories We Don't Tell
Stories are full of people who don't pull that thread.
Which brings me, naturally, to Bilbo Baggins.
Bilbo had a mysterious magic ring for 60 years.
Sixty years!
And for most of that time, it was just a particularly useful magic ring. Imagine being a little more curious about that.
Where did this thing come from? Why does it make me invisible? Why am I getting weirdly attached to it? Is it perhaps concerning that I won it from a cave-dwelling former hobbit who called it his "precious"?
There's a version of The Lord of the Rings where someone starts asking those questions a little earlier.
It would be a much worse trilogy. But probably a much better outcome for Middle-earth.
Of course, Bilbo wasn't entirely oblivious, and Gandalf had his suspicions. The point isn't that nobody ever questioned the Ring. It's how easily something extraordinary can become ordinary when we live with it long enough.
We accept things because they've always been that way. The longer they remain familiar, the less likely we are to question them.
Until something happens that makes ignoring them impossible.
That's a wonderful way to create conflict in a story. It's a considerably less appealing way to run an engineering organization.
Don't Wait for the Call to Adventure
One of the things I find fascinating about storytelling is how often a character's journey begins with a disruption to their ordinary world.
Something happens that forces them to act. A problem appears, a stranger arrives, or an unexpected responsibility falls into their lap.
But what if they didn't wait?
What if they started asking questions before the world demanded answers?
There's a useful distinction here for anyone responsible for leading people or solving complex problems. We can spend our time responding to the challenges that find us, or we can develop the curiosity to discover opportunities and problems before they become unavoidable.
That doesn't require treating everything as an emergency. In fact, curiosity is often most valuable when we have enough breathing room to explore without the pressure of an immediate crisis.
Sometimes the most useful thing a leader can do is ask a question nobody else thought was worth asking.
What are we assuming is true? Why do we do it this way? What would we try if this constraint didn't exist? What happens if we follow this idea one step further?
These questions won't always produce something useful. Sometimes the answer really is that everything is fine.
But occasionally, one more question changes how we understand the entire problem.
We tend to wait for the problem to become urgent before we start questioning it.
Curiosity lets us get there first.
You don't always need to wait for the call to adventure. Sometimes you can go looking for it yourself.
Otherwise you're going to leave your poor nephew traumatized and missing a finger.