Dark mode for small teams

It is rarely the thing that gets a project approved, and often the thing that decides how it goes. Most advice about dark mode assumes a team that does not exist at your size. Here is the version that does not.

Consistency is the quiet half of design work: it rarely gets complimented, and its absence is noticed immediately. If it only works because one person remembers to do something, it does not work yet.

What to keep

Pure black on pure white is harsher than a slightly softened pair. The teams that handle this well are rarely the ones with the biggest budgets. It rarely shows up as a line item, which is exactly why it slips.

What to drop

Process that exists to coordinate ten people is overhead when there are two of you. Getting it slightly wrong is survivable. Ignoring it entirely is not.

The practical version

Shadows stop working in dark mode, so borders carry the depth. The cost of getting this wrong is rarely visible on the day it happens. Assume whoever inherits this will have half your context and none of your patience.

How to tell if yours is fine

The measurable part of design is whether people can find what they came for and act on it without hesitating. Three things worth confirming about dark mode before you move on:

• Someone can say what the current setup is without going to look
• Pure black on pure white is harsher than a slightly softened pair — and you know whether that is true here
• There is a way to tell whether the last change to this helped

Most of the value here comes from doing the first two things, not all of them.