Shaw Redesign and Replatform

Background

The Shaw project was a complete eComm site redesign and replatform where we were empowered to imagine the new space telcom's could operate - it was super interesting to be constantly evolving the content of the site to hit the moving target of that industry vertical. Our challenge was simplifying a technical product line, accommodating multiple user types from veteran technical users to new and less technical users and giving them the support and tools needed to feel confident in their purchases.

Process

Our process began with conceptual pitching where we had the flexibility to work directly with our Product Owners, craft a vision and helping define a product roadmap. This experience was where I learned Agile methodology and also was able to attend Agile training through the lens of User Experience.

My role on the project revolved around creating the new Shaw Design System with ideation, building, managing and maintaining the system. In this role I focused on technology and it's partnership with User Experience in managing how the new Shaw CMS flexed and adapted to component variations, states and custom options. This project grew my interest in design systems and helped shape how I consider consistency, governance and reusability in my UX craft.

Another large aspect of this project was the in-depth inclusion of accessibility. We worked on a framework for building components keeping accessibility as a defining requirement. Our documentation was extensive as each component was concepted, designed and slotted into the design system. My knowledge of accessibility came from the research that went into making each component flexible and accessible.

Closing thoughts

As a UX designer Shaw was a rich platform to help build my design system knowledge, accessibility craft and help build a foundation for Agile methodology. A large takeaway for me is merging this passion for Design Systems with an Agile methodology - because of the extensive documentation process some context fell through the cracks, especially when communicating with developers. There was just too much documentation to consume it all quickly.

Later in my career I started using a more agile approach where there was less documentation but it was more meaningful per component or design. Keeping annotations concise and using more face-to-face conversations can prove to be more efficient in a collaborative process.