Content Strategy
Design What-If: Four Passes That Move Feedback Past Taste
Stress-test design decisions against real user scenarios.
What it does
Design feedback usually stalls at taste. "I don’t like it" — and the project has nowhere to go, because a preference is not a direction. This skill replaces taste with a four-pass process that pressure-tests a design until the project commits to one idea and an emotional target it can be judged against.
The four passes — Hidden Truth, What If, Feel, and Combine — force the design to answer what it is actually communicating, what alternatives would change, what feeling it must land, and which elements survive combination. The output is a committed direction with the reasoning recorded, so later feedback is measured against intent instead of mood.
- Hidden Truth pass. Strips the decoration to state what the design actually communicates — the message underneath the styling.
- What If pass. Pressure-tests three to four wild variants so the chosen direction is a decision, not a default.
- Feel pass. Names the emotional target explicitly so the design can be tested against a feeling instead of an opinion.
- Combine pass. Merges the strongest elements into a single committed direction — no floating alternatives.
- Recorded rationale. Locks the decision and its reasons so later feedback has a target to argue against.
When to use it
- Kicking off a new design or creative direction: Run the four passes before showing options to stakeholders, so the first review is a decision, not a roulette wheel.
- Feedback has stalled on taste: When reviews produce "I don’t like it" with no direction, this framework converts preference into criteria.
- Choosing between directions: When the team cannot pick between options, the Feel pass gives you a testable emotional target.
- Reopening a decided design: When a project reopens decisions late, the recorded rationale shows what was committed to and why.
The methodology
- 1
Pass 1 — Hidden Truth
Ask what the design actually communicates, stripped of decoration. Write the one-sentence message a viewer would take away. If the honest answer is not the message the project wants, that is the finding — not the starting point.
30–60 minutes - 2
Pass 2 — What If
Generate three to four alternatives that deliberately break the current direction — different hierarchy, different tone, different medium. The point is not to produce final options; it is to reveal what the current design is choosing by showing what it is rejecting.
1 hour - 3
Pass 3 — Feel
Name the emotional target: the feeling the finished experience must produce at its key moment. Then test each direction — current and variants — against it. Directions that cannot produce the target feeling fail regardless of taste.
30 minutes - 4
Pass 4 — Combine
Take the strongest elements from the surviving directions and merge them into one committed design. The project commits here — everything after this is refinement against the recorded rationale, not re-opening.
45 minutes
Common mistakes
- Feedback expressed as taste ("I don’t like it") — Gives the design team nothing to act on and reopens the review cycle indefinitely. Convert every preference into a criterion the design can test against.
- Presenting too many options — More options mean more taste votes and no decision. The Combine pass exists to converge — use it.
- No emotional target — Without a target feeling, any direction can be argued either way. The Feel pass is what makes the review objective.
- Reopening decisions after commit — Every reopened decision multiplies the timeline. The recorded rationale is the guard — changes must argue against it, not against taste.
Output
A committed design direction plus a one-paragraph rationale: the hidden truth, the variants considered, the emotional target, and what the final design chooses.
Format
Short written decision doc — direction, emotional target, and rationale. No deck required.
Feeds into
Becomes the strategic input for design-brief-enforcer, which turns the direction into enforceable specs.
Next steps
After the direction commits, run design-brief-enforcer to translate it into named vocabulary, reference decomposition, and hard spec values. Pair with market-research if the direction needs buyer language grounding first.
Time & resources
First run
3–4 hours including the four passes and rationale write-up
Iterations
1–2 hours once the team is practiced
Low — the framework is a meeting format, not a toolchain.
Take it with you
Want to run this in Claude? This page is the strategic overview. The GitHub SKILL.md is the full technical specification — import it and run the method.
Ask Claude: "Use the Design What-If methodology to pressure-test this design." Paste the current direction, the variants, and the intended emotional target.
