Skip to main content

Childhood Truths Adults Rationalize Away

· 3 min read
Calvin Cheng
Shape what gets built and the value it creates.

Calvin asks questions adults stop asking. Not because adults know the answers, but because we've learned to stop asking. (This is part of a series exploring Calvin and Hobbes.)

"Why should I do homework?" isn't a lazy question. It's a fundamental challenge to the system. "Why is being 'good' defined by convenience?" cuts to the heart of how we've structured society. "Why do adults say one thing and do another?" exposes the gap between stated values and actual behavior.

The Unfiltered Lens​

Children aren't naïve. They're unfiltered. Adults confuse conformity with wisdom.

I've been thinking about this in the context of product feedback. When users complain about something, they're often asking the Calvin questions: "Why do I need to do this extra step?" "Why does this work this way?" "Why can't I just do X?"

As product people, we often rationalize these questions away. We say "that's how the system works" or "that's industry standard" or "that's what the requirements say."

But what if we treated user complaints like Calvin's questions? What if we assumed they were exposing real problems, not just being difficult?

The Conformity Trap​

I've worked in organizations where questioning the status quo was seen as disruptive. Where "that's how we do things" was considered a valid answer. Where conformity was rewarded over curiosity.

But the best products, the best companies, the best teams - they question everything. They ask the Calvin questions.

When I'm building something new, I try to channel my inner Calvin. I ask: Why does this need to exist? Why does it work this way? Why can't it be simpler? Why are we optimizing for this metric instead of that one?

These aren't rhetorical questions. They're filters. They help me see when I'm rationalizing instead of reasoning.

Hobbes as the Voice of Reason​

Hobbes often provides the quiet, unsettling answer to Calvin's questions. He doesn't dismiss them. He doesn't say "that's just how it is." He engages with the question, even when the answer is uncomfortable. (I explore Hobbes as a psychological construct in more depth.)

In teams, we need Hobbes voices. People who don't just execute, but who question. Who don't just accept "that's how we do it," but who ask "why?"

The challenge is that these voices are often seen as disruptive. They slow things down. They create friction. They make people uncomfortable.

But friction isn't always bad. Sometimes it's the only thing preventing us from building the wrong thing faster.

What We Lose​

As we "grow up" professionally, we learn to accept constraints without questioning them, to optimize for process over outcomes, to rationalize away user complaints, to conform to "industry standards," to stop asking "why?" (This connects to what we lose and what we gain as we grow up, and how systems optimize for control rather than meaning.)

We call this maturity. But sometimes it's just learned helplessness.

Calvin reminds us that curiosity matters more than correctness. That asking the right questions is more valuable than having the right answers. That unfiltered truth is often more useful than polished rationalization.

The Test​

Here's a test I use: When someone asks a "dumb" question - one that challenges assumptions or exposes gaps - do I dismiss it or engage with it?

If I dismiss it, I'm probably rationalizing. If I engage with it, I'm probably learning.

Calvin never stops asking. Neither should we.