Shared Secrets
Designing order

Designing order

Is it just us or is everybody suddenly talking about design systems?

More and more of Humbleteam’s clients don’t just want to build a product, they want a design system that can help them maintain and evolve that product on their own.

But just creating a design system isn’t enough. You also need to make sure that the designers working with it in the future understand how the system works.

We have four ways to make sure that a design system handover is successful:

  1. General Guidelines
  2. Project Onboarding
  3. Formalist, our Figma Plugin
  4. Checklists

Let’s go over each of these.

#1 Guidelines!

A design system is essentially a set of rules. To help designers implement these rules, Humbleteam creates a detailed set of guidelines with every design system that we ship.

Every designer who works with the system gets a copy of these guidelines, as well as an onboarding session to help them get started.

Some rules are generally applicable to all of our design systems. Humbleteam’s designers start working with these immediately when they join the company.

Other rules are specific to particular projects. These usually cover the following elements:

  1. Structure of the design system file
  2. Structure of the components page
  3. Structure of layers
  4. Rules for setting up and using auto-layout
  5. Rules for using instances
  6. Rules for creating a component

We launched
a podcast!

Each episode of CTRL SHIFT follows the story of a business or industry that did a full 180, and the drama that ensued.
Tune in

#2 Onboarding!

When a designer starts working with a new design system it’s easy to make mistakes. To help avoid them, we create an onboarding process where we go over the following points:

  1. Creating wireframes
  2. Flow file structure
  3. Creating a component
  4. Preparing a file before submitting it to development
  5. Project features (e.g. typography, colors, icons, illustrations, etc.)
  6. Creating a flow

For each of these items we attach a Loom video, so a new designer can not only read about these things, but see them explained by a more experienced designer.

#3 The Plugin!

This is where it gets interesting.

We noticed that there were two big problems related to design systems that consistently came up:

  1. Lack of oversight. With so many rules to keep track of, it’s easy for even the most experienced designer to get lost in the details, and start making mistakes.
  2. Disorder. Intense pressure from deadlines tends to push good housekeeping to the wayside. Designers keep postponing the difficult task of organizing to a more convenient later date that never actually comes. Short-term fixes lead to long-term waste.

To address these problems, we tried to automate the process of checking and correcting layouts, by creating our own Figma plugin.

The idea behind it is simple, and based on what software engineers call a linter: The plugin runs through a list of rules, checking the Figma file for errors. If the designer has, for example, forgotten to name layers, use Figma styles, or fractional coordinates, the plugin will hunt them, find them, and help fix them.

Designing Order. Image1

We soon realized that this plugin could be useful for other designers, so we added new features and, voilà — Formalist for Figma was ready for the world.

How Formalist helps:

  1. We notice errors that we’d otherwise have overlooked.
  2. We’re able to fix errors automatically, and right away. (For example, we found in the working layouts the use of a component with a remote parent. If it is not found, then sooner or later you will have to redo many interface elements manually, instead of a couple of clicks. It would be hard to catch with a normal eye if you do not click through each layer.)
  3. The quality of our layouts has increased, with all screens subject to a single structure before being transferred to development.
  4. We estimate that we save from 3 to 10 hours every month by reducing the time for reviewing layouts and fixing errors.

Bonus advantage: Perfectionists are 200% happier now.

White loudspeaker
Next email:

The story about the scientific exodus to business

Get exсlusive startup secrets right in your inbox!
Hands

Thank you! You're officially a part of our secret community.

#4 Checklists!

When the flow is almost ready, designers use a checklist for final quality assurance. It’s still necessary to do this manually because some of the checks can’t be performed by the plugin.

Here’s one example of a checklist:

Designing Order. Image2

Over to you!

So, that’s how we at Humbleteam maintain order in design systems. We hope this has been helpful.

If you’re facing the same problems, do check out the Formalist Plugin on Figma Community.

For even more features, try out Formalist Premium on Gumroad. (Use the promo code "2jfadmd" to get the first month free.)

Want a demo? Email the developers at [email protected].

The article was written by our designer Nikita Bryuzgin. Thanks for reading!

Subscribe to hear about legendary business pivots on our CTRL SHIFT podcast.

Share