12.02Report Design and CompilationAvailable

Research Report Design

Make a research document readable: hierarchy, typography, whitespace, consistent charts, accessible treatment, and headlines that state the finding.

Free. Works on Claude, ChatGPT, Gemini or any assistant that accepts a skill file.

What this skill does

The method, encoded.

A research report can be analytically sound and functionally unreadable. The evidence is right, the argument is right, and the reader cannot find either, because the page gives them no way to know what matters. Three charts sit at equal size, so nobody can tell which one is the point. The headline says "Satisfaction by Segment", so a reader who skims the headlines learns nothing. The base and the caveat are in six-point grey at the foot of the page, which is a design decision that quietly removes a disclosure the researcher was obliged to make.

This skill treats design as part of the argument rather than a coat of paint applied at the end. It covers the density contract between a document to be read and a reference to be searched, the small number of typographic decisions that actually affect long-form legibility, whitespace as the tool that groups and separates, one primary idea per page and how to test for it, chart hierarchy and chart-family consistency, accessibility as a baseline rather than an enhancement, and the headline convention with worked before-and-after pairs.

It also names the five design failures peculiar to research documents: the wall of charts, the slide that is a document, the inconsistent chart family, the decorative image, and the caveat in six-point type.

Chart selection goes to a separate skill. So does presentation design. This one owns the page.

Best used for

  • Compiled reports that read well and look like working documents
  • Decks that have become a wall of charts with no point per page
  • Team report templates being created or revised
  • Deliverables that must meet an accessibility standard
  • Documents assembled by several people whose charts do not match
  • Dense deliverables where the readability trade-off must be made deliberately

Typical inputs

What you give it.

Compiled report with settled claims, headlines, bases and caveats, Stated reading mode (screen, print, projection) with the primary one named, Purpose on the density spectrum (narrative, reference or stated hybrid), Brand or template system, with mandatory and conventional elements distinguished, Accessibility requirement, where one is stated, Architecture document with chapter altitudes and page budgets, Chart source files rather than exported images, Previous report in the same series

Typical outputs

What you get back.

Design specification covering grid, type, spacing, colour, charts and disclosures, Page template family with named anchor positions, Designed document with one primary idea per page, Headlines rewritten as findings, tested for overreach, Consistent chart family with fixed colour meaning, scales and category order, Disclosure specification for bases, sources, question references and caveats, Accessibility check record with measured contrast and stated exceptions, Design QA log by page, issue category and fix applied

Method coverage

What the skill works through.

  1. Why design is part of the argument, not a coat of paint
  2. Choosing a density contract: a document to read or a reference to search
  3. Grids, anchor positions and a template family small enough to memorise
  4. The typographic decisions that matter: size, measure, leading, hierarchy steps
  5. Whitespace as structure rather than leftover
  6. One primary idea per page, and the covered-headline test
  7. Chart hierarchy within a page
  8. Making charts look like one family
  9. The headline convention, with before and after
  10. Bases, sources and caveats: giving disclosures a legible home
  11. Accessibility as a baseline that helps every reader
  12. The five design failures of research documents
  13. What design must never do to a claim

Download

Free skill. One file.

Enter your email once. Every skill you download after that takes a single click.

How to install

Add the skill file and the five kernel protocols to a Claude Project, a ChatGPT Project, a Gemini Gem, or paste them at the top of any assistant conversation. Then give it your real research material, not a description of it.

Download skill

Questions

Common questions.

How do I make a research report look professional?

Make a small number of decisions and hold them without exception: line length, leading, a type scale of about four clearly distinct sizes, one primary idea per page, a headline that states the finding, a fixed position for bases and sources, and one meaning per colour throughout. Consistency is worth more than sophistication. A plain document applied consistently reads as competent; a sophisticated one applied inconsistently reads as careless, and the carelessness transfers to the analysis in the reader's mind.

What should a chart headline say?

The finding, not the topic. "Reasons for Lapsing" is a label. "Lapsed members left over scheduling, not price" is a headline: it makes a claim, it can be disagreed with, and it survives being quoted in an email with no chart attached, which is what happens to headlines. Test that it is true of that page and nothing more, and watch for causal words the design does not license. "Support contact destroys satisfaction" claims causation that a cross-sectional survey cannot support.

What type size and line length should a report use?

Line length matters more than size and is more often wrong: aim for roughly 55 to 75 characters per line for continuous prose. Set leading at about 1.4 to 1.5 times the type size for body text. Size depends on the reading mode, which has to be decided first; screen reading generally needs larger type than research documents use, and every element including bases and axis labels sits above a stated accessibility floor. Use about four clearly distinct sizes. Sizes that are close together read as inconsistency, not hierarchy.

How much information should go on one page?

One primary idea. Test it by covering the headline and asking a colleague what the page says. If they name two things, one of them is being ignored by every reader, and the page should split. If they say "I don't know", the page may have no finding on it at all, which is common and is usually the discovery that lets a document lose a third of its pages without losing anything.

How do I make a research report accessible?

Measure contrast rather than judging it: at least 4.5 to 1 for body and small text, 3 to 1 for large text and meaningful non-text elements. Set a type size floor and hold it for bases and captions too. Never carry meaning in colour alone, which means direct labelling, position, pattern or shape in charts and a word alongside any colour-coded status. Use real heading levels rather than large bold text, mark table header rows as headers, give meaningful images alternative text, and check every chart in greyscale, which takes two minutes and catches most failures.

Why does my deck feel like a wall of charts?

Because every page carries equally weighted visuals with topic headlines, so no page has a point and the reader has to build the argument themselves. The fix is three things: one primary idea per page, a headline that states the finding, and the deletion of the charts that exist because a distribution existed rather than because a finding did. Where a page carries several charts, one should be visibly dominant and the rest subordinate. Three charts of equal size is not a hierarchy.

Where should the base size and caveats go on a page?

In a fixed position on every page, at a size that can actually be read. A base line in six-point grey satisfies the letter of a disclosure while defeating its purpose. And a material caveat is not a footnote at all: if a reader would act differently knowing it, it belongs in body text next to the finding it qualifies, not at the foot of the page or in an appendix.

How do I make charts made by different people look consistent?

Fix five things once and apply them everywhere: what each colour means (and keep each segment's colour constant through the whole document), whether axes start at zero and how any exception is signalled, the order of categories, whether labels are direct or in a legend, and the weight of gridlines and axes. Rebuild inherited charts rather than patching them. The diagnostic that this has failed is that a reader can tell which analyst built which chart.

Should a research report be dense or readable?

Choose, and write the choice down. A narrative document carries one idea per page and reads well but answers specific questions badly. A reference document is dense, consistently placed and searchable but persuades badly. Both are legitimate. The failure is not choosing, which produces a document too dense to read and too incomplete to search. The usual right answer is a narrative main document plus a genuinely dense appendix, designed to different rules and visibly different.

Can design change what a report says?

It must not, and this is the main risk of the stage. A headline shortened to fit a column is a claim altered by a layout constraint. A base dropped to clean up a chart makes a finding uncheckable. A number rounded to fit a label loses its source. And a page with room for a fourth bullet will get one, which is how content that was never in the evidence enters a document that arrived clean. Design moves and sets things. It does not edit evidence.

Research where people already are.
Analyse it where you already work.

Yazi helps researchers conduct surveys, AI interviews and longitudinal research directly through WhatsApp.

New Report on SA Gambling Impact
Check It Out