Develop Product Judgement
How to develop product taste through comparison, evidence, critique and the consequences of decisions.

Two support interfaces produce the same answer. One shows where the policy came from and lets the reviewer correct it. The other looks simpler, but hides the source and places the send button beside the draft.
Choosing between them involves more than visual preference. The designer and product manager need to understand the user's work, the consequence of an incorrect answer and the effort involved in checking it. That judgement is part of product taste.
Make the judgement visible
Taste appears in choices: which problem to solve, what quality requires, where to use a familiar pattern and which feature to leave out. A polished interface is not enough if it creates confusion or cannot be operated safely.
For an important decision, ask:
- Who is this for, and what are they trying to do?
- What must be true before the result is useful and trustworthy?
- Which option best fits the situation, and what does it sacrifice?
- What will be harder to maintain, support or change later?
- What evidence would make us reconsider?
The answers help a team explain its judgement and expose the assumptions behind it.
Compare before choosing

Review multiple approaches to the same task. Ask what each helps a person accomplish and where it creates friction. Consider the strongest case for an option you initially dislike; it may reveal a constraint you have overlooked.
AI can generate alternatives quickly, but a large collection of plausible variations does not define the standard. The team still has to choose which differences matter and test its assumptions with people doing the work.
Learn from consequences
Keep examples of decisions that worked and those that did not. Record the context, the choice, the alternatives and what happened afterwards. Before looking at an experiment's result, write down what you expect. When the result surprises you, investigate whether your understanding of the user, the mechanism or the measurement was wrong.
Practise an adjacent craft far enough to receive useful correction. Building a prototype, conducting research or modelling an operating cost can reveal constraints that are easy to miss from a distance. Specialists can help explain the difference between a plausible result and a dependable one.
Good judgement also includes knowing when an attractive option has not earned its place. Product bets covers how to test and stop an idea; accountability covers the responsibility that follows the decision.
v3.1 · Updated Oct 2026