Critique

Use this to review your own work before calling it done, or to review someone else's. Look at the rendered design (a screenshot or the live page), not only the code.

How to look

  1. Five-second test. Look for five seconds, then look away. What was it, what was most important, what should you do next? If those answers don't match the brief, start with hierarchy.
  2. Squint. Blur your eyes or the image. You should see a clear focal point, clear groups, and a path through the page.
  3. Grayscale. Imagine it without color. Does the hierarchy hold?
  4. Read it as the person. Go through the main task step by step with the real content.
  5. Then the checklist.

Checklist

Hierarchy

  • [ ] One dominant element per view; it's the most important thing.
  • [ ] One primary action per region; secondary actions are visibly quieter.
  • [ ] Clear steps between levels of text (size, weight, color), no near-misses.
  • [ ] In label/value pairs, the value leads.

Layout and spacing

  • [ ] Every spacing value is on the scale.
  • [ ] Space inside groups is clearly smaller than space between groups.
  • [ ] Few distinct alignment edges; nothing is a few pixels off.
  • [ ] Line lengths are comfortable (about 45–75 characters).
  • [ ] Sections vary in rhythm; it's not the same block repeated.

Typography

  • [ ] 5–7 sizes from the scale; 2–3 weights.
  • [ ] Line height and letter-spacing suit each size (tight headlines, tracked caps).
  • [ ] No orphans in headlines; tabular figures where numbers align.

Color

  • [ ] Accent used sparingly, on what matters.
  • [ ] Neutrals have temperature; no gray text on colored backgrounds.
  • [ ] Status never relies on color alone.

Components and states

  • [ ] Consistent radii, borders and elevation.
  • [ ] Hover, focus, disabled, loading, empty and error states exist where needed.
  • [ ] Icons from one set, one stroke width, sized to their text.

Content

  • [ ] Real, specific copy; no lorem ipsum or interchangeable slogans.
  • [ ] Edge cases tried: long text, empty, many items.

Accessibility

  • [ ] Text contrast 4.5:1 (3:1 large); controls 3:1.
  • [ ] Targets big enough; focus visible.

Character

  • [ ] The design follows the direction you wrote down.
  • [ ] It has its signature move, done well.
  • [ ] Nothing from the default trap crept in (purple gradients, card grids, uniform radii, eyebrows above headings, generic copy).
  • [ ] Would someone remember it tomorrow?

Prioritize

Not every issue matters equally. Fix in this order:

  1. Broken: content cut off, overlapping, unreadable contrast, a missing primary action.
  2. Hierarchy: the wrong thing leads, things compete, grouping is unclear.
  3. System: off-scale spacing, stray sizes and colors, inconsistent components.
  4. Character: drift back to defaults, a weak signature.
  5. Polish: optical alignment, punctuation, small state details.

Giving feedback

When reviewing someone else's design, report the few issues that matter most, each with:

  • What: the issue, pointing at the exact element.
  • Why: the principle and its effect on the person using it ("the two buttons have equal weight, so it's unclear which continues").
  • Fix: a concrete change ("make Cancel a text button; keep Continue solid").

Lead with what works, so it survives the revision. Three well-explained issues help more than twenty nitpicks.