- Situation
- A global retail-pharmacy business was standing up an enterprise pharmacy-software transformation across multiple product domains. There was no visual-design discipline operating at scale, no shared system, and no consistent way for apps built by separate teams to look or behave like one product.
- What I owned
- I ran the entire build of the discipline from 2 designers to 12: all interviewing, hiring, and onboarding. More than headcount, I wrote the function's operating model, the team vision and standards, the hiring practices, the onboarding program, the design-review process, and a senior-designer model that placed art-direction leads inside each domain to cut bottlenecks. I set the shared visual standards, branding, accessibility bar, and naming conventions, and I led the visual-design side of the enterprise design system in partnership with UX and development.
- What changed
- Separate domain apps became one coherent system adopted across every product team, governed by a design system with common vocabulary and a repeatable review process. The team ran as a function, not a queue: designers were mentored up, domains had their own leads, and the standards outlasted any single person. This is my proof I can drive adoption org-wide and build a team that sustains it.