Design, before Any SoftwareLesson 74 of 74

Module 7 · Making the decision once

When not to build one

In this lesson

  • 8 min read
  • 7 reading sections
  • Knowledge check
  • Lesson 9 of 9 in this chapter

This chapter’s goalConvert a set of one-off screens into named tokens and a small component set, decide for any new element whether it is a variant of something existing or a new thing, specify every state a component can be in, and say at what point a project is large enough for the system to be worth its maintenance cost.

This chapter’s media

The film explains chapter ideas. The audiobook narrates the complete teaching text.

FormatEnglishहिंदी
Chapter filmWatch1:50Not available
Full audiobookNot availableNot available
How a design system usually diesAt firstOne person builds it in their own time, because they care about it. It is good, andpeople use it.ThenThey move team, or leave, or are pulled onto something urgent.Soon afterNobody else knows the conventions, so changes stop being made.Months onThe product moves on, and the system describes screens that no longer exist.In the endPeople stop consulting it, which is rational, and at that point it is genuinelydead.The defence is unglamorous: keep it small enough that somebody else can hold it, write down thedecisions rather than only the outputs, and make sure two people have changed it.
The defence is unglamorous: keep it small enough that somebody else can hold it, write down the decisions rather than only the outputs, and make sure two people have changed it.

Figure

A little at a time

Explore an idea, try it, then check what stays.

Step 1 of 9Free · no account needed
Lesson steps

Systems slow down the first three screens

Building tokens and components before you know what the product is means deciding things you cannot yet decide. The first three screens take longer, and several of the decisions turn out to be wrong, and unpicking them costs more than making them fresh would have.

This is the part that published design-system advice rarely says, because that advice comes almost entirely from organisations with dedicated system teams, hundreds of screens and dozens of contributors. Their conclusions are correct for their situation and are routinely applied to situations a hundred times smaller.

Your place and first choices stay on this browser. Classroom credit is recorded separately.

Stuck on something?Ask Meher, your AI tutor

How to cite: Addaly (2026) ‘When not to build one’, in Design, before Any Software. Edited by M. Mun. Addaly. Available at: https://addaly.com/learn/design-foundations/the-cost-of-a-system (Accessed: 21 November 2026).