You’ve crafted a meticulous DesignOps document on Confluence. But here’s the thing: Who’s reading it? If you’re constantly reminding designers to follow the guidelines or, worse, keeping them from reinventing the wheel, there’s a better way.
The secret? Turn your process into a checklist. It’s simple and actionable. Each check is a mini victory for your designer and, in return, gives you a live status update on the project. Everybody wins!
That’s where Compfeed comes in – a DesignOps tool that lives inside Figma, designed to make checklists not just helpful but easy and fun to use. Imagine your design team enjoying the process of ticking off steps. With Compfeed, it’s not just possible; it’s practically inevitable.
To give you a head start, we’ll share how you can best convert your DesignOps document to a checklist.
Governing Contributions
Include specific questions as checks. For instance, did the designer try to use existing components first? Are the changes well-documented? These checks help in maintaining the integrity of the design system.
Outlining a Process
Start by organizing the phases and checks in logical order. This ensures a smooth workflow and helps visualize the entire process from start to finish
Ensuring Quality
Make sure every new contribution meets the defined quality standards, whether in naming conventions, the use of auto layout, or aligning properties with development.
Navigating Different Processes:
New vs. Evolving Design Systems
Not all design systems are created equal. The process will differ depending on whether you’re working with a new or evolving system.
Brand new Design Systems
This isn’t like a blank canvas. The focus is to consolidate all the variations you can find of buttons, checkboxes, modals, and such to define one clear Status Quo component. Your primary task is to remove discrepancies and establish a consistent foundation.
What is the Status Quo?
The Status Quo is the current accepted state of a component following the defined process. Establishing this baseline is the first step in a new system.
Evolving Design Systems
Conversely, an existing system already has a defined Status Quo. The focus here shifts to consolidating features, ensuring that new contributions still support the existing use case and align with the established standards.
