Designing for Curiosity

This is the Google story everyone knows, but doesn't learn from.

Google gave its engineers 20% of their time to work on whatever interested them. No client requests. No executive assignments. No mandate to improve an existing product. Just time set aside for exploration.

It’s often remembered as a perk. A luxury. Something only a fast-growing tech company could afford to do. Well, that framing misses the point. 

The 20% policy wasn’t about generosity. It was about creating room for curiosity inside a system that usually eliminates it. Because curiosity doesn’t vanish overnight. It gets trained out of us.

As children, we ask questions constantly. Not because we’re unfocused, but because nothing feels fixed yet. Why does this work the way it does? What happens if you change it? What’s really going on here?

Then school teaches us to value answers over questions. Work reinforces it. Execution becomes safer than exploration. Efficiency becomes more important than wondering if the system itself is flawed. By the time we enter the workforce, most of us have learned to stop asking.

Google pushed in the opposite direction.

One day a week, engineers were encouraged to follow the questions that wouldn’t leave them alone. Problems they noticed but weren’t asked to solve. Assumptions everyone accepted without discussion. No approval process. No guaranteed outcome.

That’s where the real story begins.

Paul Buchheit noticed something odd about email. Everyone treated storage as scarce, forcing people to constantly delete messages just to make room for new ones. It wasn’t questioned; it was accepted. He wondered what would happen if that assumption disappeared. During his 20% time, he built Gmail.

Around the same time, Lars and Jens Rasmussen were frustrated with online maps. They technically worked, but they didn’t behave like maps. Each click required waiting. Each movement felt disconnected. They asked a simple question: what if an online map worked the way people naturally explore space? Their 20% project became Google Maps.

Neither of these products came from a roadmap. They came from curiosity applied to things everyone else treated as “just the way it is.” That’s why this story matters. Google didn’t win because it gave people free time. It won because it made curiosity acceptable, visible, and protected.

And that’s the thread we’re about to follow.

Defining Curiosity

Curiosity is the desire to learn, explore, or understand something new.

Not in the abstract. Not someday. Right now.

It’s the impulse to question assumptions, examine how things really work, and explore different perspectives before jumping to conclusions. It shows up in questions like what if? and why not?; especially when the current approach seems “good enough.”

Curiosity isn’t about being nosy. It’s about wanting to understand the why behind the data. It’s about being open to new ideas and experiences, even when they challenge what we believe to be true.

Most importantly, curiosity requires a willingness to be wrong.

Because being wrong isn’t failure. It’s information. And in B2B, where long sales cycles and complex decisions dominate, that information is often the difference between relevance and irrelevance.

So the real question becomes:Why should companies that aren’t Google care about this?

Why should a manufacturing company, a service business, a healthcare organization, or a professional firm adopt practices that came out of Silicon Valley?

Why should teams already under pressure to deliver take time to explore, experiment, or question how things are done?

And maybe the most honest question of all:What happens if they don’t?

Curiosity isn’t a tech-company advantage. It’s a business advantage. And the benefits show up whether you’re writing code or not. 

The Five Ways Curiosity Pays Off

1. Curiosity helps you notice the real problem

Most teams are very good at fixing things quickly. The risk is fixing the wrong thing with great efficiency. Curiosity slows the moment just enough to ask what’s actually causing the issue.

Is the problem really demand, or is it confusion? Is it performance, or is it trust? What would change if we stopped treating symptoms and spent more time understanding causes?

2. Curiosity deepens understanding of the people you serve

It’s easy to rely on reports, personas, and assumptions. Curiosity pushes you to listen more closely. To notice where people hesitate, what they ask before they buy, and what frustrates them after they say yes.

What almost stopped them? What surprised them? What problem are they really hiring you to solve, even if they never say it out loud?

3. Curiosity makes innovation safer, not riskier

Big breakthroughs rarely start big. They start with someone asking a small question that everyone else ignored. Curiosity doesn’t demand bold bets right away. It encourages small experiments and thoughtful tests.

What would we learn if we tried this with one client? What assumption are we making because it feels easier than checking it? What’s the smallest version of this idea that could teach us something useful?

4. Curiosity improves decisions before they harden

Many decisions fail not because they were reckless, but because they were rushed. Curiosity invites more context, more perspectives, and better framing before a choice becomes policy.

Who hasn’t weighed in yet? What information are we missing? If this turns out to be wrong, what did we overlook at the start?

5. Curiosity keeps organizations adaptable without panic

Change feels threatening when it arrives suddenly. Curious organizations notice shifts earlier because they’re already paying attention. They’re asking what’s changing, what’s emerging, and what no longer fits.

What are we assuming will stay the same? What signals are we ignoring because they don’t match our current model? If we were starting today, what would we do differently?

Designing for Curiosity

Curiosity doesn’t slow progress. It sharpens it. It keeps teams from mistaking motion for momentum and certainty for clarity. It creates space for better questions before bad answers become habits.

And this is where most companies get uncomfortable.

Because curiosity doesn’t fit neatly into dashboards or quarterly plans. You can’t spreadsheet it. You can’t mandate it with a slogan on the wall. You have to design for it.

You have to ask:

Where are we discouraging questions because they feel inconvenient?Which assumptions are we protecting simply because they’re familiar?What would break if we allowed people to explore before we demanded certainty?

Especially in B2B, where long sales cycles, legacy processes, and “that’s how it’s always been done” thinking dominate, curiosity is often the first thing sacrificed in the name of efficiency.

That’s a mistake.

The most effective organizations don’t move faster because they rush. They move faster because they are better. They spend time understanding the real problem before committing resources to solving the wrong one. They create environments where people are allowed, even expected, to ask uncomfortable questions.

Not endlessly. Not recklessly. But intentionally.

Because curiosity isn’t about chasing shiny ideas. It’s about learning faster than your competitors. It’s about noticing when customer needs shift before churn spikes. It’s about questioning your positioning before the market stops listening. It’s about experimenting in small, thoughtful ways instead of betting everything on assumptions you never tested.

Most companies say they want innovation. Very few build systems that allow curiosity to survive long enough to produce it.

That’s why the Google story still matters.

Not because you should copy their policies. But because you should copy their mindset.

Allow me to say it again: curiosity isn’t a tech-company advantage. It’s a leadership choice. And the organizations that last aren’t the ones with the most confidence. They’re the ones that never stop being curious.

If this sparked questions about how curiosity shows up in your strategy, your messaging, or how your market actually sees you, that’s a good sign. It means you’re paying attention.

That’s exactly the kind of conversation we have every day at Craft. If you’re ready to explore what curiosity could unlock for your business, let’s talk.

Because the most important work rarely starts with a solution. It starts with a better question.