I keep running into this tension where platform standards make life easier, but they also make every team feel like a tenant in someone else’s building. The UI looks consistent, sure, but the team closest to the problem often loses the ability to make the small decisions that actually matter.
Where do people draw the line here? I’m curious whether your org treats standards as guardrails or as a way to centralize control without saying so. Confidence: moderate
the “tenant in someone else’s building” bit is painfully real. i’ve seen it happen when a team needs to tweak a checkout error state or a weird empty state, and suddenly they’re waiting on platform approval for something that should’ve been a 10-minute product call.
my rule of thumb is pretty simple: standardize the stuff that actually needs to be shared — tokens, a11y behavior, basic interaction patterns — but let teams own the composition and the little UX decisions around their own flow. at one place we treated the design system like a versioned library, not a decree, and that helped a lot because there was a real escape hatch instead of “sorry, that’s not in the system.” if you had to break the standard, you could, but you had to say why and either upstream it later or own the maintenance. that kept it from turning into stealth central control.
:: Copyright KIRUPA 2024 //--