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

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.

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.


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.
