Post
Notes From a Recent Planning Session
A concrete post with a clear subject and real-world context.
Last week we sat down with the editorial team to review the upcoming quarter’s workload. The agenda was straightforward: three industrial manuals, one internal policy update, and a corporate dossier that had been sitting in draft for six months. What came out of that session was a clearer picture of how we approach document structure, and why small decisions in layout can save hours of rework later.
The first item on the list was a 200-page equipment operation guide. The client had sent a Word file with inconsistent heading levels, embedded tables that broke across pages, and no clear hierarchy between warnings and standard notes. We discussed whether to rebuild the entire style from scratch or adapt their existing template. The team agreed that a full restructure would take longer upfront but would reduce revision cycles by at least two rounds. That tradeoff — more time now for less time later — became a recurring theme.
The second manual was a safety protocol document for a chemical processing facility. Here the challenge was visual: how to make critical hazard information stand out without overwhelming the reader. We decided to use a single accent color for all warnings, paired with a consistent icon placement in the margin. The goal was to create a system where a field operator could scan a page and immediately locate the actionable instruction, even under low light or time pressure.
The corporate dossier was a different beast. It contained quarterly performance data, strategic recommendations, and board-level summaries. The original layout was dense — single column, small type, no pull quotes or data breaks. We proposed a modular grid that separates narrative sections from data panels, allowing readers to choose their own path through the document. The client’s feedback was immediate: they wanted to test it on the next quarterly report.
What stood out from the session was how often the same questions came up: Who is the primary reader? What is the most common use case? How much time does someone have to read this? Answering those questions first made every subsequent decision — from type size to margin width — feel less like guesswork and more like design with intent.
We ended the session with a list of action items: finalize the equipment guide template by end of week, send the safety protocol mockup for client review, and schedule a follow-up call for the dossier. The next post in this series will cover what happened when those first drafts came back from the client.