A Concrete Definition of 'Product Sense' (and How to Build It)Nielsen Norman Group
ProductDesign
NN/g defines 'product sense' as pattern recognition from experimentation, not innate talent.
- The definition: Product sense means predicting which decisions will succeed based on patterns learned through actual experimentation cycles.
- The nuance: The hard part isn't knowing the patterns — it's knowing when a pattern applies to your specific context and when it doesn't.
- How to build it: It comes from repeated exposure to experiment outcomes over time, not from seniority or title alone.
- Why it matters: Gives leaders a teachable framework for developing product sense across a team, instead of treating it as an unteachable gift.
UX-Context Design: Using UX Knowledge to Inform AI-Generated DesignNielsen Norman Group
DesignProduct
As AI generates more UI, research needs to become machine-usable context, not human-facing documents.
- The shift: Research and design outputs are moving from decks written for humans to curated context that directly guides AI-generated design.
- New skill: NN/g calls this 'UX-context design' — packaging user knowledge into a form AI tools can actually consume and apply.
- Why it matters: Design teams that keep producing traditional docs risk getting bypassed as AI generates interfaces directly from prompts, without their input baked in.
- Practical step: Worth auditing what research assets already exist in reusable, structured form versus locked in slide decks nobody feeds into AI tools.
For design
Start treating your research repository as an AI-context library, not an archive — structure findings so they can be pulled directly into AI design workflows, or your team's insight gets skipped entirely.
The aggressively mediocre fightAI's default pull toward generic, average output is a fight designers now have to actively wage.
- The problem: Left unsteered, AI tools default to generic, statistically 'average' solutions rather than distinctive design decisions.
- The fight: Designers now have to consciously counteract that pull toward mediocrity in every AI-assisted workflow.
- Why it matters: As AI-generated design scales across teams, quality control becomes an active daily practice, not a one-time review step.