Direction / Feedback / Thoughts — a framework for unambiguous design critique¶
Insight: Design critique fails when participants don't signal the intent behind their feedback. A three-tier framework resolves this: (1) Direction — "please do this," non-negotiable changes with specific actions ("reduce spacing to 16px"), (2) Feedback — "please solve this," identifies problems but leaves solutions to the designer ("the hierarchy is confusing"), (3) Thoughts — "just musing," observations requiring no immediate action but worth noting for future iterations ("this reminds me of that travel app"). Labeling each piece of feedback with its tier eliminates the guesswork that makes critique sessions unproductive.
Detail: Tisza (15 years UX experience, formerly Microsoft) notes this framework has been used in consulting and design agencies. The key problem it solves: designers leaving critique sessions unsure whether feedback was a command, a problem to solve, or casual brainstorming. For design systems teams specifically, this framework is valuable during component review and governance meetings where multiple stakeholders have different levels of authority over design decisions. It pairs with the existing knowledge about designer boundaries (Dan Mall) — knowing whether feedback is Direction vs. Thoughts helps designers set appropriate boundaries on what they commit to changing.
Sources
- Niki Tisza — "The Best Approach to Design Critique" (2025-04-29)