Design, before Any SoftwareLesson 73 of 74

Module 7 · Making the decision once

Consistency is not uniformity

In this lesson

  • 8 min read
  • 6 reading sections
  • Knowledge check
  • Lesson 8 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

A little at a time

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

Step 1 of 8Free · no account needed
Lesson steps

Two things that sound alike

Consistency means the same things look the same. A destructive action is always the same colour; a card always has the same radius; a section heading always has the same space above it. This is what lets a reader stop examining, and it is the property that makes every deviation meaningful, as the repetition lesson established.

Uniformity means everything looks the same. It is what you get when a system is applied without judgement, and it produces work that is competent, coherent and completely inert: no hierarchy between screens, no sense that any moment matters more than another, nothing an eye wants to land on.

A system is meant to produce the first. Left unsupervised, it produces the second.

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) ‘Consistency is not uniformity’, in Design, before Any Software. Edited by M. Mun. Addaly. Available at: https://addaly.com/learn/design-foundations/consistency-versus-uniformity (Accessed: 21 November 2026).