TL;DR
- Role: Product Designer, App Experience Team
- Timeframe: 2012 to 2013
- Business problem: Partner onboarding for Windows 8 app experiences was too custom, too slow, and too dependent on repeated design effort.
- What I changed: Built a white-label system that standardized onboarding and turned repeated partner work into a reusable model.
- Proof: Reduced global partner onboarding time by over 60%.
The problem was not the partners
Each partner felt like a new project: new asks, new assets, new coordination, new delay. The team absorbed that variance one engagement at a time. Onboarding depended on whichever designer happened to take the brief, and every new region paid the same setup cost again.
The partners were not the problem. The process was. There was no shared backbone between partners, design, and engineering, so every custom deliverable started from scratch.
I led the white-label initiative for global partnerships and worked across app design, motion, and coded UI. Staying in the implementation layer, not just the mockup, closed the gap between design intent and shipped output.
What I did
- Built a white-label system instead of custom per-partner design: one-time investment in tooling for a repeatable speedup on every future partner.
- Worked across design, motion, and coded UI rather than handing off at the mockup. Implementation fluency closed gaps that handoffs typically open.
- Ran "Friday Tips" inside the team: treated tooling and productivity knowledge as a shared asset so the gains compounded past individual projects.
- Created repeatable patterns for regional requirements, brand assets, and engineering constraints so partners entered a system, not a queue.
Operating model · white-label system
Before / after
From a queue of one-offs to one system.
Every partner rebuilt design, motion, and code from scratch. The team absorbed the variance one engagement at a time.
Partners enter a system, not a queue. The one-time investment pays back on every future partner.
What changed
- Cut global partner onboarding time by over 60%.
- White-label workflow adopted across regions and partner engagements.
- The team's collective tooling knowledge compounded through Friday Tips rather than staying siloed.
More importantly, this engagement named a pattern that recurs across the later work: when a team keeps solving the same problem, the real design opportunity is the system underneath it.
Reflection
This is early proof of the systems-thinking habit, not a flagship case. The highest-impact work in a partner program is often not the visible craft. It is the operating model behind it. Fix the workflow once and the next partner gets the benefit without anyone having to be a hero.