Type Synth | Amy Keeney

Microsoft Account Notice

A one-time transparency notice explaining how account-associated data works across the Microsoft ecosystem, shown to every Microsoft account holder — over a billion people. I led the writing across surfaces (Windows, Office, mobile). The work took 18 months.

The genesis of a notice shown to billions of people

Microsoft's account-related data practices live across an ecosystem: Windows, Office, Xbox, Outlook, and more. Historically that landscape has been described in different places, in different voices, with different framing. The Microsoft Account Notice was the moment to harmonize — one shared explanation of how the system works, sent to everyone with an account.

The work

I owned every word, and the structure, voice, and strategy that produced it. The notice itself was the visible artifact; the work behind it included:

  • Writing for over a billion users, across reading levels, contexts, and languages.

  • Translating legal and regulatory requirements into plain English that wouldn't read as legalese.

  • Tailoring the notice for Windows, Office, and mobile while keeping the voice and structure coherent.

  • Designing regional variants to meet regional requirements.

  • Holding the voice line through 18 months of stakeholder review, dependency wrangling, and revision.

Stakeholders

Alignment required, by a rough count, nine separate functions: regulatory, legal, product, engineering, design, brand, content design, business planning, and product management.

Add to that executive review at the highest levels, including the CEO himself.


A writing project at this scale isn't really a writing project. It's a coordination project with words at the end.

Outcomes

The notice shipped on time and met the business goals it was set against. Read-through rates were high, which suggests the copy itself was working.

Users also reported confusion, particularly around visual treatments that hadn't yet rolled out across the ecosystem. The novelty of the visual was a friction point, even when the content carried people through it.

Less visible but more enduring: the project shaped the infrastructure for cross-ecosystem notice delivery and tracking — which users had seen which notices — for everything that came after.

What I learned

Plain language at this scale is partly a craft problem and mostly a political one.

The harder fight isn't writing the line; it's defending it.

Copy can carry people through unfamiliar visuals, but it can't make visuals familiar on its own. Visual newness has its own friction curve, separate from content quality.


Sometimes the most senior thing you can do is let go of a choice you believe in, gather the data, and earn it back. "Pick your battles" is incomplete advice; the harder skill is staying ready to fight the same battle twice.