Aristotle gets credit for first principles thinking, but the concept has never been more relevant than it is right now. As we shift to building software with AI tools, this is one of the most important mental models you can carry into every client engagement.
The Core Idea
First principles thinking is the practice of removing assumptions to get down to the fundamental truth of a problem. Instead of asking, “How has this been solved before?” you ask, “What are we actually trying to solve?”
It’s easy to say, but harder to do in practice. We are wired to pattern match. We see a situation that looks like something we’ve encountered before, and we reach for the solution that worked then. This is an efficient way to make decisions but doesn’t always lead to the best products.
What We Hear from Clients
When clients come to us, they rarely say, “Here’s the problem I’m facing. Help me figure out the best way to solve it.” More often, they say, “We need feature X.” Sometimes it’s “We need a dashboard.” Sometimes it’s “We need an AI chatbot.”
This isn’t a criticism. It’s human nature. They’re being proactive. They’ve done their homework, talked to their teams, and arrived at what seems like a logical answer. The solution they’re proposing often does address a real pain point but there are usually several ways to address those pain points.
As consultants, it’s our job to ask why. Not in an interrogative way, but in a genuinely curious one. Why do users need that dashboard? What decision are they trying to make with it? What’s the cost of making that decision slowly, or incorrectly? When you start pulling on those threads, you often find that the problem is different than the proposed solution suggested.
That’s first principles thinking in action. You’re not dismissing what the client brought to the table. You’re just making sure you understand the actual foundation before you start building.
What Happens When We Skip It
If we take feature requests at face value and start building, we can end up delivering exactly what was asked for and still miss the mark entirely. The product works as specified but users don’t adopt it. The client is frustrated and nobody wins.
This happens more than people want to admit. A team can work for months, deliver the scope within the budget and still produce something that doesn’t move the needle for end users. The specification was right. The problem definition was wrong.
Why AI Makes This More Urgent
AI tools are great at helping teams move fast. The gap between “let’s try this idea” and “here’s a working prototype” has shrunk dramatically. That’s exciting. But speed is neutral. It can accelerate you toward the right solution just as easily as it can accelerate you toward the wrong one.
There’s a real temptation, especially with AI in the workflow, to conflate velocity with progress. A client asks for an AI-powered feature. The team spins it up quickly. It looks impressive in a demo and the momentum builds. Then we stop asking the important question; ‘are we building the right things for our users?’
The faster we can build, the more important it becomes to make sure we’re pointed in the right direction before we start moving.
Moving Up the Value Chain
There’s another dimension to this worth naming. As AI tools take on more of the execution work like writing code, the most valuable thing a consultant can offer is increasingly strategic. We need to continue to differentiate by knowing which features are worth building.
That’s the value of first principles thinking. It’s not just a useful habit for discovery meetings. It’s the foundation of what good product consulting looks like as the role continues to evolve.
Ask why. Push past the proposed solution. Find the actual problem. Then use every tool at your disposal to solve it well.