Designing the org, not the pixel

At some point in a design career, the pixels stop being the constraint. Not because they got easier — they didn't — but because the team around you got better at them than you are. The honest thing, when that happens, is to notice, and to move to where you can still be useful. For most senior designers I know, that place is the org that produces the pixels, not the pixels themselves.

Org as design surface

Every team ships the meeting it was designed in. If your standup is boring, your roadmap will be boring. If your critique is polite, your product will be polite. If your PRDs are written to avoid disagreement, your product will avoid having a point of view. Nothing about the interface can be braver than the room it came from.

"You cannot ship a product that is braver than the meeting it was designed in."

The three things I actually design now

• 01The words a team allows itself to use. "Nice" is banned. "Boring" is a compliment. "Obvious in retrospect" is the bar.
• 02The rituals that decide what ships. A weekly review with a stack rank, not a demo reel. A written stance, not a slide.
• 03The hires and the seating chart. Two designers who disagree in public are worth ten who agree in Slack.

What you give up

You give up the 11pm silence where a file finally clicks. That silence is real, and I miss it. What you get in exchange is a different silence — the one in a room where a team that used to look at you for the answer looks at each other. That is worth it, most days.

The uncomfortable part

Designing the org means being wrong more often than designing pixels ever let you be. Screens have obvious feedback loops; org changes take a quarter to show a signal, and even then the signal is noisy. You will make calls you can't fully justify to the person who wants a chart. Make them anyway. The good ones become the operating rhythm of the company; the bad ones become the story you tell in your next interview.