If you're looking to hire a development firm to build you a mobile or web app, this Quick Reference Guide is a must-have.
Design systems are common to most large organizations, or at least they should be. A quick Google search will bring you to multiple articles about why your business will burn to the ground if you don’t have a design system in place, but in this article, we’re going to focus on the realities of implementing a design system. The question today is not “what is a design system?” but “how do I adopt one?”
Okay so maybe not burn to the ground, but it’s important to understand that every organization with multiple product contributors will eventually need something to help ensure that the work they do is consistently executed. For small organizations, this is usually some sort of Creative Director or Development Lead who is responsible for articulating the company’s vision and/or technical strategy. However, eventually, one person isn’t enough to keep all the little design and dev ducks in a row.
Design systems are a set of reusable components, patterns, guidelines, and standards that we implement to act in place of a director as a single source of truth for an organization’s product teams. The fact of the matter is that it doesn’t matter how brilliant your design, development, or content teams are; unless they’re sitting on top of each other in the office (now we’ve put that image in your head), they are human and they will make different decisions about how a product should be executed if standards are not in place. If you expect your products to remain consistent throughout your organization, you need to provide guidance and support to the people of your organization.
Recently Paper Leaf partnered with Alberta Blue Cross® to support them in implementing a large-scale design system that would eventually serve over 300+ employees.
“We knew that we needed a design system,” says Shaista Ali, the COE manager, digital experience with Alberta Blue Cross®. “We also knew we didn’t have the capacity to tackle it alone. We have exceptional designers, developers and digital strategists, but these folks are always fully resourced to ongoing projects.”
Alberta Blue Cross® wanted an outside perspective and industry expertise. The Paper Leaf team was composed of designers with experience building and working on a variety of products across industries.
“We knew they wouldn’t be biased towards existing products at Alberta Blue Cross®. Working with Paper Leaf provided us access to a robust team with experience in product strategy, design, and development, and gave us the opportunity to build maturity in our own team as we worked together.”
The first step you need to take is determining the scale of what you need in a design system, and deciding if your internal team has the capacity to carry it out. A small shop with one or two designers doesn’t have the same communication challenges a large organization has, so the effort of implementing a full-scale design system may outweigh the benefits.
If you’re not sure, take a moment to think about the following:
This is where external support can be beneficial to not only get the research done quickly but ensure that the decisions made are objective.
Don’t sleep on the importance of research! In the first phases of our project with Alberta Blue Cross®, our research was extensive. We interviewed nine different teams, performed competitor research, audited and tested key products, and developed technical strategies, rollout approaches, and governance models.
By the end of discovery we had a big pile of research and an even bigger pile of challenges the Alberta Blue Cross® teams were experiencing. This part is often forgotten, and as an unbiased partner, we are able to complete research objectively to deliver as much value to the organization as possible.
When we say useful, we mean a practical tool that answers the challenges you uncovered during your research phase. For some, a well-crafted user interface kit will be enough when you’re just starting out, and for others, a more robust tool is called for.
For Alberta Blue Cross® we needed an accessible and scalable tool that would not only demonstrate how the brand should be applied, but how components should function. We customized the open-source platform Storybook to create an online hub for the Alberta Blue Cross® system, along with a robust Figma component library that their designers and UX strategists could use to create quick and consistent product mockups.
Every component was coded and deployed to a sandbox environment so that teams can interact with and test the components as needed. Storybook also provided us with a clean way to display supporting documentation.
The design and build phase was a true collaboration between the Paper Leaf and Alberta Blue Cross® Design teams. Unlike typical product builds, part of our consultancy not only included executing on the framework for the system but supporting Alberta Blue Cross® in learning how to manage it independently.
Once you’ve got your system built comes the hard part, getting your organization to accept change! 😱 The amount of process change required will differ from company to company, but it’s completely reasonable to expect at least a small amount of pushback when messing with someone’s established workflow.
Your team will have questions about how the design system will impact their roles, and what will be expected of them, so a well-thought-out change management strategy will be key. Here are a few of the things you should consider to help your team get to know their new design system friend:
*AMA = Ask Me Anything
You should be starting to develop your governance plans during your research and discovery phase since “those who fail to plan, plan to fail” and all that, but blog articles like ordered lists so here we are. There are four stages of design maturity, and stage three is called “surviving the teenage years” for a reason. It is when the acne usually emerges and your patience is really put to the test.
A governance model is what will keep your design system healthy and your team happy as you all navigate DS puberty and reach successful mass adoption with a system that’s all grown up and continuing to evolve over time.
Here are some ideas to consider:
Just in case you scrolled to the bottom without reading the whole article, here is the summary:
A lot of work to implement? Yes. Worth it though? Definitely. Design systems may require a bit of sweat and tears to implement, but once you have one in place, they make product updates faster and more efficient and foster creativity by eliminating guesswork when it comes to base components.
Connect with us below, and let’s explore how to create a more cohesive and efficient design process together.