Structuring Success: How teams impact design systems
How team structure shapes the truth inside a design system
Published
This is the first of four write-ups from my Web Expo talk, Building NewsKit. The others cover adoption and advocacy, composable components and the lessons I'm keeping.
We often speak about the single source of truth within the design systems discourse. A magical place, a holy land of truth, the fountain of knowledge. The notion of a centralised and authoritative resource containing all the information and assets related to the design system. Or, in simpler terms — where the system lives. The idea of a 'Single source' suggests that there's a finite point, but in reality, truth is distributed throughout the organisation.
This truth is engrained in how we talk to each other, what we commit to code, what we mark as 'final' in our design files. As companies scale, and we think about enterprise level design systems, we end up with micro-organisations, with their own established truths. These teams have their own sets of standards.
And things happen that impact the truth:
- Changes in business priorities
- Restructuring and reorganisation
- People leave and join the company
- We learn new things
So, our notion of what the truth is changes. The conversations we have and contributions to the system change the truth.
But it's important to remember, that the truth is both personal, and communal. An individual's perspective on the system, isn't reflective of the whole truth.
Personal truth refers to an individual's subjective understanding based on their personal beliefs, experiences, and perspectives. It is shaped by factors such as their upbringing, culture, personal values, emotions, and life experiences. Personal truths are often influenced by subjective biases, and can vary greatly from person to person.
On the other hand, communal truth is the collective understanding or consensus reached by teams and organisations. Communal truth is formed through shared experiences, cultural norms, social interactions, and the exchange of ideas and information. It represents a shared understanding that is accepted and recognised by the group.
We need more people
Clearly, one person is not enough coverage to capture the truth. We need more people. We need more perspectives. We need to create teams.
An individual can only observe and influence the system from their own perspective. A team can observe and influence the system from multiple perspectives.
Floodlights and spotlights
Picture each person as a light pointed at the system. A generalist is a floodlight. The beam is wide, so it covers a lot of ground, but nothing it lights is lit brightly. A specialist is a spotlight. The beam is narrow and strong, and everything outside it is dark.
Neither is better. A system with only floodlights is understood shallowly everywhere, and one with only spotlights has deep knowledge in a few places and blind spots everywhere else.
A system needs many skill sets
There is no single skill that covers a design system. These are the ones I'd point at, and your list will probably differ.
| Skill set | What it covers |
|---|---|
| Visual design | Layout, typography, colour theory, visual design language, component library, design tokens, brand |
| User experience | Research, information architecture, interaction design, usability, testing, documentation |
| Front end development | HTML, CSS, JS, UI frameworks, developer standards, maintenance, monitoring, testing |
| Accessibility | Testing, documentation, specifications, advocacy |
| System operations | Documentation, architecture, process, tooling, inter-discipline operations |
| Content | Content strategy, technical and UX writing, voice and tone, principles |
Because people with different skills influence different parts of the system, the truth of the system gets shaped in many ways at once.
Collaboration, saturation and bias
Add people and you cover more of the system. Five people pointing in different directions can cover the full circle between them.
That stops working at some point. We can reach a critical mass, and past it too many people become a problem of their own. With twelve lights on the same circle, most of them are lighting ground another light already covers.
Then there is bias. If those five people all face the same way, they cover half the circle and leave the other half dark. Having enough people doesn't mean every area is covered, so it's worth checking which parts of the system nobody is looking at.
The centralised team
Within the centralised team, design, product and engineering come together to build and maintain the system. That's the model NewsKit started with.
But the system doesn't operate on its own. It sits in the middle of every team in the organisation, and for the health of the system and the business we need to be aware of all of them.
That calls for a third kind of light, the lighthouse. It does the communicating, sending signals to the teams around it and watching what they do.
We needed more lighthouses
By this point our team structure and strategy weren't going to be sustainable for NewsKit. Where the systems people sat within the organisation had to change.
The next article covers what that looked like in practice, starting with why adoption isn't binary.