Fundamentals
Design Mistakes Guide Diagnose the Cause, Not the Symptom
A long list of rules can make every design look broken. Start with the job, name the visible mismatch, and test the smallest change that could improve the experience.
The short read
Start with the job
A choice is not a mistake in the abstract. Connect it to the audience, task, message, system, or constraint.
Name the consequence
Explain what becomes harder to notice, understand, trust, use, or maintain.
Fix the cause
Change the smallest high-impact decision and retest instead of applying every rule at once.

Define the mismatch before prescribing the fix
Design advice often turns patterns into commandments: use two fonts, never center body copy, avoid gradients, keep everything above the fold. Those shortcuts can help a beginner notice a decision, but they cannot tell you whether the decision fits this work.
A useful diagnosis connects a visible choice to its consequence. “There are four fonts” is an observation. “Four similar display faces make the section levels difficult to distinguish” explains the problem. The second statement gives you something to test.
| Observe | What is visibly happening, without explaining the cause yet? |
|---|---|
| Connect | Which audience, task, message, requirement, or system rule does it affect? |
| Explain | What consequence does the mismatch create? |
| Test | What comparison, measurement, or behavior would confirm or challenge the interpretation? |
| Change | What is the smallest revision that addresses the cause? |
Hierarchy problems make the wrong thing feel important
Squint at the composition or step away from it. Notice which three elements survive. Compare that order with the decision the audience needs to make. Hierarchy can fail because everything is loud, because the primary action resembles a secondary one, or because the meaningful content is visually quieter than decoration.
Test the first read
Ask someone what they notice, what they think the page is about, and what they would do next before giving context.
Change one lever
Adjust size, weight, position, spacing, contrast, or repetition. Do not change all of them at once or you will not know what repaired the order.
Typography problems hide roles and interrupt reading
Start with the content roles: title, section, label, instruction, data, action, and long-form text. Each role needs enough distinction to be recognized and enough consistency to be learned. More typefaces are not automatically bad; unclear roles are.
Test real text at real widths. Look for overly long lines, cramped line spacing, ambiguous labels, weak emphasis, and display styles that collapse when a heading wraps. Use the Font Pairing tool to explore relationships, then judge them with your content.
Color problems confuse meaning or lack measurable support
Write down the jobs color performs: brand recognition, hierarchy, state, category, data, focus, or atmosphere. If several colors perform the same job, the system may feel arbitrary. If one color performs conflicting jobs—such as success and primary action—the interface may teach the wrong pattern.
Measure contrast from the actual interface when the values are available. A screenshot can point to a place that deserves inspection, but it cannot prove an exact ratio when compression, transparency, imagery, or unknown values affect the pixels. State what needs checking and what evidence would resolve it.
A stronger accessibility note
The label appears faint against this surface. Measure the rendered colors in the real state and test whether the control remains understandable when color is unavailable.
Can you see the symptom but not the cause?
Share the work and the job it needs to do. Your free First Read identifies one consequential mismatch and a useful next move.
Layout problems break relationships and rhythm
Spacing is information. Items that belong together should generally feel closer than items that begin a new group. Alignment creates a path through the composition. Repeated dimensions help a system feel intentional—until the content needs a different structure.
Test at the narrowest and widest relevant formats. A layout that looks balanced in one artboard may produce awkward empty space, clipped evidence, or a confusing reading order elsewhere. Diagnose the relationship that failed before adding another breakpoint.
Interaction problems often live outside the polished state
Review the default, hover, focus, pressed, disabled, loading, empty, success, and error states that the experience actually uses. Check whether status is communicated beyond color, whether keyboard focus remains visible, and whether motion has a purpose and a reduced-motion alternative.
Inspect the recovery
The happy path shows what the interface wants. Recovery shows whether the interface helps.
Try an invalid value, no data, a slow response, a failed upload, a long name, and keyboard-only navigation. The most consequential problem may never appear in the hero mockup.
Consistency should reduce learning, not erase useful difference
Repeated patterns help someone predict what an element means and how it behaves. Audit components that look alike but act differently, and elements that perform the same action with different labels, shapes, or positions.
Do not force every page into the same composition simply to satisfy a system. Preserve difference when it helps the content or task; document why the exception exists so it does not become accidental drift.
Fix in consequence order
Meaning and task
Repair the issue that makes the purpose, information, or next action unclear.
Access and recovery
Address barriers that prevent people from reading, navigating, understanding status, or recovering from a problem.
System and trust
Resolve contradictions, broken patterns, and unsupported claims that make the experience feel unreliable.
Polish
Refine rhythm, optical balance, imagery, and expressive detail after the design is solving the right problem.
QuestionsAnswers
Questions, answered.
A few practical details before you keep going
Share this resource

Written by
Nikki KippleProduct Designer & Design Instructor
Designer, educator, founder of The Crit. I've spent years teaching interaction design and reviewing hundreds of student portfolios. Good feedback shouldn't require being enrolled in my class — so I built a tool that gives it to everyone. Connect on LinkedIn →
A checklist can name symptoms. A critique can connect the evidence.
Share the work and what it needs to do. We will look for the most consequential mismatch rather than manufacturing a list of faults.