Getting legal, compliance, and design to agree on the same sentence, before it shipped

Situation

Federal content has three approvers who rarely agree: an accessibility standard, a legal or compliance reviewer, and the person actually trying to complete a task on the page. Most projects treated those as sequential hurdles, so content got rewritten three times by three different people, on federal and commercial engagements running on Agile and SAFe timelines. Nobody owned the words, and rework ate the schedule.

Approach

I built the standards teams needed to stop guessing: content audits across the affected products to flag what to keep, revise, consolidate, or cut, then voice and tone guidelines and a style guide that became the shared reference, not just documentation nobody opened. I sat directly with legal and compliance reviewers on federal engagements so 508 and regulatory requirements got resolved before launch, not after. And because a lot of our schedule slippage traced back to unclear project scope, I co-led an intake framework that made teams answer the hard questions on day one instead of week six.

Outcome

The guidelines got adopted across design teams, not just used once and shelved. Scope ambiguity dropped 70%. Across more than 40 initiatives, we hit a 100% on-time delivery record and 90% stakeholder satisfaction — numbers I still track, because "the client didn't complain" isn't actually a metric.

• 40+ design and content initiatives delivered, 100% on time
• 90% stakeholder satisfaction across engagements
• 70% reduction in scope ambiguity from the new intake framework