Why Judgment Is Becoming the Scarce Resource
AI has dramatically increased the speed at which software can be built. The pace and velocity of execution continue to rise, and that is exciting.
But faster building skips over a critical discipline in product strategy and design: determining what to build and developing confidence that it is the right thing to build. As execution becomes easier, judgment becomes more valuable.
Senior designers often refer to this judgment as sense-making, the ability to synthesize context, patterns, and behavior into clarity before anything is built. When building anything quickly becomes possible, building the wrong thing becomes exponentially more likely. That carries real business consequences, especially in creator-led companies where time, trust, and audience attention are limited resources.
While many are asking what could be built, the more important question is what problem is actually being solved. That question requires judgment.
Why Pattern Recognition Matters More Than Instinct
Founders and creators bring deep knowledge of their audience, niche, competitors, and domain. That expertise is invaluable.
Experienced product designers bring something different: a pattern library built from observing thousands of users interact with hundreds of products across industries. They know what works in fintech, what fails in SaaS, how users adopt AI features, where onboarding breaks, and where engagement stalls.
A feature request may appear obvious, but underneath it may be a deeper user need that has surfaced before in another product category. Jon Kolko describes this as abductive reasoning, inference to the best explanation by combining contextual insight with cross-domain pattern recognition.
This synthesis requires deep understanding of your specific context, knowledge of design patterns across industries, and judgment about which patterns apply and which do not. That judgment is often what companies are truly investing in.
The Strategic Questions Experienced Designers Ask
Sense-making shows up in the questions designers ask early. Experienced designers know which early decisions cascade into expensive downstream problems, so they ask questions that reveal assumptions and clarify intent.
Why is this being prioritized over alternatives? Who are the first 1,000 people who will love this? What is the user’s actual job to be done here?
These questions are not theoretical. They are pattern-based, developed from seeing what breaks, what scales, and what actually drives adoption across multiple products. Execution becomes cheaper in an AI-enabled world. Wrong decisions do not.
When Teams Cannot Articulate What They Want to Build
A recent project illustrates this clearly. The business provided training and community to customers, and the team was highly capable and deeply knowledgeable about their domain. Yet at the start of the engagement, they struggled to articulate what they actually wanted to build.
The issue was not lack of intelligence but proximity. Years of working within the limitations of existing technology had shaped their mental model of what was possible. Conversations defaulted to incremental improvements, starting from what currently existed and optimizing within existing constraints.
The team could optimize the present. They could not envision the ideal future state.
This is common among founders and creators. Processes evolve around technical limitations, and over time, how things work today becomes mistaken for how things should work. Optimization is possible. Reimagination is harder.
What Sense-Making Enables
Early design work in that project focused on separating technical constraints from actual needs. That shift allowed the team to observe patterns in how customers and instructors actually used the training and community, recognize similar patterns from other learning and community platforms, question assumptions about why certain steps existed, and distinguish between system limitations and genuine requirements.
The breakthrough came when a low-fidelity prototype demonstrated possibilities the team had not previously articulated. Not because the team lacked intelligence, but because they lacked exposure to adjacent patterns.
The domain knowledge existed internally. The cross-context pattern recognition did not. That synthesis created clarity before heavy execution began.
Why This Matters Even More Now
As building becomes easier, three shifts occur. Execution becomes accessible to more people. Poor ideas are built faster and waste more resources. The ability to decide what to build becomes more valuable than the ability to build it.
Execution is no longer the primary bottleneck. Judgment is.
Examples like Gmail or Superhuman did not emerge from raw feature aggregation. They emerged from recognizing unmet user needs and behavioral patterns that were not obvious from surface-level requests. Roman Pichler notes that AI can analyze data but cannot truly understand user needs or empathize better than humans. Jules Walter defines product sense as empathy combined with creativity to address needs, developed through observation across different contexts.
That is the muscle experienced designers bring.
The Real Risk in the AI Era
Without early sense-making, organizations risk building technically impressive solutions that solve the wrong problem, copying competitor patterns that do not fit their context, missing the insight that could make the product dramatically better, and investing months in execution before discovering the core hypothesis was flawed.
With strategic design thinking early, teams gain pattern matching across contexts, hypothesis validation before heavy investment, and strategic focus on what compounds.
The AI era does not make design less important. It makes strategic design thinking more essential. You can build quickly and affordably. You cannot recover time spent executing the wrong idea. The companies that win will not be the ones that build fastest. They will be the ones that knew what to build.
