# Prompting For Design Critique Instead Of Design Praise

> Ask what a user will fail to do, not whether it looks good.

- **Author:** [Layla Al Mansoori (@layla_almansoori)](https://www.promptabide.com/layla_almansoori)
- **Published:** 2026-04-24
- **Updated:** 2026-08-22
- **Tags:** `design`, `ux`, `critique`, `product`
- **Views:** 7660
- **Likes:** 453

## Prompt

```
Show a model a screenshot and ask what it thinks, and you get compliments. "Clean, modern, good use of whitespace." Useless.

Ask this instead:

"Here is a screenshot of [screen]. The primary task is [task].

1. What will a first-time user try to click first, and is that right?
2. What information do they need for this task that is not on screen?
3. What is competing with the primary action for attention?
4. Where would this break — long names, empty state, a slow network, 320px wide?
5. What would you cut?"

Question 5 gets the best answers, because it forces a ranking. Everything on the screen has a defender until you make something leave.

Q4 is where I have got the most concrete wins — an empty state nobody had designed, a two-line product name that broke the card grid.
```

---

Canonical HTML: https://www.promptabide.com/bides/design-critique-not-praise-layla-almansoori-1
Agent guide: https://www.promptabide.com/llms.txt · https://www.promptabide.com/agent-instructions.md
Sitemap: https://www.promptabide.com/sitemap.xml
