# Anti-Rationalization Checklist（design-brief-builder）

| Rationalization | Reality |
|---|---|
| "I already know what the user wants, no need for the interview phase" | Your assumption is not the user's preference. The interview phase exists to extract what the user can't articulate unprompted. |
| "Skip the interview, just write the Brief from the Spec" | Product-Spec describes function, not visual direction. Without interview, the Brief will be generic and unusable for design. |
| "The product is simple, no need for detailed design questions" | Simple products still need color, typography, density, and interaction decisions. Every dimension matters regardless of scope. |
| "I've seen similar projects, I can infer the design direction" | Inferring is guessing. WebSearch for trends, ask the user for preferences — don't substitute memory for research. |
| "No need for WebSearch, I know current design trends" | Design trends change every quarter. Unless you verified this week, your knowledge is stale. Search first. |
| "Skip the sufficiency judgment, the Brief is complete enough" | Sufficiency judgment catches gaps the writer can't see. Run it every time. |
