2.8 Qualitative taste validation
2.8 Qualitative taste validation
humans (not agents) test for taste / UX / defect discovery, not just correctness. Delivered either via a dedicated usability research service (Netizen Experience, UserTesting, Lookback, Maze, PlaybookUX) or via your own user base through canary releases and A/B tests. Catches what automated tests can't: is this confusing? Does this feel wrong? Would a real user hit this edge case?
Levels
Level 0
None
Level 1
Occasional usability review or ad-hoc user feedback
Level 2
Continuous human validation wired into release loop — either via research-service cohort or via canary/A-B rollouts to real users with feedback capture
Level 3
Taste feedback patterns extracted; design-system rules updated; prompts/components evolved to address recurring taste failures
Recipes that advance this criterion
No recipes yet.