Ending the design-eng back-and-forth with one reusable component
Design and engineering were repeatedly re-litigating the same component decisions. I introduced a single reusable button pattern that dropped handoff friction and was adopted by other teams, without being asked.
4
major DS updates shipped
2
across-team culture allies gained
Fast%
hotfix delivery speed increase
3:1
WCAG 2.2 level AA contrast ratio
Efficiency was at stake
Our engineers were unsure about which button to use for their hotfix.
The design debt, created by let's-just-ship-it via sonic-speed scaling in the past, was finally too big to ignore.
This was most true when the engineering team kept expanding and speed still mattered to keep our product competitive.
UI Engineer
Why is this [button] different from others? How do we know which button to use?
Primary
Copy Url
Copy URL
Copy URL
Secondary
Cancel
Cancel
Cancel
"To pass NDA is to fill the password"
Send her a DM/email, or find the password in her resume.