Design criticism that names names

Criticism and commentary is the part of the site where a piece of design work gets held up against the brief it was answering. A rebrand, a new grid system, a shift in how a studio handles type: each gets examined for the problem it was trying to solve and whether the solution actually holds up.

What separates a critique from a write-up

A write-up describes what changed. A critique says whether the change was the right call and explains the thinking behind that judgement using the actual decisions made. The way Klim Type Foundry handles optical sizing gets discussed in a piece like this because it illustrates a principle about matching letterforms to context.

• Names the studio, designer, or project rather than speaking generally about "good typography" or "strong branding"
• Takes a position on whether the work succeeds, and on what terms
• Points out at least one tradeoff or weak spot, because praise without reservation reads as promotion rather than analysis
• Explains the mechanism behind a decision

Some claims made about a piece of work are checkable. When a studio says its new brand palette meets accessibility guidelines, that is a statement with actual maths behind it, and a critique that takes the claim on trust is doing less than one that checks it. Our True-Contrast Smart Palette runs a foreground and background pair through the same relative luminance calculation the guidelines specify, and returns a contrast ratio alongside PASS or FAIL badges for the AA and AAA thresholds, so you can see whether a PASS badge in a press release actually holds up before you repeat it. Like any calculator, it depends on the hex values you give it, and a typo or a slightly wrong swatch will hand back the wrong reading, so it works as a check on your own judgement.

A redesign that claims to load faster is making the same kind of checkable statement. Load time comes down to latency plus how much has to travel divided by the connection's bandwidth, and a homepage that ships a heavier JavaScript bundle can end up slower than one shipping heavier images, because JavaScript bytes cost the processor more to run than image bytes cost it to display. The Performance Budget Calculator runs that formula backwards: pick a network, from a slow mobile connection to a fast wired one, set a target load time, and split the weight budget across JavaScript, images, and CSS with fonts, and it returns the total page-weight budget along with per-category figures and a warning once the JavaScript share runs past roughly 150KB. It reserves a slice of that budget for protocol overhead rather than treating the whole figure as payload, and if the network's own latency already eats the target time, it says so instead of quietly returning zero. It still only works from the numbers you give it, so it's worth running against a redesign's actual asset weights before a performance claim gets repeated in a piece.

Where this fits against the rest of the site

The Inspiration Showcases section exists to surface work worth looking at. The Design Feed covers what's happening in the industry as it happens. This section moves slower, because a piece here might sit with a single rebrand or a single design system for two thousand words, and an argument needs that room to hold together.

If you've written a piece that argues a position on design work and think it belongs here, the editorial address is designblog.