Loblaw Digital content design guide

An extension of the Loblaw Design System project, serving as a resource for all teams.

Role

  • Proposed the concept, conducted research, wrote, and iterated on the guide while leveraging resources and industry standards

  • Engaged with design leadership to secure buy-in and ensure alignment

  • Worked with design leads to raise awareness through presentations and collaborated with team leads to integrate the guide into design workflows

Goal

  • Establish a centralized hub for content best practices, rooted in accessibility and inclusion, to educate and support product and design teams

  • Define core values and a strong foundation to advance content design within the organization

  • Collaborate with the Design System team to integrate content examples into component work

  • Enhance the customer experience by ensuring all people can engage with our products without barriers, regardless of ability, identity, or lived experience

Impact

  • Presented to 400+ colleagues to raise awareness and build skills

  • Created a centralized resource to help non-writers develop confidence and improve messaging consistency across platforms

  • Increased awareness of inclusive language, leading to better products

  • Established an accessible, organization-wide source of content best practices

Here are some examples of the guide. Right now, it’s an internal resource.

 
Principles. Table of contents. Be simple and direct, Only provide what’s essential, Conversational writing, Don’t drop the connecting words, Focus on key concepts, Write for all reading levels, Reduce friction, Be consistent, Write in present tense,…
Only provide what’s essential. Ask yourself, what’s the main point of the message you’re writing? Yes - To complete 2-step verification, you’ll get an email. This can take up to 5 minutes. No - Your email needs to connect with our servers to complet…
Reduce friction. Think about what would stop a user. Could they be concerned about something? Will they have trust issues? Are we asking for too much without explanation?   Use text labels to make users feel safe. Nip the negative feeling before the…
Active instead of passive voice. The active structure focuses on the person. Yes - We’re investigating the problem, Select add to cart to buy, How would you like to pay? No - The problem is being investigated, The add to cart button should be select…
Can, may and might. Terms of ability. “Can” implies ability and “may” implies permission (and sometimes uncertainty). Don’t use “may” when you mean “can.” Yes - You can change your personal information at any time, You can use PC Optimum offers up t…
Login vs. Log in. Use login when referring to the page or process. Yes - Head back to the login page and try again, Go to account settings to change your login details. No - Head back to the log in page and try again, Go to account settings to chang…