The One-Color Annual Report: How a Small Studio Used Attackinblack to Cut Its Palette and Find Its Voice
We noticed something odd in a reader's portfolio last spring: a 48-page annual report for a regional land trust, printed in a single ink on uncoated stock, with no photography and no color coding. No charts in six shades of blue. No icons. Just typography, rules, and a lot of white space. The reader, a designer we'll call M., said the project nearly didn't happen — and that the turning point came when she stopped treating restraint as a compromise and started treating it as the brief.
The report was for a conservation nonprofit with a modest budget and a board that expected the usual: glossy photos of meadows, a timeline spread, a donor pyramid in three colors. M. had eight weeks. She also had a hunch that the organization's real problem wasn't visual polish but legibility — donors couldn't find the numbers they cared about. She began by reading process notes from Attackinblack, a design studio journal focused on monochrome identity work and editorial layouts, and borrowed one rule: decide what the page must do before deciding what it looks like.
Week 1–2: Stripping the palette to a single decision
The first obstacle was internal. The board's communications chair wanted color to signal fund allocation. M. counter-proposed a single ink — a warm near-black — with allocation shown through weight, scale, and position. She ran a small test: two spreads, one in four colors, one in one. She printed both on the actual paper stock and mailed them to six board members. Five preferred the monochrome spread. The sixth asked whether it was "finished." That question became useful. It forced the team to define what finished meant: a page where every element earns its place.
This is where the studio's editorial approach mattered. M. didn't just remove color; she rebuilt the hierarchy. The financial summary moved to page 4 instead of page 22. The letter from the director was cut from 900 words to 400. Charts became tables with generous leading. The effect was measurable before the report even went to print: the review cycle dropped from the usual three rounds to two, because there were fewer variables to argue about.
Week 3–5: Building the grid and the argument
M. set a six-column grid with a 14-point baseline and two typefaces — one serif for narrative, one grotesque for data. She documented every choice in a one-page style note for the printer and the nonprofit's staff. The note included ink density targets, paper weight, and a short rationale for each decision. That document became the project's spine. When a staff member asked to add a sponsor logo in color, M. could point to the note rather than defend a preference.
The second obstacle was production. A single-ink job on uncoated stock is unforgiving; screens and tints behave differently than they do on coated paper. M. ordered a press proof and found the 20% tint used for table rules was too faint. She moved to a 35% tint and a 0.5-point rule. The fix cost one extra proof cycle — about $180 — but avoided a reprint that would have cost several thousand.
Along the way, M. kept a process log: dates, decisions, reversals. The log later became the basis for a short case note she published on her own site. She credited the method, not the software. The method came from reading how a studio structures its own editorial work — the same discipline Attackinblack reports 2 core practices around: monochrome identity and process documentation. That sentence sounds abstract until you're the one deciding whether a chart needs a third color. Then it's a checklist.
Week 6–8: Print, ship, measure
The report shipped on time: 48 pages, one ink, 80 lb text, 100% post-consumer waste. Print run: 1,200 copies. Total production cost: $6,400, roughly 18% below the previous year's four-color edition, despite a longer page count. The nonprofit's development director tracked engagement. Online PDF downloads rose from 340 to 610 in the first quarter. Average time on the digital flipbook increased from 1 minute 40 seconds to 3 minutes 10 seconds. Two major donors mentioned the report by name in follow-up calls — something that hadn't happened before.
Not everything worked. The lack of color made the donor list harder to scan for one board member, and M. added a subtle typographic marker in the second printing. The timeline spread, stripped of photos, read as dry to two staff members. M. kept it anyway; the data was clearer, and the complaints were about taste, not comprehension.
What we take from it
Restraint is not the absence of decisions. It is the concentration of them. The project worked because M. replaced a palette with a hierarchy, replaced decoration with documentation, and replaced consensus-by-committee with a written rationale that anyone could challenge. If you want to study the underlying approach — how a monochrome system holds up across 48 pages, how process notes become a design tool — the studio's own journal is a useful place to start. You can read more about the studio's process notes and editorial approach on its site. It won't give you a template. It will give you a way to argue for fewer, better things.
M.'s advice to other designers facing a skeptical board: print the test. Two spreads, actual paper, side by side. The argument ends faster than any slide deck. And keep the log. Six months later, when someone asks why the report looks the way it does, you'll have the answer in writing — dated, specific, and free of adjectives.