Design System Governance
As we already know, design systems have become an unavoidable tool for organizations to maintain consistency and efficiency in their design and development process. But, more is always needed to have a fully functional design system. Therefore, there needs to be more than just a set of design components and guidelines.
Enters design system governance. First, what is design governance?
It is the process that prevents poor design decisions. It is a process that helps us keep track of progress and defines a set of steps we need to take when we encounter specific issues (e.g., the product team cannot find or cannot use particular components). And as always, no rule fits all. You discuss it with your team, and it is up to you to define your processes.
If you haven't thought about this before, let's break down the process. At some points, the product team comes with a request for the design system team about a specific component that is not part of the system yet, so that should be taken into consideration also. Questions that I like to start with:
Is this a valuable component?
Is this component being used?
Can this component be easily found?
Does this component need an update?
Does this component even exist? etc. etc...
Each question is connected with the following action you need to perform. To try and keep this post simple and to the point, since we have an attention span of a goldfish, I will try to mark up some baseline flow:
Product team request
Component issue
Define problem
Communicate solution
Design component
Review component
Have designer-developer meeting
Develop component
Review again
Test component
Iterate if needed
Create documentation and stage for the release
Launch component
Brad Frost has this flow defined here if you want to dive into more details.
Having this process defined is essential for ensuring the design system remains consistent and adequate. Nathan Curtis notes that governance is about establishing a clear structure for decision-making, outlining roles and responsibilities, and ensuring that the design system is aligned with the organization's goals and values. Establishing governance from the beginning is essential so everyone will be on the same page.
Putting in more effort at the beginning will save much of your time later.
To build and maintain a successful design system, it is crucial to consider documentation and governance from the outset. Here are some best practices for getting started:
Start with a clear purpose
Before you begin creating your design system, it is crucial to understand why you are building it and what you hope to achieve. This will help ensure that your design system is aligned with your organization's goals and values and will make it easier to prioritize your efforts.
Involve everyone
Design systems should not be created in isolation. Instead, involve all stakeholders, including designers, developers, product managers, and stakeholders from other departments, in creating and maintaining your design system.
Select clear governance
As mentioned, governance is crucial in ensuring the long-term success of a design system. Establish clear decision-making processes, outline roles and responsibilities, and ensure that everyone involved in the design system understands how decisions will be made.
Document everything
Make sure your design system documentation is comprehensive and up-to-date.
Continuously iterate
You will never have your design system finished. It is like a baby that requires constant attention. You will need to refine and iterate on it constantly. Review it with your team and make necessary changes to ensure consistency meets your goals and values.
Knowing this, in theory, is excellent, but acquiring some practical skills can be tricky. It can be tricky for various reasons we are all familiar with, such as poor communication, people not interested in following processes, needing more time for that, etc.
Be patient, my child. At some point, things will come to their place. I always ask myself, "What can I do now with what I have?". It is essential to communicate with the whole team and explain the pros and cons of some of the approaches. Don't just give up and let it be. Remember, having a solid base for everything goes a long way.
Stay healthy! Cheers!
Let me know what you think. And ofc clicking that subscribe button means a lot!