A design library is a collection of guidelines and standards that describe a design system and maybe template assets to go with it. Creating a library for an experience of any scale is no trivial matter. It’s not like you open up a code editor, chop things up, throw a ZIP file to some marketer and say, “Here you go. Enjoy!” You’ve got to have a plan.
So, let’s assume you’ve done due diligence: your design system is stable and mature, and you’ve answered all the
right questions to justify the effort. You are ready to get started.
The process of creating a library involves many different activities across four sequential phases:
Once you’ve broken down the plan into four chunks, it’s easier to focus the conversation on specifics: individual activities that may be obvious (documenting guidelines) and what’s not (oh, yeah, you’re right, I need a communications plan!).
The Creating a UX Design Library diagram (downloadable as a tabloid-sized PDF resizable for poster printing) illuminates all of these activities and relationships, and even provides useful rationales for key parts.
With this scaffolding in place, you can establish an approach and also drill into who’s involved, how long it lasts, and how much it’ll cost.
Who is Involved?
Every library is supported by a librarian (sometimes two) that coordinates activities, leads meetings, engages others, and does a lot of the dirty work. Depending on scale, the librarian may work with one or more contributors to create assets (HTML and wireframes), guidelines, training materials, and helpful tools (like a copy deck).
However, you can’t build a library in a vacuum. Depending on your objectives, inputs may come from a few or from seemingly everyone: product management, engineering, training, design technologists, writers, other designers on your team, vendors, and on and on. These folks are probably prime candidates to consume the library too, whether to understand how it works or get their hands dirty and actually use it.
How Long Does it Take?
The time it takes to build a library varies but is usually measured in months. Typical projects that transform an existing, stable design system into reusable design assets for wireframing and comps takes 2-3 months. Setting up a deeper library of code, a moderate amount of guidelines, and web-based platform for documentation and collaboration expands a timeline to 3-6 months or longer.
The three primary dials that tune how long it takes to assemble a library are:
Scale: How many items are you formalizing and documenting? Creating a library of 10 items is far easier than a rich repository of over 500 variations.
Design Asset Variation: It takes far less time to create a library of wireframe assets than to source, organize, and normalize design comp starting points. While “perfect” code is produced for projects, getting it into repositories and modularized for long term sustainability is more complex.
Documentation Level of Detail: The bigger the organization, the bigger investment you’ll need to make in preparing guidelines and instructional material to help them learn and use the system independently.
How Much Does it Cost?
Cost is always a tough nut to crack, and you often don’t know the precise cost until you complete a first cycle. That said, you can guide discussions of cost using three questions: how big is it, what’s most important (such as HTML/CSS assets over other assets), and what hidden costs does the sponsor not value or understand?
The more you plan and organize the library at the beginning, the more you save time and effort later on. Getting the library’s plan and organization correct is crucial. Invest in how you are going to roll out the design library and what you’ll build by when. Get organized first. Don’t just dive in!
However, the most important thing you need to plan for isn’t even the build itself. Libraries evolve, and looking at the effort like it’s a one-and-done investment is foolhardy. Instead, be ready to align interests, funds, and people to administer the library over time.
Published here on August 30, 2018.
About the Author
Nathan Curtis has been involved in UX since 1996, when he started focusing his creative energies on IA, ID, usability, and front-end development. He’s also an entrepreneur at heart, having founded the renowned EightShapes in Washington, DC. You can follow Nathan on Twitter at
In five 90-minute sessions, we’ll explore how you’ll develop your team’s own
Outcome-Driven UX Metrics.
With the right strategic UX metrics, your executives and stakeholders will see:
The progress your team is making towards launching better-designed products and services.
The cross-discipline collaboration that’s now shipping better products faster.
The increased value that customers see with every release.
This intensive is for those UX leaders ready to start working strategically. UX leaders who want
visibility and influence in their organization’s most crucial decisions.
UX metrics are powerful. They are an essential cornerstone of a strong UX strategy. Your UX strategy
is your ticket away from your organization’s feature-factory approach to shipping products.
Make UX a priority without having to fight to make UX a priority.
Join us for
. You’ll be happy you did.
UX Metrics Your Stakeholders Can’t Ignore