Mobile-first design for small teams

Most teams know this matters. Fewer have decided who owns it. Most advice about mobile-first design 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. Write the reasoning down alongside the decision, because the reasoning is what changes first.

What to keep

More than half of most sites' traffic arrives on a phone. The reasoning matters more than the rule, because the rule has exceptions. Most teams find the first pass takes an afternoon and the maintenance takes minutes a month.

What to drop

Process that exists to coordinate ten people is overhead when there are two of you. The cost of getting this wrong is rarely visible on the day it happens.

The practical version

Desktop layouts are easier to add than to strip back. This is the sort of thing that compounds, quietly, in both directions. If it only works because one person remembers to do something, it does not work yet.

In practice

Design decisions are the ones clients feel most confident arguing about, which makes it worth separating taste from evidence early. Three things worth confirming about mobile-first design before you move on:

• Someone can say what the current setup is without going to look
• Starting narrow forces you to decide what actually matters — and you know whether that is true here
• There is a way to tell whether the last change to this helped

If any of that sounds like a description of your current setup, it is fixable.