Content Design Assessment

Building the case for content design in a federal service rebuild: I assessed the content ahead of the rebuild and made the case for including it in the roadmap. Through evidence, plain-language examples, and clear effort estimates, I delivered a practical plan that helped a Product Owner (PO) who's new to UX understand the benefits of improving content before launch.

Role: Senior Content Designer
Team: Product owner, UX designers and researchers, accessibility specialist, business analysts
Methods: Content audit, plain language, Canada.ca Content Style Guide, WCAG, effort estimation, before-and-after examples

Project details

A federal digital service was being rebuilt on a new technology platform, and content wasn’t part of the roadmap. The product owner was new to UX work and cautious about bringing content design into the project. I wanted to show where content fit in terms she could weigh for herself.

The challenge

How do you make the case for content design to someone who hasn’t worked with UX before? I couldn’t rely on shared vocabulary or assume the value was obvious. The case had to be about effort, timing, and risk to users.

My role

As the Senior Content Designer, I was responsible for: 

  • Conducting a content audit
  • Aligning with Canada.ca Content Style Guide and WCAG requirements
  • UX improvements and plain language rewrites
  • Effort estimation

Approach

  • Start with evidence the team already trusted. Four separate analyses (a content audit, a UX design review, a UX discovery summary, and an accessibility analysis) had flagged the same friction points. Across the 28 pages reviewed, content was creating avoidable effort for users.
  • Anchor it in a standard, not an opinion. The Canada.ca Content Style Guide is mandatory for public-facing digital services, so this was a compliance matter as well as a quality one. The guide already defines what “good” looks like, so we didn’t have to.
  • Make the effort visible. I sorted the work into two tiers. Rule-based fixes (shorter sentences, active voice, consistent terminology) take about 15 to 60 minutes per screen and need no research or SME input. Rewrites for top tasks take 1 to 2 hours per screen and need SME input and an accuracy check. Both were draft estimates for discussion.
  • Show, don’t tell. A before-and-after example used the same policy information. In the “after,” important information moves out of a collapsed section and into a heading, and the text is rewritten in plain language addressed to “you.” The text went from 80 words to 59, but the point was to reduce effort for users, not just to shorten it.
  • Offer a partnership, not a takeover. I proposed four steps: include content review in each screen’s definition of done, apply rule-based fixes everywhere, prioritize rewrites by the screens users rely on most, and start shared decisions early (the landing page, card sorting, terminology, and the public-facing name of the tool). None of it required new functionality.

Outcomes

  • The product owner accepted the proposal.
  • I developed a list of 100+ content fixes for PO approval and implementation by developers.
  • Hesitation about a new discipline is usually about unfamiliarity and risk, not opposition. When I made the effort, timing, and benefit visible, the conversation became practical.

Tools and methods

  • Content audit and page-by-page recommendations with supporting rationale
  • Cross-functional collaboration with UX Research and Design, as well as subject-matter experts
  • UX writing and content design principles
  • Style guide alignment
  • Figma, M365

‍

Project snapshot

View the deck that was presented to the product owner for buy-in and scoping. Note the file has been anonymized and access is password-protected. Explore the deck: Content Design for a Federal Digital Service.

Back to Projects

LET’s CONNECT

emmastephenfucci@gmail.com‍

Scroll down for the contact form.