G's Design Leadership Playbook
Manifesto & Field Guide (v1.3)
Table of Contents
Introduction: Why This Playbook Exists
Design leadership is more than craft. It is how organizations translate complexity into clarity, ideas into outcomes, and human needs into business value. This playbook exists to amplify that impact — equipping design leaders with the tools, practices, and evidence they need to scale design's influence across teams, products, and strategy.
Purpose – Amplify Design's Impact
Design is at its most powerful when it shapes decisions, not just interfaces. This guide captures the principles, frameworks, and practices that elevate design from a service function to a strategic driver. It is built to help leaders not only deliver great experiences, but also build teams, shape culture, and influence business outcomes.
Audience – Leaders, Builders, and Partners
This playbook is written for new leaders stepping into their first management roles, for experienced design managers evolving their practice, and for cross-functional peers — from product to engineering — seeking to understand how design works and where it adds value. It is meant to bridge language and perspective across disciplines.
Format – A Practical, Living Guide
This is not a static manual or a philosophical essay. It's a working field guide: actionable, iterative, and built to evolve. It combines principles and stories with tools and scorecards, showing how design leadership moves from intention to measurable impact. As the practice grows, so too will this playbook — adapting to new technologies, new ways of working, and new definitions of what design can achieve. Future expansions on topics including Team Building and Leadership; Process and Frameworks; Culture and Creativity; Communication and Influence.
1. Manifesto
Design leadership is about creating clarity in complexity, building cultures where people thrive and grow, and proving design's impact in measurable ways.
- Design reduces complexity: It transforms tangled systems into experiences that work the same, work together, and work for the user.
- Leadership builds trust: Humor, integrity, and transparency sustain retention, motivate teams, and unlock collaboration across silos.
- Evidence drives influence: Design earns its seat at the table when it can show measurable outcomes—qualitative and quantitative—that connect directly to business value.
- Growth through education: I frame those I lead as teammates. My role blends inspiration, management, and education—building cultures where teammates can do their best work while continuously growing their craft skills.
2. Leadership Journey
I began leading through teaching, evolving my leadership into managing large, complex teams in agencies and enterprises. My leadership style began as authoritative and pacesetting. I learned the hard way that deadlines and budgets alone don't sustain people. I rebuilt my leadership approach around inclusivity, transparency, and empowerment.
Today, my teams describe me as the best manager they've had, with 95%+ retention across the last 10 years. I rely on humor, honest candor, and adaptability to cultivate organizational cultures where design talent flourishes and businesses see measurable outcomes.
3. Vision & Strategy
Vision Statement
Design exists to reduce complexity and create clarity—for users, teams, and the business.
Design's superpower is making abstract ideas concrete so that teams can point at an artifact, align or at least to commit to a shared direction. Design is the human empathizer—connecting user needs with business priorities. It is the craft of cognitive psychology, human learning, perception, and emotion, applied to create systems people can understand and trust. And it is the craft of discovery—uncovering real user needs and translating them into actionable solutions.
Guiding Principles
- Human-Centered Always: Anchor decisions in human data, not assumptions.
- Inclusive by Default: Accessibility as foundation, not afterthought.
- Evidence-Driven Impact: Connect design outcomes directly to measurable business and user value.
- Collaboration at Scale: Radical collaboration across silos builds stronger solutions than isolated work.
- Clarity Over Cleverness: Design must simplify complexity in ways that drive adoption, reduce friction, and build trust. Cleverness that obscures understanding is the enemy of scale.
4. Metrics & Outcomes
Hiring managers, executives, and teammates alike look for proof that design leadership creates impact. Metrics provide that proof. They show that design is not only creative, but also strategic, measurable, and indispensable.
This section connects principles and practices directly to outcomes, with both quantitative and qualitative measures.
Quantitative Product Metrics (User Experience Quality)
- System Usability Scale (SUS): Benchmark usability across releases; target ≥ 80.
- Task Success Rate: % of users able to complete critical tasks without errors; target ≥ 90%.
- Time on Task: Efficiency improvements in workflows; aim for ≥ 20% reduction on high-frequency tasks.
- Error Rate: Reduction in user errors through improved design; target < 5%.
- Learnability: % of first-time users completing key tasks without assistance; target ≥ 80%.
- Error Recovery: % of users who recover without external help; target ≥ 70%.
Qualitative Product Metrics (User Feedback & Insights)
- User Satisfaction (SUS Comments): Contextualizes quant scores with user voices.
- Perceived Ease of Use: Themes captured in usability testing.
- Confidence Ratings: Post-task self-reported confidence; target ≥ 4/5.
- Customer Narratives: Interviews and diary studies capturing workflow integration.
Accessibility Metrics (Inclusive Design)
- Product Compliance/Audit Pass Rate: % of products passing accessibility audits without remediation; target ≥ 90%.
- VPAT Coverage: Up-to-date accessibility documentation for all core products.
Design System Metrics (Consistency & Scale)
- Component Compliance: % of design system components at WCAG 2.2 AA; target 100%.
- Component Adoption: % of product teams using system components vs. bespoke; target ≥ 80%.
- Coverage: % of UI built with system components; target ≥ 75%.
- Visual Consistency: Automated regression pass rate + manual audit alignment; target ≥ 95%.
- Contribution Health: % of contributions accepted; target ≥ 70%.
- Change Velocity: Time from request → published component; target ≤ 4 weeks.
- Defect Rate: % of bugs tied to system components; target < 5%.
Organizational Health Metrics (Team & Culture)
- Retention Rate: % of teammates retained year-over-year; target ≥ 95%.
- Hiring Velocity: Average time-to-fill design roles; target ≤ 30 days.
- Cycle Time: From concept to validated design; reduce ≥ 10% YoY.
- Design Debt Burndown: Reduction of legacy or inconsistent patterns; target ≥ 20% annually.
- Engagement Scores: % positive on motivation, clarity, culture; target ≥ 80%.
Product Usage Objective and Key Results
- Objective: A qualitative, inspirational statement that describes what the product aims to achieve and why it matters.
- Key Results: A small set (typically 2–4) of quantifiable outcomes that indicate whether the objective is being met.
More to come later on topics including Team Building and Leadership; Process and Frameworks; Culture and Creativity; Communication and Influence;
Case Studies
Thales IAM Example
Strategy:
- All experiences leverage the same design system so every team builds with the same "legos."
- Establish a shared shell UI across MFEs to ensure experiences work the same and together.
- Rebuild MFE architecture to solve state management and cross-MFE communication gaps.
Constraints & Realities:
A global organization built from multiple acquisitions naturally comes with different work styles and rhythms. Some teams operate like lean startups, moving quickly and iteratively, while others follow a more methodical SAFe process and maintain a closer partnership with design. These differences sometimes create friction, but when channeled well, they bring complementary strengths.
The org structure adds to the challenge: Product Management and UX report up one chain, while Engineering reports up another. That separation can create silos. My leadership approach is to bridge those divides—building trust with engineering peers and influencing alignment toward our shared vision.
Finally, not every product can or should be pulled forward. Legacy products running on older stacks and headed toward end-of-life aren't being retrofitted into the platform. The cost and effort would outweigh the value, and our investment is better focused on the future platform where the ROI will be lasting.
Impact:
- Unified design system rolled out across Consumer, Workforce, and Hardware IAM portfolios.
- WCAG 2.2 AA accessibility standards embedded into system components.
- Foundation laid for a single-pane-of-glass admin experience, despite org silos and technical constraints.
CDK Global Example
Challenge:
CDK's product teams were siloed and design maturity was uneven. Designers often lacked clear career paths, consistent processes, or influence within cross-functional teams. This created both talent retention risks and inefficiencies in delivering cohesive customer experiences.
Strategy:
- Built a career framework for design roles that clarified expectations, growth paths, and competencies.
- Extended career ladders to align with engineering and product counterparts, ensuring parity and visibility.
- Created a design system adoption program, embedding metrics around usage, contribution, and visual consistency.
- Championed radical collaboration rituals to break down silos and give designers stronger voices in product planning.
Constraints & Realities:
As an enterprise SaaS company serving the automotive dealer industry, CDK operated at scale with legacy processes and multiple product lines. Designers were spread across business units with different priorities. The biggest challenge wasn't talent—it was building a system and culture that let talent thrive.
Impact:
- Established a design career ladder that enabled designers to see clear paths from IC to leadership.
- Adoption of design system components increased (tracked via contribution and usage metrics), reducing redundant design and dev work.
- Retention improved as designers felt supported, valued, and connected to a shared practice.
- Elevated design's reputation internally by tying adoption and career growth to business outcomes, making the case for design as a strategic asset rather than a service.
