Head of Design
Intro
When I take on a Head of Design role, I start by figuring out what's actually happening. Who owns what? Where do requests get stuck? What's causing friction between teams? How does design strategy connect to business goals?
Once I have a clear picture, I put structure in place: define ownership, set up regular check-ins, and make sure people know where to focus. From there, I work on the operating model. I align design with product and marketing, balance brand-specific needs with shared initiatives, and build systems that help the team deliver consistently without burning out.
What I Focus On
Streamlined workflows:
One intake point, shared planning, short review cycles. The goal: less rework, more time for actual design, and predictable delivery.
Scalable design systems:
I focus on reusable foundations rather than endless variations. Shared tokens, core components, clear documentation. Easier to maintain, faster to ship, consistent across brands.
Creative direction across UX/UI and brand:
I provide design leadership that connects user experience with business goals. Clear creative direction helps teams make better decisions without waiting for approvals.
Team stability during change:
When things are uncertain, I create structure. Clear ownership, visible decision-making, regular communication. People do better work when they know where they stand.
Outcomes
What I aim to achieve:
Briefs that arrive complete, reducing back-and-forth and unplanned scope changes
Faster onboarding so new designers contribute sooner
Higher brand consistency across deliverables
Lower QA rework through better processes and documentation
During transitions: clear roles, stronger collaboration, and stable retention
How I Lead
One playbook, not scattered docs:
A single reference linked to Figma templates, QA checklists, and project documentation. Built into onboarding and team syncs so it actually gets used.
Streamlined intake:
A single funnel for requests with stream-specific templates. Weekly triage with clear SLAs, and a visual brief that sets expectations upfront. Plus a fast lane for things that genuinely can't wait. Automation flags incomplete or stale requests before they become problems.
Design system that scales:
Shared tokens, core components, clear documentation. I focus on reusable foundations rather than endless variations. Docs include intent, usage guidelines, accessibility checks, and code examples.
QA that doesn't slow things down:
Separate tracks for content and design, with automation to route work to the right people. Async checklists tied to Jira, escalation only for meaningful issues. Fewer handoffs, fewer tasks bouncing back.
Hiring and team building:
I build teams with intention. Clear role definitions, structured interviews, and onboarding that gets people contributing quickly. I manage resourcing and budget to keep the team sustainable.
Stakeholder management:
I keep leadership and cross-functional partners informed without overwhelming them. Regular updates, clear expectations, and no surprises.
Support during transitions:
When leadership changes or teams restructure, I step in where needed. I mentor new managers, map out ownership clearly, and keep communication steady. Weekly department syncs, updated scopes with HR, and clear owners per stream to keep accountability visible.
Proof
I've done this before. My Design Ops case studies show the results: streamlined intake, reduced QA rework, faster onboarding, and 100% team retention through a major reorganization.
First 90 Days
The first 90 days are about understanding before making big changes, but not waiting to add value.
First month:
I meet with leadership, product, engineering, and marketing to understand priorities and pain points. What's working? What's stuck? What does success look like for this team? I assess design maturity and current design culture. At the same time, I identify quick wins: problems that can be solved with minimal disruption.
Second month:
I dig into the team itself. Skills, workflows, how design collaborates with other functions. I review the design system, look at user feedback, and identify where processes break down. I start implementing small changes that move the needle without destabilizing what's already working.
Third month:
Based on what I've learned, I draft a design strategy and roadmap. Not a wishlist, but a focused plan for where design can make the biggest difference, whether that's acquisition, retention, product quality, or team efficiency.
Let's Talk
If this sounds like the kind of leadership you're looking for, I'd be happy to chat.