Designed to Be Read

Designed to Be Read

  • 3 min. read

Typography for project managers, the overlooked skill that quietly moves projects forward.

Every stakeholder reads your document before they read a word

Before anyone processes a single sentence of your status report, they run a three-second visual test: does this look like something worth trusting? Win that test and your content gets a fair hearing. Lose it and the best analysis in the company gets skimmed, doubted, or quietly set aside.

Designed to Be Read is a practical handbook that teaches project managers to use typography as a project-outcomes tool, not decoration. The thesis is simple: how a document looks changes whether it gets read, believed, and approved, and that is squarely a PM's job.

This is deliberately not a design book. It's a project-outcomes book that happens to be about type: faster sign-offs, fewer misreads and reworks, more credibility, and less cognitive load on the people you need a "yes" from.

Built for the tools you're actually allowed to use

Most typography advice assumes InDesign, a font budget, and a free hand. Real project managers work on locked-down machines with a mandated brand and only Office, Google Workspace, and Jira to hand. So this book is constraints-first from the first page to the last: every technique works with the fonts you already have, inside the software IT lets you run. No InDesign. No font installs. No choosing your own brand. Just better documents from the exact tools on your screen right now.

Get the book

Companion templates and specimens at giovannitoccu.com/typography4pm →

Available as a paperback (7×10 in) and a reflowable EPUB. ISBN 979-8-18683536-3 (colour edition).

What you'll learn

  • The business case for type, the ROI argument that justifies (and defends) ten extra minutes on a document.
  • Just-enough fundamentals, the ten terms that actually matter, hierarchy, readability, and safe pairings inside a brand you didn't choose.
  • Accessibility as a requirement, contrast, size, spacing, line length, neurodiversity, and localization, framed as the compliance obligation it often is.
  • The core artifacts, fixed, status reports, SOWs, RAID registers, budgets, timelines, decks, dashboards, and everyday email, Slack, and Teams.
  • Typography inside real PM tools, Word and Docs Styles, Confluence, Jira, and Excel, plus cleaning up AI-generated documents.
  • Consistency that scales, a one-page team style guide, enforceable templates, handling pushback, and typographic KPIs that prove the ROI you promised in Chapter 1.

Who it's for

Constrained corporate project managers, the people running real projects on someone else's machine, someone else's brand, and someone else's approved software. If your job is to get a document read, believed, and signed, this book is for you.

How it's built

A single fictional-but-realistic running example, "Project Meridian," a mid-size ERP rollout, threads through every chapter, so the same status report, deck, and dashboard visibly improve as you read. Every chapter carries a signature before/after case study and cites the real sources it stands on, Butterick, Lupton, Tufte, WCAG 2.2, Section 508, and more. And because it's a book about typography, it's judged against its own advice: right-vs-wrong specimens are shown, not just described.

What's inside

Eleven chapters across four parts, bookended by an introduction that turns skepticism into buy-in in five pages and a conclusion with a 30-day implementation plan.

Part I: Foundations

  1. The Business Case for Typography
  2. Typography Fundamentals for Non-Designers
  3. Accessibility, Inclusion & Cognitive Load

Part II: The PM's Core Artifacts

  1. Project Documents That Get Read
  2. Presentations & Slide Decks
  3. Data, Charts & Infographics
  4. Everyday Written Communication

Part III: Working Inside Real PM Tools

  1. Typography in the Tools You Actually Use
  2. First Impressions & High-Stakes Documents

Part IV: Scaling & Governance

  1. Building Typographic Consistency Across the Team
  2. Measuring Typographic Effectiveness

Back matter

  • Conclusion: Typography as a PM Competitive Advantage, one-page takeaways and a 30-day plan
  • Appendices A–F: a pre-send checklist, safe font pairings and system-font fallbacks, recommended tools, a copyright/licensing/font-permission guide, a glossary, and curated further reading

Ten extra minutes on a document. Read, believed, approved. That's the whole trade.