LEADERSHIP / PLAYBOOK 03 / TEAM DESIGN · CAREER ARCHITECTURE · COACHING · HIRING
Growing the team behind the operating model
A playbook for building capable, accountable design teams, from a lean practice to a
growing organization. I do not begin team planning with headcount ratios or an
organizational chart. I begin with the outcomes the business must achieve, the decisions
design must influence, and the capabilities required to deliver a coherent digital
experience.
USE WHEN
A lean practice needs to scale, roles and decision rights are unclear, or growth is
adding coordination instead of capability
HORIZON
A 90-day implementation, then a recurring people cadence from weekly one-to-ones to
annual succession planning
WHO IT IS FOR
Heads of design, design managers, and product leaders responsible for staffing and
developing design teams
CORE ARTIFACTS
Capability plan · Role charters · Career framework · Role scorecards · Hiring rubric ·
30–60–90 onboarding · Team-health scorecard
THE PEOPLE SYSTEM SHOULD CONNECT
The smallest team that can responsibly execute the strategy.
The goal is to build the smallest team that can responsibly execute the strategy while
creating a foundation that can scale. As the organization grows, additional roles,
management layers, and specialties should solve demonstrated problems, not simply mirror
the structure of a larger company.
01
Business value
02
Required capabilities
03
Clear roles
04
Effective teams
05
Strong performance
06
Career growth
07
Leadership continuity
01 / CAPABILITY PLAN
Start with the work, not the org chart.
The product operating model defines the work design must support. Assessing each area
produces a capability plan rather than a collection of job requests. Permanent roles
should be created when the need is strategically important, recurring, and substantial
enough to justify sustained ownership.
THE WORK DESIGN MUST SUPPORT
Product and experience strategy.
Customer and market understanding.
Product discovery and validation.
Feature design and delivery.
UX architecture.
Design systems and shared patterns.
Accessibility and content quality.
Design-engineering collaboration.
Release readiness and design quality.
Product activation and adoption.
Measurement and continuous improvement.
FOR EACH AREA, ASSESS
How important is it to the business strategy?
How much work and decision-making does it require?
What level of experience is needed?
Which capabilities already exist?
Where are the most consequential gaps?
Can the need be addressed through hiring, development, partnership, automation, or
reduced scope?
NOT EVERY CAPABILITY GAP REQUIRES A PERMANENT HIRE
Make
Build the capability through a dedicated role.
Develop
Grow it within the existing team.
Borrow
Use a partner, specialist, or temporary engagement.
Share
Establish a capability that supports several teams.
Automate
Use systems or AI for repeatable, low-risk work.
Stop
Remove work that does not support a priority outcome.
02 / LEAN FOUNDATION
Design the lean-team foundation.
A lean team succeeds through focus, experience, and leverage, not by attempting to
service every request.
A STRONG FOUNDATION USUALLY INCLUDES
An accountable design leader who can set direction and remain close to the work.
Experienced, broadly capable product designers.
Direct collaboration with product and engineering leaders.
Access to research, content, accessibility, data, and technical specialists.
Shared patterns and tools that reduce repeated work.
Explicit protection for discovery, quality, and system-level improvements.
OPERATING PRINCIPLES FOR A LEAN TEAM
01
Organize around priorities
Assign designers to the most important value streams or outcomes. Avoid distributing
limited capacity evenly across every project.
02
Prefer durable ownership
Persistent ownership builds domain knowledge, stronger partnerships, and
accountability for results. Continually moving designers between urgent requests
destroys that advantage.
03
Hire for breadth first
Early designers should be comfortable moving between problem framing, research,
interaction design, prototyping, systems thinking, delivery, and measurement.
Specialization becomes more valuable as the volume and complexity of recurring work
increase.
04
Protect enabling work
A lean team still needs time for UX architecture, design-system patterns, research
practices, accessibility, and quality improvement. Without this investment, delivery
becomes slower as the product grows.
05
Control intake
New work should enter through product priorities, not informal requests. Every
meaningful ask should identify the business outcome, the customer problem, the
decision required, its urgency and consequence, and the capacity it will displace.
True emergencies should be narrowly defined: serious customer harm, regulatory
exposure, production failure, or material revenue risk.
03 / SCALING
Scale in response to organizational signals.
Growth should be triggered by persistent conditions rather than a target team size.
Adding people without changing ownership can create more coordination rather than more
value. Team topology and decision rights should be reviewed whenever staffing changes
materially.
ORGANIZATIONAL SIGNAL
APPROPRIATE RESPONSE
Designers are split across too many unrelated initiatives
Create persistent value-stream ownership
The design leader cannot coach while covering critical product work
Add a manager, lead, or principal
Different teams are creating incompatible experiences
Strengthen UX architecture and design-system ownership
Research demand exceeds the team's ability to gather evidence
Add research capability or research operations
Senior designers repeatedly solve cross-product problems
Formalize staff or principal-level roles
Coordination and administration consume leadership capacity
Introduce design operations
Content creates usability, trust, or localization problems
Add content design leadership
Accessibility issues are discovered late
Establish dedicated accessibility capability and governance
Product adoption is weak despite successful delivery
Add service design, growth design, or product-marketing collaboration
New markets introduce distinct behaviours or requirements
Add localized research, content, and market expertise
04 / TEAM TOPOLOGY
Evolve the team topology.
The embedded structure provides product context. The centralized practice provides
quality, career development, shared methods, and experience coherence. Both are
necessary.
STAGE 1
Lean practice
Designers operate as a coordinated central team while partnering directly with the
highest-priority product areas. The design leader acts as a player-coach and owns
strategy, standards, staffing, and critical work.
STAGE 2
Expanding practice
Designers become embedded in persistent value streams while remaining connected
through a design chapter. Senior designers begin to own broader journeys, shared
systems, and cross-team decisions.
STAGE 3
Scaled practice
The organization develops complementary structures:
Embedded value-stream designers.
Design managers accountable for team health and performance.
Staff and principal designers accountable for complex, cross-product experience
problems.
Shared design-system and UX architecture capabilities.
Enabling practices such as research operations, content, accessibility, analytics,
and design operations.
A design leadership team connecting business strategy, product direction, craft,
and organizational capability.
05 / ROLE CHARTERS
Create explicit role charters.
A job description helps recruit someone. A role charter helps that person succeed. Role
charters should distinguish accountability from participation: several people may
contribute to a decision, but only one role should be accountable for making it.
Management and individual-contributor paths should be treated as equally valuable.
Promotion should not require a strong designer to become a people manager.
EVERY ROLE CHARTER SHOULD DEFINE
01
Purpose
Why the role exists.
02
Outcomes
What should improve because of the role.
03
Scope
Products, journeys, capabilities, or teams covered.
04
Decision rights
Decisions the person owns or materially influences.
05
Responsibilities
Recurring work expected of the role.
06
Partnerships
Key relationships with product, engineering, data, marketing, and operations.
07
Performance evidence
How strong performance will be recognized.
08
Boundaries
Work the role is not expected to own.
09
Growth
Capabilities required to progress.
EXAMPLES OF DESIGN LEADERSHIP SCOPE
Product designer
Owns the quality and effectiveness of an experience within a defined initiative or
product area.
Senior product designer
Owns complex journeys, frames ambiguous problems, influences product direction, and
improves the work of adjacent teams.
Staff or principal designer
Shapes cross-product experience direction, UX architecture, major strategic
initiatives, and reusable organizational capabilities without requiring
people-management authority.
Design manager
Builds an effective team through staffing, coaching, performance management, work
allocation, and partnership with product and engineering.
Head or director of design
Connects business strategy with experience direction, establishes the operating
model, develops leadership capability, shapes investment, and remains accountable
for the effectiveness of the design organization.
06 / CAREER ARCHITECTURE
Build a transparent career architecture.
Career levels should describe increasing scope and impact, not simply years of
experience. Each level should include examples while leaving room for different forms of
excellence. A designer may demonstrate senior impact through product strategy, systems
work, research leadership, growth, or exceptional delivery.
EVALUATE GROWTH ACROSS CONSISTENT DIMENSIONS
Customer and domain understanding.
Problem framing and strategic thinking.
Interaction, visual, content, and prototyping craft.
Use of research and evidence.
Systems thinking and UX architecture.
Delivery and design quality.
Business and product judgment.
Collaboration and influence.
Development of others.
Contribution to shared capabilities.
Ownership of measurable outcomes.
LEVEL
TYPICAL SCOPE
EVIDENCE OF IMPACT
Developing designer
A defined problem with guidance
Produces sound work, seeks feedback, and follows established practices
Product designer
A feature or connected workflow
Independently delivers useful, usable, and well-executed experiences
Senior designer
A complex journey or value stream
Shapes direction, manages ambiguity, and influences cross-functional decisions
Staff designer
Multiple teams or a major product area
Resolves systemic problems and creates leverage beyond individual projects
Principal designer
Product portfolio or enterprise experience
Establishes long-term direction, architecture, and organization-wide capability
Design manager
A group of designers and their product coverage
Improves team performance, growth, allocation, and partnership
Director or head
Design organization and strategic portfolio
Improves business impact, organizational capability, quality, and leadership depth
07 / PERFORMANCE
Define what strong performance means.
Performance should be judged through outcomes, quality, behaviour, and organizational
contribution, not artifact volume or personal visibility. Not every individual can be
credited directly with a business metric. Performance should account for the person's
scope, opportunity, decisions, and contribution to the team result.
A USEFUL MODEL
Strong performance = valuable outcomes + sound judgment + quality execution + effective
collaboration + increased organizational capability
EVIDENCE MAY INCLUDE
Customer problems clarified or resolved.
Business or product measures improved.
Risk reduced before major investment.
Better decisions enabled through research.
Complex workflows made more coherent.
Quality problems prevented or corrected.
Adoption or engagement improved.
Shared patterns created and adopted.
Product and engineering collaboration strengthened.
Other designers coached or enabled.
Important lessons made reusable.
ROLE SCORECARDS
Each person should have a scorecard with:
Three to five expected outcomes.
Responsibilities that must be performed consistently.
Capabilities being developed.
Behaviours expected at their level.
Evidence that will be reviewed.
Support required from their manager or organization.
The scorecard should be reviewed when business priorities or role scope change.
08 / COACHING
Make coaching part of the work.
Coaching is most effective when it is frequent, specific, and connected to real
decisions. Coaching develops capability; sponsorship creates opportunity. Leaders should
actively connect strong performers with visible, consequential work appropriate to their
next level.
WEEKLY OR BIWEEKLY
One-to-ones
Current decisions and obstacles.
Relationships with partners.
Feedback and performance.
Workload and wellbeing.
Career-development actions.
Support required from the manager.
A one-to-one should not be consumed by status reporting.
THE WORK
Design critique
Critique improves the work by examining the problem, evidence, alternatives, and
execution. It should be psychologically safe and separate from formal performance
evaluation.
THE PROCESS
Work review
Managers and senior designers review how the person frames problems, communicates,
makes trade-offs, and follows work through implementation, not only the final
design.
DEVELOPMENT PLANNING
A small number of development priorities connected to future scope.
Development actions may include:
Owning a more ambiguous problem.
Leading research or validation.
Presenting to senior stakeholders.
Coaching another designer.
Contributing to UX architecture.
Leading a design-system improvement.
Measuring a released experience.
Working in an unfamiliar product domain.
SPONSORSHIP
Coaching develops capability. Sponsorship creates opportunity.
Leaders should actively connect strong performers with visible, consequential work
appropriate to their next level.
09 / HIRING
Build a fair and repeatable hiring system.
Hiring should begin with a capability need and evidence-based scorecard, not a recycled
job description. All candidates should be evaluated using the same core criteria, and
interviewers should record evidence before discussing their recommendations. Avoid
assessing vague “culture fit.” Evaluate whether candidates demonstrate the behaviours,
judgment, learning ability, and contribution the organization needs.
BEFORE OPENING A ROLE, DEFINE
The business and customer outcomes the role will support.
The capability gap being addressed.
Why development, partnership, or reassignment is insufficient.
The expected scope and level.
What success should look like after 6–12 months.
How the role changes team capacity and topology.
USE STRUCTURED ASSESSMENT
An initial conversation about motivation, scope, and relevant experience.
A portfolio discussion focused on decisions, evidence, contribution, and results.
A structured product or strategy scenario related to the role.
Cross-functional conversations covering collaboration and leadership.
A final review against the original scorecard.
If original work is requested, keep it small and relevant, or compensate the candidate. Existing work, structured discussion, and realistic scenarios usually provide better evidence than speculative unpaid projects.
PROTECT FAIRNESS WHEN USING AI
AI can help draft job descriptions, identify inconsistent interview feedback,
schedule activities, and summarize evidence.
It should not independently screen, rank, reject, or evaluate candidates.
Candidate data should remain protected.
Interviewers must be accountable for every hiring decision.
10 / ONBOARDING
Treat onboarding as the first development program.
A new hire's first 90 days should progressively build context, relationships,
confidence, and ownership. Every new hire should have a manager, onboarding partner,
clear first outcome, stakeholder map, and scheduled feedback checkpoints.
FIRST 30 DAYS
Understand
Learn the business model, customers, strategy, and product.
Review the Visual Roadmap and UX architecture.
Meet product, engineering, and business partners.
Observe customer research and product use.
Understand decision rights, quality standards, and team practices.
Receive access to systems, evidence, and shared artifacts.
DAYS 31–60
Contribute
Take ownership of a bounded problem.
Participate in discovery and critique.
Work with engineering on implementation.
Contribute to research or validation.
Receive structured feedback from the manager and partners.
DAYS 61–90
Own
Lead an initiative or meaningful portion of a value stream.
Demonstrate independent decision-making at the expected level.
Identify an experience or operating-model improvement.
Establish a longer-term development plan.
11 / AI LEVERAGE
Use AI to increase team leverage.
AI fluency should become part of the practice without replacing customer contact, design
judgment, or craft. Strong performance includes knowing when AI is appropriate, how to
assess its output, and when direct research or expert judgment is required. AI should
also reduce administrative work for managers, but it should not make autonomous
decisions about hiring, performance ratings, promotion, compensation, or workforce
reduction.
DESIGNERS SHOULD LEARN TO USE AI FOR
Research preparation and synthesis.
Retrieval of prior decisions and evidence.
Alternative concepts and counterarguments.
Rapid prototypes.
Content exploration and localization.
Requirements, states, and edge-case discovery.
Design-system and accessibility checks.
Specification and documentation.
Feedback and telemetry analysis.
THE ORGANIZATION SHOULD PROVIDE
Approved tools and data-use policies.
Training in evaluation and critical review.
Reusable prompts and workflow patterns.
Examples of acceptable and unacceptable use.
Methods for protecting confidential customer information.
Time to share effective practices.
Quality measures that assess outcomes rather than AI activity.
12 / PEOPLE CADENCE
Create a consistent people cadence.
These practices should support decisions rather than create administrative theatre. When
possible, routine status collection and artifact maintenance can be automated.
CADENCE
PRACTICE
INTENDED RESULT
Weekly or biweekly
One-to-ones and design critique
Better work, support, and timely feedback
Monthly
Capability and capacity review
Early identification of gaps and overload
Quarterly
Outcome and development review
Alignment between performance, priorities, and growth
Quarterly
Team-health and operating-model review
Improvements to structure, collaboration, and quality
Semi-annually
Talent and calibration review
Fair expectations, recognition, and promotion decisions
Annually
Workforce and succession planning
Deliberate hiring and leadership continuity
13 / TEAM HEALTH
Review team health with a balanced scorecard.
Metrics should be used to improve the environment, not monitor individuals. A delivery
problem may reflect unclear priorities, poor dependencies, insufficient staffing, or
weak decision rights rather than individual performance.
BUSINESS & CUSTOMER IMPACT
Progress against product outcomes
Customer task success and time to value
Adoption, engagement, and retention
Contribution to strategic capabilities
DELIVERY EFFECTIVENESS
Time from problem framing to evidence
Rework after development begins
Design coverage of priority initiatives
Cross-team dependency delays
Design debt and time to resolution
QUALITY & LEVERAGE
Usability and accessibility results
Design defects found before and after release
Reuse of shared components and patterns
Adoption of UX architecture
Number of teams enabled by shared capabilities
PEOPLE HEALTH
Role clarity
Quality and frequency of coaching
Engagement and sustainable workload
Retention of strong performers
Internal mobility and promotion
Representation and equitable access to opportunity
Leadership and succession coverage
HIRING & ONBOARDING
Time to fill important capability gaps
Candidate experience
Hiring-quality evidence after onboarding
Time for new hires to reach meaningful ownership
Retention and performance of new employees
14 / PROMOTION
Manage performance and promotion transparently.
Promotion should reflect sustained evidence of operating at the next level, not tenure,
a single successful project, or proximity to leadership. No one should discover a
significant performance concern for the first time during an annual review.
A FAIR PROMOTION PROCESS INCLUDES
Published expectations.
Regular feedback before formal review.
Evidence drawn from multiple initiatives.
Input from relevant cross-functional partners.
Calibration across comparable roles.
Consideration of available opportunity and structural bias.
A written explanation of the decision.
A clear development path when promotion is not yet supported.
WHEN PERFORMANCE FALLS SHORT, MANAGERS SHOULD
Clarify the expected result and observed gap.
Determine whether the cause is capability, context, workload, role ambiguity, or
support.
Provide specific feedback and appropriate coaching.
Establish observable improvement checkpoints.
Follow through consistently and fairly.
15 / LEADERSHIP CONTINUITY
Build leadership continuity.
A growing organization cannot depend on one design leader to provide every strategic
decision, quality review, stakeholder relationship, and coaching conversation.
LEADERSHIP DEVELOPMENT SHOULD DELIBERATELY CREATE
Designers who can lead complex initiatives.
Principals who can shape cross-product direction.
Managers who can coach and build healthy teams.
Owners for UX architecture and shared systems.
Successors for critical leadership roles.
Communities of practice that preserve knowledge.
Clear delegation and escalation mechanisms.
A leader's success should eventually be visible in the decisions the organization can make without their direct involvement.
IMPLEMENTATION
A 90-day implementation approach.
Establish clarity about work, capabilities, roles and baselines; build the people
system; then operate it, align staffing with priority value streams, and remove
practices that do not improve outcomes.
DAYS 1–30
Establish clarity
Map design work to business value streams.
Inventory team capabilities and recurring gaps.
Document role charters and decision rights.
Assess current workload, coverage, and management capacity.
Baseline delivery, quality, and people-health measures.
Identify critical single points of dependency.
DAYS 31–60
Build the people system
Publish the career framework.
Create role scorecards.
Establish one-to-ones, critique, and development-planning practices.
Standardize hiring and interview rubrics.
Introduce the 30–60–90-day onboarding model.
Identify development and sponsorship opportunities.
Define approved AI practices and training needs.
DAYS 61–90
Operate and refine
Conduct the first capability, talent, and capacity reviews.
Align staffing with priority value streams.
Create hiring plans for demonstrated gaps.
Assign ownership for shared systems and architecture.
Establish succession plans for critical roles.
Review early evidence and remove practices that do not improve outcomes.
WHAT SUCCESS LOOKS LIKE
How to tell the people system is working.
A scalable design organization is not defined by the number of designers it employs. It
is defined by how clearly people understand their responsibilities, how effectively they
make decisions together, how consistently they deliver quality, and how deliberately the
organization grows the capability of every person on the team.
Every designer knows why their role exists.
Teams understand who makes which decisions.
Performance expectations are visible and consistent.
Designers receive regular coaching and actionable feedback.
Career progression does not depend on becoming a manager.
Hiring addresses demonstrated capability gaps.
New employees reach meaningful ownership quickly.
Shared systems allow a lean team to have broad impact.
Growth adds capability without adding unnecessary bureaucracy.
Leadership capacity expands throughout the organization.
The team is evaluated by the customer and business value it enables.
NEXT / PLAYBOOK 04
Make product quality repeatable
Continue reading
Discuss growing a design team
Start a conversation