• Thinking
  • first principles
  • feynman
  • teams

The Power of Stupid Questions

A junior's "why are we building this?" saved a week of work. Feynman, first principles, and being willing to look stupid for five minutes.

Published: ·4 min read·First on Substack

YKYasir Khalid

Last week, in an internal team discussion about designing production downtime alerts - a junior member of my team (who has been around in the company slightly longer than me, but fresh out of university) asked: “Why are we building this alert again?”

As I started explaining the rationale from scratch, I realised our approach was fundamentally flawed. We were solving for a pattern we’d seen at other banks, not for what our actual SREs needed. That “stupid” question saved me from building the wrong thing for a week - which added zero to none value to my production support team.

The Feynman Method

Richard Feynman, one of the greatest physicists of the 20th century, built his entire career on asking stupid questions. In his autobiography, he admits that people would think he was slow at first because he’d ask things like “Is a cathode plus or minus?” But later, when someone was deep in equations, Feynman would spot the error that everyone else missed. His secret? He never pretended to understand something he didn’t. He always went back to basics.

There’s a famous story where a Caltech faculty member asked Feynman to explain why spin one-half particles obey Fermi-Dirac statistics. Feynman said, “I’ll prepare a freshman lecture on it.” A few days later, he came back and said, “I couldn’t do it. I couldn’t reduce it to the freshman level. That means we really don’t understand it.”

Think about that. A Nobel Prize winner admitting he doesn’t understand something because he can’t explain it simply. That’s the power of stupid questions. They expose what we think we know but actually don’t.

First Principles vs Pattern Matching

When Elon Musk wanted to start SpaceX in 2002, rockets cost $65 million. The “smart” answer would have been: rockets are expensive, that’s just how it is, either find the money or give up. But Musk asked what felt like a stupid question: “What is a rocket actually made of?”

He broke it down. Aerospace-grade aluminum, titanium, copper, carbon fiber. Then he asked an even stupider question: “What’s the value of these materials on the commodity market?” Turns out, about 2% of the rocket’s price. The other 98% was layers of contractors, markups, and accepted inefficiencies that everyone had stopped questioning.

The other 98% was layers everyone had stopped questioning.

Within a few years, SpaceX cut launch costs by 10x. Not by being smarter than NASA engineers. By asking questions that felt too basic to ask.

Here’s the thing about stupid questions. They’re only stupid when you already know the answer. But most of the time, what looks like a stupid question is actually someone refusing to accept a pattern second hand.

The Cost of Looking Stupid

There’s a reason people don’t ask stupid questions. It’s scary. In his book “Think Like a Rocket Scientist,” Ozan Varol talks about how we have to abandon what he calls “reasoning by analogy.” When you’ve built up credibility, when you’re the senior person in the room, asking a basic question feels like you’re gambling with your reputation.

But here’s what I’ve learned: the people who do great work are the ones willing to look stupid for five minutes to avoid being wrong for five months. They understand that intellectual confidence isn’t about having all the answers. It’s about having the courage to question all the questions.

When I Built Sportscanner

When I started building sportscanner.co.uk, I kept asking myself what felt like stupid questions. Why do users need to visit 10 different websites to book a badminton court in London? Why isn’t there a unified search?

The “smart” answer was that this problem probably doesn’t exist, or someone would have solved it already. Big companies like Google or booking platforms would have tackled it. The market must be too small. Users must be fine with the current fragmented experience.

But I kept asking the stupid question: “Why not?” I scraped 10,000+ URLs, built a unified interface, and now 400+ players across London have registered to use it - purely via word of mouth and some reddit spam posting.

The Difference Between Smart People and People Who Do Smart Things

The difference between smart people and people who do smart things is this: smart people question every pattern until they hit bedrock. They’re willing to look stupid. They ask “why” like a five-year-old until the answers start falling apart.

If you’re not asking stupid questions, you’re probably just stacking borrowed patterns on top of each other, hoping they hold. You’re building faster horses when what you need is a car.

Your License to Look Stupid

So here’s my challenge to you. Next time you’re in a meeting and everyone’s nodding along, ask the stupid question. Question the underlying assumptions. Go to the root.

Don’t accept “that’s how we’ve always done it” as an answer. Don’t accept “that’s what big tech companies do” as an answer. Don’t accept “everyone knows that” as an answer.

The stupid questions are the ones that make you think from first principles. They’re the ones that strip away the layers of accumulated assumptions and force you to confront what you’re actually trying to solve.

Your ability to ask stupid questions is directly proportional to how deeply you understand what you’re building.

What’s the last stupid question that changed your approach to a problem?