News and articles on information design, clear communication and user-centred work.
This journal is where the Information Design Unit writes about the work behind clear communication. It is a place for notes from projects, reflections on method and observations about how people read, search and decide.
The Information Design Unit sits within Enterprise IG, a branding and design agency with 22 offices worldwide. Our articles draw on that wider network, but they are written from the specialist side of the practice.
Articles will be listed here as they are published. Each one will carry a short introduction, and each image will be captioned so that the reader knows what it shows and why it matters.
Reading habits shape every decision we describe in these notes.
Many of our articles start with a simple observation about how someone reads a page. That observation is then tested with people, not only with reasoning at a desk.
Drafts pinned up together show how a system holds across many pages.
Articles on method often describe the wall as much as the result. Seeing many pages side by side is how we check that headings, spacing and labels still agree.
Wayfinding is tested on foot, not only on a drawing.
Future notes will describe how signs are checked in real spaces, with real walking routes and real questions from visitors.
Sorting exercises reveal how people group information before we design it.
Card sorting and content review help us decide what belongs together. Those decisions are often more useful to readers than any visual change.
Articles are written by practitioners in the Information Design Unit who worked on the project or research being discussed.
Yes. Where possible, we show the before and after of a layout and explain the reason for each change.
To suggest a topic, visit our contact page. For our wider view of the subject, read how we think.
Policy documents are written to protect the company. Customer messages are written to be understood. Those two goals collide every day in support tickets, onboarding flows, and…
Start With the Reader's Task, Not the Template Most teams open a layout tool before they answer a basic question: what must the reader do with this document? A policy reader mus…