From consultative design to release-level ownership.

TIMELINE

2021

PLATFORM

Web • Mobile

OWNERSHIP

Onboarding logic

Release impact

Mobile UX

Feasibility

Trade-offs

Validation

DESIGN LEADERSHIP

Layouts stable across breakpoints

Fewer manual fixes per sprint

Handoff without late-stage clarifications

Shared reference for 3 designers

Developers noted clearer handoff

SCOPE

Design system

Responsive UI

Component logic

Handoff

Design was in a consultative role at this company — development decisions came first, and designers supported them. Within that setup, I started noticing that the same UI decisions kept coming back: layout behavior, spacing rules, responsive logic, states, and handoff details. I worked to make those decisions easier to repeat, before anyone asked me to.

5M+

SUBSCRIBERS

150+

ENTERPRISE CLIENTS

3

PLATFORMS

12+

PLATFORMS RESEARCHED

Environment

💨

Engineering-led culture, design in a consultative role, developers shaped the final product

💨

White-label, vendors own content, quality uncontrollable

💨

Layouts needed manual fixes across screen sizes

💨

No established DS ownership, no shared process in the team

💨

First draft of the system criticized, rebuilt almost from scratch

# engineering-led # white-label # worst-case

Approach

Lobbied to join — full ownership from day one

Solved the detach problem independently — nobody asked

Recognized B2C patterns don't transfer — Netflix owns content, vendors don't

Beyond that: researched 12+ streaming platforms with purchased accounts, designed every layout against worst-case content — empty thumbnails, duplicates, low resolution — documented every state and edge case, introduced autolayout practices to the team, and mentored the junior designer to full autonomy.

# self-initiated # system-first # no-one-asked

Outcome

Developer: "the clearest handoff they'd worked with" — unprompted

PM on leaving: "very comfortable to work with" — unprompted

Product shipped looking the way it was designed. In an engineering-led culture, that's earned.

The system survived 4+ vendor customizations without major rework, the library stayed manageable at scale, and the team started defending design decisions collectively instead of individually.

# maintainable-system # design-before-code

“The clearest handoff to work with”

Kate

Front-end developer, unpromoted

Other cases