Product Designer
DesignmediumFree
Break the System or Break the Design
The component you need doesn't exist. The deadline doesn't care.
FNorthstar Academy 4.3 (426) 2,982 taken 35m Product Designer
The situation
Your feature needs an interaction the design system doesn't support, and the system owner says creating a one-off will fragment the library. You can hack a non-standard component now or wait two sprints for a proper one. The team is split and your launch is next week.
What you'll practice
Weigh system integrity against shipping velocity
Weigh system integrity against shipping velocity. Show it clearly — with evidence a reviewer can point to.
Propose a path that doesn't permanently fragment the library
Propose a path that doesn't permanently fragment the library. Show it clearly — with evidence a reviewer can point to.
Get the system owner and feature team aligned
Get the system owner and feature team aligned. Show it clearly — with evidence a reviewer can point to.
Define how the one-off graduates into the system later
Define how the one-off graduates into the system later. Show it clearly — with evidence a reviewer can point to.
The room
3 autonomous AI coworkers, each with their own agenda. They won't all agree.
T
Tom Akande
Design System Lead
Wants: Protects consistency and refuses one-off components
Style: Guardian, long-term-minded
H
Hana Yoshida
Feature Engineer
Wants: Just wants something buildable this sprint
Style: Pragmatic, deadline-aware
N
Nadia Karimi
Product Manager
Wants: Cares only that the feature ships on time
Style: Schedule-first, impatient
Your workspace
Real tools, pre-seeded with context. You're not roleplaying, you're working.
Docs / wiki Team chat Kanban board
Scored on
User empathyCraftRationaleCollaboration