Information Structure
Users scan, they don't read. Attention is short, and the moment two pieces of information compete on the same screen, both lose. So the first discipline of microcopy isn't writing well — it's deciding what not to say here.
Learn on the move: press play and turn your commute, walk or drive into time that grows your design career.
Listen to the full Information Structure course on DesignPath
That means one item, one idea. Present only what the current action needs. Don't cram every restriction, warning, and edge case into a single tooltip — that's content hoarding, and it buries the one thing the user actually needs right now. Work with designers to distribute information across the flow, surfacing each piece at the moment it becomes relevant. A clear screen isn't one with less to say; it's one that says it at the right time.
When It Matters Most
- Dense forms and settings — where every field tempts you to add "just one more" clarification.
- Onboarding — where the urge to explain everything upfront collides with a user who wants to start.
- Warnings and limits — where stuffing all the rules into one string makes none of them readable.
What This Module Covers
Information structure is about ordering and placing microcopy so it lands. We cover front-loading the words that matter (the serial position effect), being specific instead of generic (concrete data over abstract rules), and explaining the why before the what (so a request reads as help, not friction). The next articles make each concrete.
Front-Load What Matters
People remember the beginning and the end of a string and lose the middle — the serial position effect. Microcopy that respects this puts the most important information first, where attention is highest.
Cut the Lead-In
The most common waste of the first position is a lead-in — a warm-up phrase that pushes the real message into the forgettable middle.
- "To get your results, provide your email" → the benefit ("results") opens, but the action lands mid-string.
- "Provide your email to get your results" → action first, benefit as the payoff.
Both have their place — but the rule is the same: decide what you most need the user to register, and put it in the first position. Don't open with "Please note that…" or "In order to…" when the meaningful word could lead.
Order Within the String
Front-loading isn't only about the first word of a label — it's about the order of everything:
- Headings carry the most weight; make them the message, not a category ("Payment failed" beats "Payment information").
- Error and helper text should open with what to do, not with an apology.
- Lists should lead with the most common or most important item, since the middle of a long list is where attention dips.
Where AI Helps
AI is good at spotting buried leads and rewriting for first-position impact.
Prompt: "Rewrite these UI strings so the most important information comes first and any lead-in is cut. Keep them short, and tell me what each string's key message is. [paste strings]"
AI surfaces the buried lead; you confirm it's the right one.The model can reorder for the serial position effect, but which word matters most in your flow is a product judgment — verify the rewrite still says the thing the user came for.
