Case Study — Design QA & Risk Mitigation
Preventing an Engineering Regression Through Scalable Design
Role
Content Designer
Skills
Edge-case analysis · Cross-functional communication · Risk mitigation
Context
An important edge case involving error states had been overlooked for a new experiment using collapsible cards.
Collapsed (mockup)
Budget & schedule
Expanded (actual)
Left: a representative mockup of the collapsed state, showing only topline info. Right: the same card expanded, revealing an error that would be completely hidden if every card defaulted to collapsed — which was exactly the edge case at risk.
Approach
I raised the concern as soon as I spotted it, explained the implementation risk to the team, and recommended pausing the work while we evaluated the design. The team reprioritized engineering work and adjusted milestones accordingly.
Key insight
Catching a design gap before code gets written costs a conversation. Catching it after costs a rebuild. The earlier you're willing to slow a team down, the cheaper the fix — and the easier that conversation is to have.
Key decisions
- Flagged the missed error-state scenario before implementation began, not after.
- Recommended pausing the work rather than letting it proceed on a design with a known gap.
- Worked with the team to reprioritize engineering work and adjust milestones around the fix.
Who I influenced
Engineering and design partners
Raised the risk directly with the team, who reprioritized engineering work and adjusted milestones in response.
Outcome
- Avoided a costly regression by catching the issue before implementation.
- Improved the scalability and quality of the overall design approach.