Responsive layout for small teams

We end up explaining this on discovery calls often enough that it deserved writing down. Most advice about responsive layout assumes a team that does not exist at your size. Here is the version that does not.

The measurable part of design is whether people can find what they came for and act on it without hesitating. The teams that stay on top of it are the ones who put it on a calendar rather than a wish list.

What to keep

Design for the smallest screen first and let the layout grow. None of that requires a large budget, only a decision and someone to own it. The failure mode is not doing it wrong, it is doing it once and assuming it stays done.

What to drop

Process that exists to coordinate ten people is overhead when there are two of you. The teams that handle this well are rarely the ones with the biggest budgets.

The practical version

Test on a real phone, not just a resized browser window. Getting it slightly wrong is survivable. Ignoring it entirely is not. If two people in the business would answer this differently, that gap is the actual problem.

What this looks like day to day

Consistency is the quiet half of design work: it rarely gets complimented, and its absence is noticed immediately. Three things worth confirming about responsive layout before you move on:

• Someone can say what the current setup is without going to look
• Test on a real phone, not just a resized browser window — and you know whether that is true here
• There is a way to tell whether the last change to this helped

Worth checking on your own setup before it becomes someone else's problem to fix.