Design Leadership Needs a New Standard

1. Empowering Career Growth in Design

Design teams flourish when people see a path forward, not just in titles but in impact, autonomy, and confidence. Creating a clear growth framework is an act of leadership care. When designers understand how their growth is supported, they’re more likely to stay curious, engaged, and invested in the team's success.

Strategy-level moves

1.1 Define dual career tracks

Establish well-articulated paths for both individual contributors and people managers. This prevents the assumption that growth means management, and instead honors those who grow by deepening craft, influence, and impact.

1.2 Normalize growth conversations

Weave career development into your team rhythms. Rather than saving feedback or ambition for annual reviews, build space into regular 1:1s for reflection, aspiration, and alignment. Managers should feel accountable not just for performance but for progression.

1.3 Align career goals with org needs

Great career paths are shaped by opportunity and intent. Make it clear how design growth aligns with strategic priorities, such as leading design systems, driving major initiatives, or mentoring the next generation of talent.

Tactical best practices

1.4 Stretch assignments and projects

Encourage ICs to take on responsibilities just beyond their comfort zone. Let them lead critiques, define frameworks, or own cross-functional partnerships. These assignments build trust, confidence, and readiness for the next level.

1.5 Peer mentorship circles

Facilitate ongoing mentorship relationships that cross team or level boundaries. These don’t need to be formal programs. Sometimes just creating space for shared reflection and guidance leads to strong professional bonds.

1.6 Team rituals

Embed growth into your team’s habits. Use career path templates, portfolio reviews, or growth journaling practices to keep development visible and self-directed. One particularly effective practice is growth journaling, a lightweight, regular reflection habit that encourages designers to document progress, set intentions, and stay accountable over time.

Story: Designing growth at Zalando

At Zalando, designers once faced a challenge common to many maturing teams: how to continue growing meaningfully without defaulting to management as the only path forward. In response, the design leadership introduced a dual-track career framework that supported both craft-focused and people-focused roles. This move empowered designers to align their growth path with their personal motivations, whether centered on deepening expertise or developing others.

Over time, many designers moved between roles, transitioning from manager to principal and back, depending on where they felt most fulfilled. Management was reframed not as a promotion, but as a different design challenge: shaping teams, processes, and environments to unlock growth. Meanwhile, individual contributors at the principal level continued to grow by mentoring peers, leading complex initiatives, and advancing the practice of design across the company.

With transparent criteria, consistent growth conversations, and a strong culture of mentoring, the team shifted from ambiguity to clarity. Career development became a user-centered journey, guided by curiosity, feedback, and trust.

You can read more in the original piece: The Expert Track to Design Career Fulfillment.

2. Building Cross-Functional Collaboration

Design thrives when it’s integrated into the fabric of product development, not as a downstream function, but as a partner in shaping vision and outcomes. For this to happen, design leaders must move beyond advocating for a seat at the table and instead cultivate systems, relationships, and habits that make collaboration inevitable, fluid, and valuable.

Strategy-level moves

2.1 Orchestrate organizational alignment through design

The most transformative design leaders don't just translate between functions, they architect the collaborative foundation that enables breakthrough innovation. In an era where product success hinges on seamless cross-functional execution, design must evolve from service provider to strategic orchestrator. Designers are uniquely positioned to bridge strategy and execution. They synthesize vision, constraints, and user needs into shared, tangible narratives that help teams see the big picture. Design leaders can amplify this connective role by introducing tools like journey maps, service blueprints, and experience principles, artifacts that align teams, clarify priorities, and foster a sense of mutual ownership across disciplines.

2.2 Embed design in upstream thinking

Invite design into the earliest stages of product strategy, before roadmaps are locked. This helps ensure user needs are part of problem framing, not just solution refinement. It also positions design as a co-leader in shaping opportunity spaces, not just interfaces.

2.3 Promote feedback as a team sport

Normalize critique and feedback across disciplines. Rather than presenting final designs, create rituals that invite engineers, PMs, and stakeholders into the design process. One of our most effective rituals was the weekly Design Club on Wednesdays, an open, team-wide critique space where work-in-progress could be shared for constructive input. These sessions didn’t just surface useful feedback; they built shared vocabulary, deepened trust, and pushed the standard for what we considered great design. The earlier feedback flows, the more shared the solution becomes, and with rituals like this, critique becomes a muscle, not a moment.

Tactical best practices

2.4 Run cross-functional workshops

Facilitate workshops that bring together product, design, and engineering. Whether to define a problem, generate solutions, or map trade-offs, these sessions build trust, surface constraints early, and unlock creative energy from the full team.

2.5 Document decisions transparently

Use shared tools, like Notion, FigJam, or Confluence, to document trade-offs, design decisions, and rationale. This promotes alignment and reduces backtracking. Transparency is a collaboration multiplier.

2.6 Teach designers to navigate ambiguity with empathy

Great collaboration isn’t just process, it’s emotional intelligence. Equip designers with practical tools and frameworks to foster that intelligence: active listening techniques, storytelling methods to communicate design intent, and conflict navigation models rooted in curiosity rather than defensiveness. Encourage role-playing exercises, co-reflection sessions, or design pairings where empathy is practiced, not just expected. One particularly effective ritual we used was team retrospectives, a space to unpack friction, misunderstandings, or emotional undercurrents from a place of shared learning. These skills, when nurtured intentionally, transform moments of tension into opportunities for alignment and insight.

Story: Building Top Picks for You

One of the most cross-functional initiatives our team undertook was the “Top Picks for You” feature, a personalized module designed to help users discover relevant content faster. From day one, we framed it not as a design task, but as a shared experiment across design, data science, product, and engineering.

We began with discovery workshops, where everyone contributed hypotheses and questions. Design led early concept sketches and validation, but engineers quickly helped define what was technically feasible in real time. PMs shaped the scope and ensured we were aligned with business goals. Data scientists embedded personalization logic based on live signals. This collaboration became a blueprint for how design, product management, and data science could jointly measure and influence user experience outcomes.

3. Raising the Bar for Design Excellence

Design excellence isn’t just about polish. It’s about clarity, coherence, and intentionality. It’s about delivering outcomes that feel intuitive, accessible, and deeply aligned with user needs. But excellence doesn’t happen in silos or by accident. It must be cultivated through shared standards, honest critique, and a commitment to elevating craft across the team. Design leaders have a responsibility not only to model high standards but to operationalize them. This means defining what quality looks like, embedding it into the way teams work, and creating space for creativity and refinement under time pressure.

Strategy-level moves

3.1 Define what “great” looks like

Excellence begins with clarity. Without a shared understanding of quality, teams default to opinion over principle. Design leaders must define, and regularly revisit, what “great” looks like at their company. One effective approach is hypothesis-driven design: framing work around testable, user-centered assumptions that create alignment and focus. This method encourages teams to articulate desired outcomes up front, making quality less subjective and more observable. It can be supported through quality principles, curated examples of strong work, or design maturity frameworks that evolve with the organization. Importantly, these standards should be co-created, not just top-down mandates, to foster ownership instead of compliance.

3.2 Institutionalize critique as a learning ritual

High-performing teams use critique to learn, not just to judge. Effective critiques are structured, safe, and focused on intent and impact. Design leaders can create space for different types of critique, from lightweight async reviews to deep-dive workshops, and ensure everyone, regardless of level, knows how to both give and receive feedback. Critique should be where the bar is raised, not where confidence is shaken.

3.3 Maintain systems that support, not stifle

Design systems are a force multiplier for quality, but only when they’re built to evolve. Rigid systems can hinder creativity, while loosely governed ones lose cohesion. Design leaders must invest in systems that balance consistency with expression, and empower contributors to improve and extend patterns over time. A strong system is one that invites ownership, not just adherence.

Tactical best practices

3.4 Create a design QA layer

Before handing off to engineering, set up a design QA pass to ensure that small usability or accessibility issues don’t get baked into final builds. This isn’t about perfection. It’s about accountability to the standard you’ve set.

3.5 Elevate craft through visibility

Regularly showcase work internally, whether through demos, design weeks, or Slack threads, to celebrate what great looks like and make invisible effort visible. Visibility inspires pride, promotes learning, and spreads high standards across the org.

3.6 Encourage portfolio thinking

Great design teams treat their body of work like a portfolio, not just a backlog. Encourage teams to look back at released work and ask: “Is this still our best expression of what we know?” Revisit, refine, and retire. Excellence is maintained, not just launched.

Story: Iterating on quality (HeyChauffeur)

HeyChauffeur started as a fake door test, a lightweight experiment to validate whether users were interested in a personalized mobility service. While the initial interaction was minimal, the feedback we gathered gave us clarity on what mattered: trust, flexibility, and tone. It wasn’t about visual detail yet, it was about intent. This early signal gave us permission to go deeper, and the quality bar we later set was grounded in that validated curiosity.

4. Creating with the Machine

Design is no longer a solo act. Today, machines are not just tools. They’re collaborators, capable of generating, filtering, and learning alongside us. 'Creating with the Machine' means engaging with AI not just as a productivity boost, but as a partner in shaping systems, language, and user expectations. To explore this paradigm, I often return to a short, inspiring talk: ‘How Stanford Teaches AI-Powered Creativity in Just 13 Minutes’ by Jeremy Utley. It captures the shift from using AI as a tool to collaborating with it as a teammate: a subtle but powerful mindset change for designers navigating this new frontier. As design leaders, our task is to decide when, and how, to embrace that tension. When we design with AI, we’re not just designing screens. We’re shaping behaviors, ethics, and emergent systems. That requires curiosity, principles, and cross-functional fluency.

Strategy-level moves

4.1 Thrive in ambiguity

Nobody has the perfect playbook for AI, and that’s the opportunity. Encourage your team to stay open-minded and try different things. Make space for rapid experimentation, unexpected use cases, and lightweight pilots. The best ideas emerge from a culture that treats uncertainty as fuel, not friction.

4.2 Lead with ethics

As AI becomes more embedded in products and processes, design leaders must get educated and proactive about the ethical implications. This includes bias, transparency, consent, and explainability. If designers aren’t shaping the rules, someone else will. Help your team become confident ethical stewards of the technology.

4.3 Shift from fear to fluency

In an era of mass layoffs and industry volatility, fear alone won't safeguard a career. Adaptability will. Many creatives view AI as a threat, but avoidance is not a viable strategy. Design leaders must help their teams move beyond anxiety and into experimentation. Normalize curiosity. Share success stories of augmentation, not replacement. Reinforce that fluency, not mastery, is the new advantage. And remember: change isn't coming, it's already here. Your team’s mindset will shape whether they’re disrupted, or leading the disruption. Innovation doesn’t happen in isolation. Collaborate early with data science and product management to explore feasibility, define useful signals, and test outcomes. Great AI UX begins with a shared hypothesis and evolves through iteration, not handoff.

Tactical best practices

4.4 Try tools and find your flow

No single AI tool does everything well. Encourage your team to test multiple tools and workflows to find what resonates, from prompting LLMs to leveraging image generators to scripting productivity automations. The goal is to develop a personalized flow, not one-size-fits-all tooling.

4.5 Establish etiquette and share knowledge

Introduce usage norms early: when to cite AI-generated content, how to document prompt logic, and how to disclose automation in shared work. Building an internal etiquette guide fosters trust and raises the collective standard.

4.6 Run AI hackathons and share what you learn

Host low-pressure internal challenges to explore use cases and learn by doing. Hackathons democratize access, surface unexpected insights, and strengthen cross-functional collaboration. Pair exploration with reflection to embed learnings back into day-to-day practice. When designing with AI, the behavior is the experience. Treat model behavior as a design surface, log interactions, tag friction points, and refine the system based on real usage data.

Story: From uncertainty to impact (teaching ourselves to work with AI)

Over a weekend, I built a quick prototype to gather and display open design jobs from companies around the world, a personal itch that turned into a small act of community contribution. I combined Gemini, ChatGPT, Python, Google Cloud, Cloud Scheduler, GitHub, and Airtable to automate the process of scraping jobs from around 45 companies. It wasn't perfect, but it worked. And more importantly, it was shared. I posted the early version with a simple note: “Hope this helps you or your loved ones.” Within days, I received feedback, requests, and encouragement to extend it to other platforms like Join and Lever. This wasn’t a formal initiative or a work assignment. It was a reflection of how AI-powered creativity is becoming accessible, and how small experiments can lead to real value.

5. Measuring What Matters

Design leadership isn't just about craft, culture, and collaboration — it's also about clarity. If we want design to lead, we need to show how it delivers impact. But meaningful measurement goes beyond outputs and velocity. It includes the health of our teams, the trust we build across functions, and how our work resonates with users.

Strategy-level moves

5.1 Connect design metrics to product and business outcomes

Design doesn't operate in a vacuum. Leaders should frame success in terms of customer impact and company priorities, whether that's conversion, retention, activation, or satisfaction. Map design activities to measurable product goals, and co-own those outcomes with product and engineering.

5.2 Track behavioral and attitudinal signals

Use frameworks like H.E.A.R.T. (Happiness, Engagement, Adoption, Retention, Task Success) to combine qualitative and quantitative insight. Track sentiment over time through surveys and interviews, and behavioral patterns through analytics. This dual lens helps ensure that what we're building is not only used, but valued.

5.3 Make team health a visible metric

Great products come from healthy teams. Monitor psychological safety, clarity of expectations, and feedback culture through regular health checks. Treat retention, growth opportunity, and cross-functional trust as signals of a design org that’s truly working.

Tactical best practices

5.4 Embed design in OKRs and planning

During quarterly planning, advocate for design-led goals and measurable success criteria. Use design-specific OKRs like usability improvements, system adoption, or design debt reduction to highlight meaningful impact.

5.5 Co-analyze with product and data science

Designers shouldn’t just deliver. They should discover. Partner with product analysts and data scientists to run experiments, segment users, and learn from outliers. When design is embedded in analysis, teams unlock deeper insights.

5.6 Share wins and learnings regularly

Create visibility for design impact through internal showcases, newsletters, or retrospectives. Share not just the polished UI, but the journey, trade-offs, and outcomes. This builds credibility and fosters a shared understanding of design's role.

Story: From survey to signal

In our Top Picks for You project, we discovered that while engagement was strong, users were frustrated by the overwhelming number of options. A curated, personalized selection of just 80 items — based on past browsing behavior — significantly improved satisfaction. To measure the impact, we leveraged both behavioral and attitudinal metrics grounded in the H.E.A.R.T framework, including click-through rates, dwell time, and satisfaction surveys. These signals validated our hypothesis and illustrated how narrowing scope could elevate perceived relevance, reduce friction, and increase user trust.