How I brought clarity to Canada Post's error messages—and why "just fix the copy" wasn't enough—Catherine Bryce Skip to main content
Catherine Bryce Knowledge systems · Information architecture · AI enablement

How I brought clarity to Canada Post's error messages—and why "just fix the copy" wasn't enough

Problem

Every team wrote error messages their own way. One product apologized at length; another just said "Oops."

My role

Content designer; facilitated workshops with UX writers across Canada Post.

The decision

I was asked to polish a few messages. I proposed a shared framework instead, so the inconsistency wouldn't return.

Result

One framework for categories, tone and templates, used by writers across products.

Before: three voices for one failure

Side-by-side audit of inconsistent Canada Post error messages
Same company, same moment of failure, three different voices.

The hard call: widen the scope

Error messaging wasn't on anyone's roadmap, so I used an audit to make the case. I then brought it to the Content Operations team and facilitated workshops: what makes an error helpful, where users get stuck, and what tone fits when something goes wrong.

Workshop exploration of apologetic error copy
How much apology is too much?

The framework

Every error gets a why and a what's next. Severity decides the treatment: inline, detour, or block. Tone: empathy when needed, clarity always.

Matrix mapping error severity against inline, detour and block treatments
Severity against treatment.
Error messaging framework with categories, tone and templates
Categories, tone principles, and templates.

Results

  • UX writers had shared patterns instead of guessing.
  • Cross-functional teams used the same terms for error types.
  • Users hit fewer dead ends.

What I'd do next: put it in Figma

Adoption was limited because the framework lived in documentation, outside product and design workflows. This concept builds it into components: writing prompts for title, body and action, with variants that change by severity.

Figma component library for error messages with variables for title, body and action
Concept: error components with built-in writing prompts.
← All projects Next: Email best practices walkthrough →