Designing for
What Goes Wrong.
A card deck that helps product teams uncover UX failures before they reach users. Stress test what breaks — not just what works.
The failure you didn't design for
Most design processes test the happy path. The UX Failure Deck forces you to explore every way a product can break, frustrate, or confuse.
A prompt for every breakpoint
54 scenario cards across 7 failure categories. Each card poses a real failure mode and asks what your product does about it.
Run it before you ship
Use it in critique sessions, design reviews, or sprint retrospectives. A physical prompt changes the conversation in the room.
7 failure categories
Every card belongs to one of seven failure domains — from trust breakdowns to interaction edge cases.
BEHAVIOUR
User skips onboarding
What's unclear at first glance?
Some users jump straight into the product. The interface should still make sense without setup or explanation.
& SAFETY
User doesn't want to create an account yet
Is there a guest path?
Some users want to explore before committing. If access requires immediate sign-up, they may leave before seeing value.
& STATE
Error message appears without guidance
What should the user do next?
An error without next steps leaves users stuck. Good design explains what happened and how to fix it.
& CONTENT
Labels use internal terminology
What confuses non-experts?
When language reflects internal teams instead of users, clarity breaks. Plain, user-centred language reduces hesitation.
& DEVICE
User increases system font size
Do layouts still hold together?
Layouts must adapt without breaking structure or hiding elements. Content should remain readable and usable at larger text sizes.
Back navigation loses work
Is this expected?
Users expect the back action to return safely without losing progress. If work disappears, it feels like a mistake or system failure.
User didn't ask for AI
Does the core product still work?
Automation shouldn't replace core functionality. The product must still work without AI. Users should always be able to complete tasks manually.
Draw a card.
Start a conversation.
Each card presents a failure scenario and a question your team needs to answer before shipping.
BEHAVIOUR
User skips onboarding
What's unclear at first glance?
Some users jump straight into the product. The interface should still make sense without setup or explanation.
& SAFETY
User doesn't want to create an account yet
Is there a guest path?
Some users want to explore before committing. If access requires immediate sign-up, they may leave before seeing value.
& STATE
Error message appears without guidance
What should the user do next?
An error without next steps leaves users stuck. Good design explains what happened and how to fix it.
& CONTENT
Labels use internal terminology
What confuses non-experts?
When language reflects internal teams instead of users, clarity breaks. Plain, user-centred language makes actions easier to understand and reduces hesitation.
Back navigation loses work
Is this expected?
Users expect the back action to return safely without losing progress. If work disappears, it feels like a mistake or system failure.
User didn't ask for AI
Does the core product still work?
Automation shouldn't replace core functionality. The product must still work without AI. Users should always have a clear way to complete tasks manually.
Hover to reveal the prompt
How to use
the deck
Pick a category
Choose a failure domain relevant to what you're building or reviewing — or shuffle and draw at random.
Read the scenario
Each card describes a real-world failure mode and asks a pointed question your team must answer honestly.
Have the conversation
Does your product handle this? If not, what would it take to fix? Use the card as a critique prompt.
Who uses it
UX Designers
Stress test your own work before handing it off. Find the gaps you didn't notice when you were inside the problem.
Product Managers
Run structured edge-case reviews without needing to lead a design critique. Get the team asking better questions.
QA & Researchers
Supplement usability testing with failure-mode prompts. Surface issues that scripts alone won't catch.
Design Teams
Use in retrospectives, design crits, or sprint planning. Build a failure-aware culture before it becomes a habit.
Ready to design for
what goes wrong?
54 cards. 7 categories. One deck that changes how your team thinks about shipping.