Product Judgment and What to Create

Before a single line of code is written, before an AI agent is prompted, before an architecture is sketched, someone has to decide what to build and why. This section lives at the strategic level: the decisions that determine whether a product deserves to exist and whether anyone will care that it does.

These patterns address the questions that come before engineering. Who’s the customer? What problem are they willing to pay to solve? How will the product reach them? How will it make money? And critically: should it be built at all? Getting these wrong means building the right thing for nobody, or the wrong thing for everybody.

In an agentic coding world, where AI agents can generate working software in hours instead of months, the cost of building has dropped but the cost of building the wrong thing has not. Product judgment becomes more important, not less, when creation is cheap. An agent can ship a feature by morning; only a human can decide whether that feature should exist.

This section contains the following patterns:

• Problem — A real unmet need, friction, risk, or desire experienced by a specific person or organization.
• Customer — The person or organization that pays, approves, or otherwise causes the product to exist.
• User — The person whose workflow, pain, or desire the product directly touches.
• Value Proposition — The reason a specific customer should choose this product over doing nothing.
• Competitive Landscape — The set of real alternatives available to a customer.
• Differentiation — The feature, capability, or position that makes the product meaningfully distinct.
• Beachhead — The narrow initial market or use case where the product can win first.
• Go-to-Market — The plan by which a product reaches customers and starts generating revenue.
• Revenue Model — The basic way money flows into the business.
• Monetization — The practical mechanism by which usage gets converted into revenue.
• Distribution — How the product gets into the hands of people who might buy or use it.
• Product-Market Fit — The condition in which a product clearly satisfies a strong market need.
• Crossing the Chasm — The problem of moving from early adopters to the pragmatic majority.
• Zero to One — Creating something genuinely new rather than competing in an existing market.
• Bottleneck — The limiting factor that most constrains progress.
• Roadmap — An ordered view of intended product evolution over time.
• User Story — A concise statement of desired user-centered behavior.
• Use Case — A more concrete description of a user goal and the interaction required.
• Build-vs-Don’t-Build Judgment — Whether a product or feature should exist at all.