Charlie Munger once said, at a Berkshire Hathaway shareholder meeting recapped years later by financial press, that even a fairly simple business takes real effort to understand from its annual report — and Warren Buffett, who reads more of them than almost anyone alive, put his own reading time at something like forty-five minutes to an hour per report. That's the person the document is supposedly written for: patient, financially literate, motivated. Most annual reports are not designed for that person. They're designed for someone who will glance at three numbers, skim a letter, and close the file.

That mismatch is where most of the design problems start. Not the color palette. Not the font. The report is built as if it will be read start to finish, and then it's handed to people who will read it the way they read everything else — in fragments, under time pressure, looking for a reason to keep going or a reason to stop.

Two very different readers are opening the same file

A board member skimming before a meeting and an equity analyst building a model are technically reading the same document, but they're doing almost nothing in common. One wants three or four numbers and a plausible story in under two minutes. The other wants every footnote, every restated figure, every change in accounting policy — and will actively distrust a report that hides those behind pretty graphics.

I wouldn't recommend designing for an average of these two readers, because that average doesn't exist as a person. What works instead is layering: a front section — cover, letter, highlights, one or two key charts — built for the skimmer, and a back section — full statements, notes, tables — built for the person doing real diligence, with almost no design intervention beyond clean typesetting. The mistake I see most often is applying the same visual effort to both halves, which either over-decorates the financials (bad for the analyst) or under-serves the highlights (bad for everyone else).

Where the infographic actually helps — and where it quietly lies

A bar chart showing revenue growth across five years is almost always a fair representation. A donut chart showing "where our revenue comes from" starts to get shakier once there are more than four or five segments, because the eye can't reliably compare wedge sizes past that point — people end up reading the labels anyway, which makes the chart decorative rather than informative.

The trickier case is anything involving percentage change on a small base. A division that grew from $200,000 to $600,000 technically "grew 200%," and a bold arrow-and-percentage graphic will make that look like the headline of the year — even when the division is still immaterial to the company as a whole. This is where a designer's instinct to make a number visually exciting works directly against the report's job, which is to represent scale honestly. If a number needs decoration to look impressive, that's usually the moment to leave it as plain text next to the number it's being compared to, not the moment to reach for a chart template.

Where visuals genuinely earn their space is dense comparative data — segment performance, regional breakdowns, multi-year trends — the kind of content a layered chart layout built for quarterly and annual review data is meant to carry, because it's structured to hold several data points at once without forcing the reader to hunt for context.

The shareholder letter is not the place to summarize the report

It's tempting to treat the opening letter as an executive summary — hit every division, mention every initiative, end on a forward-looking note. Read enough of these back to back and they start to sound identical, because "summarize everything" produces the same flattened tone regardless of what actually happened that year.

A letter that names one real tension from the year — a market that didn't behave as expected, a bet that hasn't paid off yet, a trade-off the board is still weighing — reads as more credible than one that's uniformly upbeat, and it also gives the rest of the report somewhere to go. The financials then answer the question the letter raised, instead of just restating what the letter already said. One thing people overlook here: the letter is usually the only part of the report written in a human voice, so if it reads like it was assembled from the same status updates as the financial section, that's the one place readers notice.

The numbers section has one job, and design should mostly get out of the way

This is the section where I'd push back hardest against decorating for decoration's sake. Once you're past the highlights page and into the actual statements — income statement, balance sheet, cash flow — the reader wants a table, not an illustration of a table. Consistent column alignment, clear subtotals, enough white space between line items to track a row across the page: that's the entire design job here, and it's easy to underrate because it looks like "no design" happened.

Where narrative framing genuinely adds value is right before the raw tables — one paragraph, in plain language, explaining why the year's numbers moved the way they did, written by someone who understands the business rather than someone reformatting a spreadsheet. If you're pulling this section together from an existing set of financial documents rather than starting from scratch, a structured Word template for financial statements and budget reporting at least keeps the formatting consistent across sections that were probably drafted by three different people in three different files.

Print, PDF, and the internal deck version rarely need the same layout

Most companies end up producing the annual report in at least two formats — a print or PDF document for shareholders, and a condensed slide version for the board meeting, all-hands, or investor call where someone actually presents the highlights out loud. Treating these as the same content reflowed into a different template usually produces a bad version of both: the print document loses density trying to look like slides, and the deck ends up overcrowded trying to preserve everything from the print version.

The deck version should be ruthless about what gets cut — three to five key metrics, one growth story, one risk or challenge acknowledged honestly. A KPI-dashboard-style presentation layout built for reporting results out loud works here specifically because it's structured for someone standing in front of the numbers, not someone reading them alone at a desk — the difference matters more than most teams plan for until they're rebuilding the deck the night before the meeting.

The review cycle is a design constraint too

Legal, finance, and the executive team will all touch this document before it ships, usually in that order, usually with each round undoing some of what the previous round approved. Building the layout so that late-stage number changes don't cascade into redesigned pages — using tables that expand cleanly, avoiding hand-placed text that breaks when a figure gets one digit longer — saves more production time than any single stylistic choice will.

None of this is glamorous advice. But an annual report that's still being laid out two days before the board meeting because a single revised figure broke four pages of formatting isn't a design failure exactly — it's a planning failure that shows up as a design problem. Build for that eleventh-hour correction from the start, and the rest of the document gets easier to defend when someone asks why a number looks the way it does.