Back

Designing on rails the team laid

You’re a designer. The team settles on a direction in a meeting, and you build exactly that. Not roughly that, but the precise thing everyone agreed was right, you included. It feels responsible. I’d argue it often isn’t.

It felt right in the room, but nobody had been in the details yet. The details that make or break a design only show up once you’re working in them. Sometimes the direction doesn’t work out as expected, or new problems pop up that nobody saw coming. Building what was agreed without digging into those details is what I mean by designing on rails the team laid. Your job isn’t to execute a direction. It’s to understand the problem first, then drive a solution that works for users.

The instinct with any direction is to judge it. Good or bad? Build it or push back? That question skips a step. The better one is what problem sits underneath it. You’ve spent years thinking about how people move through interfaces, and your teammates have spent theirs on other things. You’ll notice things they don’t, and they’ll notice things you don’t. That’s the whole point of a team with different skills.

So why do designers stay on the rail? Part of it is safety: digging in might mean pushing back, and that risks looking difficult or being wrong in front of everyone. Part of it is accountability. When the whole team agreed, the outcome belongs to everyone, which in practice means no one in particular. That feels comfortable, but you’ve stopped shaping the product and started following the rails.

What makes this hard to see is that it doesn’t look like a problem. The output matches what was discussed, and everything looks correct. It just might be less than it could have been, and the team never sees the version that wasn’t made.

Sometimes the direction holds up once you’re in the details. Then build it, but know why. When it doesn’t, saying so isn’t always enough. A sentence of doubt rarely changes direction, and a half-formed alternative can be worse: now the team has to evaluate something incomplete on top of everything else.

What changes direction is making clear you’ve understood the problem from different angles, then showing up with something better: an alternative that already accounts for the goals, the constraints, and the edge cases. If it’s clearly better, people tend to get on board, persuaded by the work rather than by an argument. Each time that happens, the next one gets a little easier. That’s how trust builds.

Going off-rail isn’t going against your team. It means taking what they said seriously enough to keep going:

  • Find the why behind the direction.
  • Map the full picture from your point of view.
  • Drive the solution, and let the team see it next to what was discussed.

Staying on the rails gets the team exactly what it discussed. Going off them, done well, gets users what they actually need. That’s the job of a designer.