Stakeholders Only Give Color Feedback on a Structural Redesign
Your team is redesigning a multi-step signup flow that currently has a high drop-off rate. You built the first review artifact directly in Figma at near-final visual fidelity — full brand colors, final typography, polished icons — because "it's faster to just build the real thing once." In the review meeting, every piece of stakeholder feedback is about color contrast, icon style, and font size. Nobody comments on whether the new step order or field grouping actually fixes the drop-off problem, which was the entire point of the redesign.
- Using the ideas from this subject, explain why this outcome was predictable given the artifact you chose to show.
- What fidelity and interactivity combination should have been used for this first review, and why?
- Concretely, what would you change about the artifact for the next review meeting to get the feedback you actually need?
- Is it ever correct to skip straight to high fidelity for a redesign like this? Name the condition under which it would be.
1. Why this was predictable
Fidelity controls what kind of feedback an artifact invites, not just how "finished" it looks. A near-final visual mock looks done, so reviewers have nothing left to react to except the surface layer — color, type, icon style — and they implicitly assume the structure underneath (the thing that actually determines whether drop-off improves) must already be settled, precisely because it looks that polished. The team asked a structural question ("does this fix drop-off") using an artifact built to answer a visual one, and got visual answers back.
2. What should have been used instead
Low-to-mid fidelity, low-to-moderate interactivity: a grayscale wireframe of the new step order and field grouping, ideally with basic click-through so reviewers can follow the sequence, but with no brand color, final typography, or icon polish. That artifact visibly isn't finished, so the only thing left to react to is exactly what needed validating — does the new structure make sense, is anything missing, does the step order actually address where users were dropping off.
3. What to change for the next review
Strip the mock back down: grayscale boxes, placeholder or close-to-real copy, the same step order and field grouping, no brand visual system applied yet. Explicitly frame the meeting up front — "I want feedback on the flow and step order today, not on color or type, we'll get to that once structure is confirmed" — so the framing reinforces what the artifact's fidelity is already signaling.
4. When skipping to high fidelity is legitimate
When the structure is already low-risk and well-understood — for example, reusing an existing, already-validated step order from another part of the product, or a flow the team has already tested structurally in a prior project — the cost-of-change risk that justifies low fidelity is much smaller, so going straight to high fidelity can be a reasonable efficiency win rather than a gamble. The condition is specifically that structural risk is low, not that the team is simply in a hurry.
Share this question