How to Cultivate Shared Design Leadership Between Manager and Lead
Introduction
Imagine you're in a meeting room at your tech company. Two people discuss the same design problem, but each sees it through a different lens. One focuses on whether the team has the right skills. The other zeroes in on if the solution truly solves the user's problem. Same room, same problem, completely different perspectives—this is the beauty, and sometimes the challenge, of having both a Design Manager and a Lead Designer on the same team.
The old way was to draw neat lines on an org chart: Design Manager handles people, Lead Designer handles craft. But that's a fantasy. In reality, both roles care deeply about team health, design quality, and shipping great work. The real magic happens when you embrace the overlap instead of fighting it—when you think of your design org as a living organism. This guide will walk you through a step-by-step framework to make shared design leadership work seamlessly.
What You Need
- Commitment from both roles to collaborate and communicate openly.
- Regular sync time—at least a weekly one-on-one between Design Manager and Lead Designer.
- Shared vocabulary around team health, craft standards, and delivery processes.
- Clear decision-making criteria for when to escalate or delegate.
- A willingness to embrace overlap rather than avoid it.
Step-by-Step Guide
Step 1: Acknowledge the Overlap as a Strength
Instead of trying to separate the Design Manager's and Lead Designer's responsibilities into neat boxes, start by accepting that overlap is inevitable—and valuable. Think of the team as a living organism. The Design Manager tends to the mind (psychological safety, career growth, team dynamics). The Lead Designer tends to the body (craft skills, design standards, hands-on work). But mind and body aren't separate systems. The first step is to openly discuss with your counterpart: "Where do we naturally overlap? How can we use that to strengthen the team?" Create a shared document where you list areas of joint responsibility (like hiring, project scoping, or design critiques) and agree on primary vs. supporting roles.
Step 2: Define the Nervous System – People & Psychology
Primary caretaker: Design Manager
Supporting role: Lead Designer
The nervous system is about signals, feedback, and psychological safety. When healthy, information flows freely and people take risks. The Design Manager takes the lead here: they monitor the team's pulse, host career conversations, manage workload, and prevent burnout. But the Lead Designer plays a crucial supporting role by providing sensory input about craft development needs—spotting when a designer's skills are stagnating or identifying growth opportunities the Manager might miss. Together, establish a rhythm: the Manager runs weekly one-on-ones and team health checks, while the Lead Designer gives input on skill gaps during monthly craft reviews.
Step 3: Define the Musculoskeletal System – Craft & Quality
Primary caretaker: Lead Designer
Supporting role: Design Manager
This system drives the team's ability to produce high-quality design work. The Lead Designer sets design standards, conducts critiques, and ensures the team builds skills. They own the craft roadmap and push for excellence. The Design Manager supports by ensuring team members have the time and resources to develop those skills, and by helping the Lead Designer communicate craft needs to stakeholders. Work together to create a shared "craft health dashboard" that tracks things like peer review participation, skill progression, and design system adherence.
Step 4: Define the Circulatory System – Process & Delivery
Primary caretaker: Both roles share responsibility
Supporting role: Neither exclusively leads; they co-own
This system ensures that work flows smoothly from concept to shipped product. It includes project planning, cross-functional collaboration, and delivery rituals. The Design Manager focuses on team capacity, timelines, and stakeholder alignment. The Lead Designer focuses on design quality throughout the process, from discovery to final QA. Hold a joint weekly "circulatory check" where you review the project pipeline, identify bottlenecks, and decide who will address each issue. This prevents the "too many cooks" problem because each role knows when to step in and when to step back.
Step 5: Establish Regular Sync Rituals
To keep all three systems healthy, schedule recurring touchpoints:
- Weekly one-on-one (30 min): Discuss team morale, craft issues, and upcoming decisions. Use this to calibrate your shared leadership approach.
- Bi-weekly system review (45 min): Review the nervous, musculoskeletal, and circulatory systems. What's working? Where is the overlap causing friction?
- Monthly team health survey: Collect anonymous feedback on psychological safety, skill development, and process clarity. Both roles review results together.
- Quarterly alignment session: Revisit the shared document from Step 1. Update roles and responsibilities as the team evolves.
Step 6: Handle Conflicts with Grace
Even with clear systems, disagreements will happen. For example, the Design Manager might prioritize team morale over pushing craft standards, while the Lead Designer wants to raise the bar quickly. When conflicts arise, refer back to your shared framework. Ask: "Which system is this about? Who is the primary caretaker?" If it's a people issue, the Manager makes the final call—but only after listening to the Lead's perspective. If it's a craft issue, the Lead decides—but with the Manager's input on team capacity. If it's a process issue, you co-decide. Document these resolutions as case studies to guide future decisions.
Tips for Success
- Start small. Don't try to implement all three systems at once. Pick one (e.g., the nervous system) and make it work for a month before adding another.
- Communicate the framework to the team. Let designers know how Manager and Lead share responsibilities. This reduces confusion and builds trust.
- Review and adapt quarterly. Teams change, priorities shift. Treat this framework as a living document.
- Celebrate the overlap. When Manager and Lead collaborate well, it's a model for the whole organization. Share wins in all-hands meetings.
- Don't get hung up on titles. The principles here apply to any pair of senior roles—whether they're called VP of Design and Design Director, or something else. Focus on the systems, not the labels.
Related Articles
- Navigating the Cyclical Nature of Web Development: A Practical Guide
- The Surprising Dangers of Cognitive Offloading: How a Personal Knowledge Base Saves Your Skills
- Agentic Pair Programming for Data Science: Exploring marimo's Collaborative AI
- How to Use AI Tools in Coding Without Losing Your Fundamentals: A Developer's Guide Inspired by Stanford's Youngest Instructor
- SwiftUI and AppKit Mastery: New macOS Development Guide Launches for Beginners
- AWS Unveils AI Agent Revolution: Quick Assistant and Amazon Connect Expansion Redefine Enterprise Workflows
- 6 Startling Findings About the Growing Gender Gap in Math Achievement
- From Zero to Agent: A Beginner's Journey into Building AI