Most research reports are read by almost nobody. The people who commissioned them read them. The people who wrote them read them. A small number of others – reviewers, close colleagues, people with a direct stake in the findings – read them. Everyone else skims the executive summary, if they get that far, and moves on.

This is treated as an audience problem. The findings are too technical, or the subject too niche, or the policymakers too busy. Sometimes that’s true. But in a significant number of cases, the real problem is the document itself – specifically, that it makes no concessions to how people actually read.

How people actually read documents

Nobody reads a report the way they read a novel. They don’t start at page one and work through to the end. They land on it, assess it rapidly, decide whether it’s worth their time, and if so, navigate to the parts that are relevant to them.

That assessment happens fast – within seconds of opening the document. And it’s driven almost entirely by visual information: how dense the text looks, whether there are clear navigation aids, whether the page has a hierarchy that makes the structure legible at a glance. If the document looks like a wall of undifferentiated text, most readers make an unconscious decision that this will be hard work. Many of them stop there.

The readers who continue – who make it to page three and beyond – are usually the ones who have no choice. They need the information. Everyone else, including many of the people the research was produced for, has already left.

What visual hierarchy actually does

Visual hierarchy is the system of signals a document uses to communicate its own structure. Size, weight, colour, spacing, position – these are the tools, and when they’re used well, a reader can understand the shape of a document before reading a single word.

They can see where sections begin and end. They can identify headings and subheadings. They can find the key findings without hunting for them. They know, from the layout alone, what’s most important and what’s supporting detail.

When hierarchy is absent or weak, none of that is available. The reader has to supply the structure themselves – reading every word to understand where they are and what matters. That’s a significant cognitive load to place on someone who was already ambivalent about engaging with the document.

Good hierarchy doesn’t simplify the content. It makes the content navigable. Those are different things, and the distinction matters for research organisations and charities who worry – rightly – about being seen to oversimplify complex findings. The findings don’t need to be simpler. The document structure does.

The most common hierarchy failures

Headings that don’t do structural work. A heading in a slightly larger font, or in bold, but otherwise indistinguishable from body copy, is not a heading – it’s emphasised text. Proper headings are visually distinct enough that a reader scanning the page can find them without reading. That usually means a meaningful size difference, a different weight, and often a different typeface or colour. If your headings aren’t findable at a glance, they’re not functioning as headings.

Executive summaries that summarise rather than lead. The executive summary is the most-read part of any research report. It should contain the findings, not a description of what the report contains. “This report examines X and concludes Y” is a contents description. “The evidence shows Y, with implications for Z” is an executive summary. The design of the executive summary matters too – it should look different from the rest of the document, signal its own importance, and be legible at a skim.

Body copy with nowhere to land. Long paragraphs of unbroken text are hard to navigate back into once a reader has looked away. Subheadings within sections, pull quotes for key findings, and clear paragraph breaks aren’t decorative – they’re navigation aids. A reader who loses their place in a dense document often doesn’t go back.

Findings buried in the middle. The instinct in research writing is to build toward the conclusion – to show the methodology, the data, the analysis, before revealing what it all means. That’s appropriate for a journal article. For a policy-facing report or a charity’s impact publication, it’s usually the wrong order. The findings should be early and visible, with the supporting evidence behind them for readers who want it.

This is a design problem, not a writing problem

The fix for most of these issues doesn’t require rewriting the content. It requires restructuring how the content is presented.

That means headings that are designed, not just formatted. An executive summary that’s laid out as a distinct section with its own visual language. Section introductions that tell the reader what they’re about to find. Page layouts that have enough white space for the content to breathe.

None of this dilutes the research. A well-laid-out report contains exactly the same information as a poorly-laid-out one. The difference is that one of them gets read, and the other doesn’t.

The typography decisions that underpin all of this – typeface, weight, size, spacing – connect directly to the first article in this series. And for organisations publishing PDFs, the structural decisions here also intersect with accessibility: proper heading hierarchy isn’t just a visual tool, it’s what screen readers use to navigate a document. The accessible PDFs article covers that ground in detail.

The five-second test

Here’s a fast way to audit whether your current report layout is working.

Print a page – any page from the body of the report, not the cover. Set a five-second timer. Look at the page. Look away. What do you remember?

If the answer is “the key finding on that page,” the hierarchy is working. If the answer is “some text, I think there was a heading,” it isn’t.

The five-second test won’t tell you exactly what to fix, but it will tell you whether you have a problem. Most reports fail it. That’s not because the content isn’t there – it’s because the design isn’t making the content findable.

If your reports are failing this test, that’s worth addressing – not as an aesthetic concern, but as a practical one. Research that doesn’t get read doesn’t have impact, regardless of how good it is. Get in touch to talk about a report design or template project.