
Designing a dashboard around decisions
A dashboard becomes useful when it helps someone choose a next action. More charts rarely solve a problem of unclear priorities.
Read the story ↗
Notes on thoughtful design, clear content and the practical work of making digital things.

From the studio
Twelve considered articles on the decisions behind useful brands, websites and product experiences.

A dashboard becomes useful when it helps someone choose a next action. More charts rarely solve a problem of unclear priorities.
Read the story ↗
An identity system earns its place through consistent everyday use. A concise guide with real examples is often more useful than a large collection of abstract rules.
Read the story ↗
A project brief should make decisions easier. It needs enough detail to expose constraints while leaving room to discover a better solution.
Read the story ↗
Motion can explain how an interface changes, but essential content should never depend on waiting for an animation to finish.
Read the story ↗
People need particularly clear language when something has failed, is still processing or requires a decision with consequences.
Read the story ↗
A successful build is one piece of release evidence. We also need to inspect the delivered pages, their data and the tasks people will perform.
Read the story ↗
Content models work best when they describe a stable editorial idea. Repeated visual blocks are useful clues, but they are not the whole model.
Read the story ↗
A bounded feature is easier to evaluate than a general promise of intelligence. Begin with a task that has a clear input and a reviewable result.
Read the story ↗
A photograph that works in a wide hero may fail in a narrow card. Planning the image system alongside the layout prevents awkward crops later.
Read the story ↗