or, a communication problem presents itself as an intellectual problem.
Here’s something I’ve noticed playing out in teams: A product person proposes an idea. Someone else responds, “I think we need to think from first principles.” The room nods. The conversation moves on. And somehow nobody is entirely sure what just happened.
At first glance, this seems like a rigorous move. First-principles thinking has become shorthand for deeper thinking, questioning assumptions, and getting back to fundamentals. Most people encounter the phrase as a thinking tool. Break the problem down. Strip away assumptions. Identify constraints. Rebuild from the ground up. Those are all useful.
What I’ve become interested in over time is what happens when that phrase enters a group conversation.
The Communication Problem Hidden Inside the Thinking Problem
When someone says we should think from first principles, they’re rarely just describing a method. They’re also making a move in the conversation. They’re suggesting that the current discussion is operating from assumptions that should be challenged, and that a more fundamental way of looking at the problem exists. Sometimes that’s exactly what’s needed.
The difficulty is that the phrase often arrives without the reasoning attached to it:
- the principle isn’t visible,
- the assumptions being challenged aren’t visible
- the constraint that’s supposedly fundamental isn’t visible.
Everyone understands that something important has been implied, but not everyone understands what that thing is. What sounds like an intellectual disagreement can quickly become a communication problem.
Why The Phrase Often Feels Unsatisfying
I’ve noticed that people reach for “first principles” for three reasons especially:
- they have a model
- they don’t have a model
- they’re performing the phrase instead of doing the work
Sometimes they’ve already done the work. They’ve identified a constraint they believe the group is overlooking and are trying to redirect attention toward it. Maybe they’re thinking about customer behavior, economics, organizational incentives, or a technical limitation that changes how the problem should be approached. In those situations, the phrase is acting as shorthand for a model that already exists.
Other times, the phrase is less of a conclusion and more of a request. Something about the current reasoning feels wrong, but the person hasn’t yet figured out exactly why. They’re not pointing toward a finished model. They’re inviting the group to help build one.
And occasionally the phrase becomes a substitute for reasoning rather than an invitation for it. The language signals rigor, but the underlying logic never becomes visible enough for anyone else to examine. The conversation sounds sophisticated while becoming harder to challenge.
The hard part is that all three situations can sound remarkably similar in the moment.
I have heard people label phrases like this thought-terminating clichés. I think that’s only really true in that third case, because a thought-terminating cliché shuts down inquiry and replaces thinking with a slogan. The distinction isn’t whether the principles are named immediately; it’s whether the underlying model ever becomes visible.
“Think from first principles” mainly becomes frustrating when it replaces reasoning; it doesn’t when it invites reasoning, and that’s the step I think often gets skipped.
And since we’re talking about this phrase in conversation, the value of first-principles thinking is more than identifying foundational assumptions: it’s making those assumptions available for other people to inspect, challenge, refine, or build upon. Is the speaker creating ambiguity or shared understanding?
Why This Shows Up So Often In Design
Is design full of thought-terminating clichés? Design organizations are full of language like this:
Customer-centric.
Strategic.
Innovative.
User-first.
Data-driven.
Systems thinking.
None of these terms are inherently problematic. Most of them describe useful ideas.
The challenge is that they often create the appearance of agreement before agreement actually exists. That leads to conflicts that appear on the surface to to be about solutions, when they’re really about the underlying assumptions that remained invisible long enough to become expensive. I’ve sat in workshops where everyone enthusiastically aligned around being customer-centric while carrying entirely different ideas about what customers needed. I’ve seen teams spend weeks debating execution when the real disagreement was hidden inside competing definitions of what good looks like. Those conflicts didn’t emerge immediately because the language was broad enough to accommodate multiple interpretations.
Better Habits for Principled Thinking
When someone says, “Let’s think from first principles,” I’ve found it useful to treat that statement as the beginning of the conversation rather than the conclusion — less because the phrase is wrong, more because it’s incomplete.
The most useful follow-up questions tend to be simple, and turn the abstract statement into something people can actually work with:
- What assumption are we challenging?
- What constraint feels fundamental?
- What would have to be true for this approach to work?
- What principle are we anchoring on?
Sometimes they reveal a strong model that deserves attention. Sometimes they help someone clarify a half-formed idea. Sometimes they expose reasoning that doesn’t hold up particularly well. All three outcomes are useful.
In Practice
A surprising amount of design work involves making reasoning visible. Researchers translate observations into insights. Stakeholders translate concerns into priorities. Teams work backwards from business goals, customer needs, technical constraints, and organizational realities. Much of the job is helping people understand not just what someone believes, but why they believe it. That’s one reason phrases like “think from first principles” can be so frustrating: they often point toward something important, then stop one step short of making that thing visible to everyone else.
The next time someone says it in a meeting, resist the urge to treat it as a conclusion. Treat it as the beginning. Ask those follow-up questions. If they questions make the reasoning clearer, the phrase is doing useful work. If the reasoning never becomes more visible, you’ve learned something useful as well.
Most disagreements aren’t caused by different conclusions. They emerge when people are operating from different assumptions without realizing it. We can’t and shouldn’t eliminate all abstractions. But we can make our shared reasoning inspectable enough that everyone can evaluate the same thing
Coming soon: Part 2: “What conversation are we having?”
Leave a Reply