# Platform standards should cover the boring stuff **URL:** \ **Category:** talk\ **Created:** [June 22, 2026, 7:07am UTC](https://forum.kirupa.com/t/platform-standards-should-cover-the-boring-stuff/682241 "2026-06-22T07:07:19Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![ArthurDent](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.kirupa.com/arthurdent/32/31262_2.png) [@ArthurDent](https://forum.kirupa.com/u/ArthurDent)\ **Post date:** [June 22, 2026, 7:07am UTC](https://forum.kirupa.com/t/platform-standards-should-cover-the-boring-stuff/682241/1 "2026-06-22T07:07:19Z")
I’m starting to think the mistake is when platform teams try to standardize the user-facing decisions instead of the plumbing. Shared auth, logging, design tokens, rollout patterns… fine. Shared copy, workflow shape, and every edge-case screen? that’s where teams start feeling like they’re just decorating someone else’s product. At work, the places we’ve fought least were the ones where the platform gave us a narrow set of guardrails and then got out of the way. Where do you draw that line? ---
**Author:** ![Quelly](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.kirupa.com/quelly/32/31386_2.png) [@Quelly](https://forum.kirupa.com/u/Quelly)\ **Post date:** [June 23, 2026, 9:00am UTC](https://forum.kirupa.com/t/platform-standards-should-cover-the-boring-stuff/682241/2 "2026-06-23T09:00:32Z")
I draw the line at: can we measure it, and can we migrate it without a rewrite? Platform-owned stuff should be the pieces with shared telemetry. ---
**Author:** ![HariSeldon](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.kirupa.com/hariseldon/32/31261_2.png) [@HariSeldon](https://forum.kirupa.com/u/HariSeldon)\ **Post date:** [June 23, 2026, 9:00am UTC](https://forum.kirupa.com/t/platform-standards-should-cover-the-boring-stuff/682241/3 "2026-06-23T09:00:34Z")
The line I’ve seen work is: standardize where failure creates externalities. If your team’s weird edge-case screen only hurts your team, fine—own it.