Eight lessons from building NewsKit
What I'm keeping from six years at News UK and the design system behind its brands.
Published
This is the last of four write-ups from my Web Expo talk, Building NewsKit. The others are what's in a design system, adoption and advocacy and composable components.
I've been at News UK for six years. We're a media company that publishes and broadcasts news, and we're the company behind NewsKit, the open source design system built for news brands.
I'm a generalist, which means I do a bit of everything. I've worked in design, development and product strategy, and I've been a consumer, a consultant and a contributor to design systems. I'm not an expert by any means, but I've seen design systems from lots of angles. Joni Mitchell sums it up better than I can. I've looked at design systems from both sides now, and I really don't know design systems at all.
Lots has changed recently and we've learned a lot. These are the lessons I'm sticking with.
1. My system isn't your system
Your system is for your business. What's in NewsKit, from the Figma library to the theme pipeline and the audio player, comes from News UK's business. Yours will look different.
2. The truth can be personal and communal
There's no single source of truth sitting in one place. Each person holds a piece, and the team holds a shared version. Both are real, and they change whenever people join, leave or learn something. More in the first article.
3. Build diverse teams, talk to each other and work in the open
One person covers one area of the system. Mixed skill sets cover more, as long as you watch for saturation and bias. You also need people who communicate across teams.
4. Adoption isn't binary
Any usage is good usage. Teams use the Figma library without the React library, or take a few components and not the rest, and that still counts. See adoption and advocacy.
5. Be adaptable
Respond to change, and take feedback with resilience and grace. Our first audio player took three months and got feedback that it wasn't flexible enough. We rebuilt it.
6. Buy-in isn't a one-time thing
Focus on business needs over system needs. Consumers act in their own interest, so the pitch has to be about what they're trying to ship.
7. Provide the building blocks
Give people the pieces to build their own path. A default component from the system doesn't have to be a consumer's default, and composable components are how we made room for that.
8. It's okay to not have all the answers
I don't have them. We changed our team structure and our components because the first answers weren't enough.