Player‑coach roles ask one person to do two jobs well. How ready is your org?
High‑fidelity screens and a stronger design team, in one 50‑hour week. Below is a typical team’s week. Answer six questions to make it your org’s, and see which player‑coach it can support today.
A typical org can support a balanced player‑coach today.
A typical team’s result
A typical org can support a balanced player‑coach today.
Invest next1Design system2AI practice3Team load
Design system first: 4h back, lifts quality and speed.
With a balanced player-coach (7h hands‑on, 8h leading)
Your answers- Org
- Scale-up
- Role
- Mostly player
- Design system
- Partial
- AI
- Everyone's own
- Strategy
- Fuzzy
- Load
- Full
- Seniority
- Mixed
6 designers across 4 squads. A partial design system, everyone using AI their own way, a strategy that's still forming, a mixed design team at full load. A starting point: change any answer below to match your org.
Tune it for your org Your numbers, in hours
Tune it for your org
These are my numbers. Put in yours and the week redraws.
- people
Everyone who reports to the lead. Each one adds a weekly 1:1 to the week.
- squads
Product teams with their own roadmap.
- of 4
The rest run on the designers alone.
More inputs meetings, managing up, hiring, the week itself
- h/wk
Standups, planning and reviews, per squad, per week.
- h/wk
Time with the product and engineering leads.
- h/wk
Your manager, exec reviews, the leadership staff meeting.
- h/wk
With each squad's PM and engineering lead, for the squads the lead sits in.
- h/wk
1:1s, feedback and growth, per designer, per week. Shapes quality, team health and attrition.
- h
Sourcing, interviews, debriefs and onboarding.
- h/wk
What the lead actually works, not what the contract says.
- %
How much more the lead's hands-on hours produce with a shared AI practice. Changes outcomes, not hours.
An example week for a typical design team.
What this week means for the business
Which player‑coach you need
The same title covers three jobs: the coaching, the balanced and the producing player‑coach. Here is the model’s best split for three teams the size of yours; where the foundations are still being built, the coach side takes the week.
Forming
The design system is drifting or on version one. Crit and reviews are being rebuilt. Strategy and the trust with product and engineering are still settling.
- committed
- 46h
- leading
- 3h
- hands-on
- 1h
The coaching player-coach. Meetings and fixing take most of the week, and what's left belongs to the design team. Hands-on time comes back as the foundations hold.
Structuring
Typical teamRituals are running. The design system is adopted but its rules are still argued. Product and engineering trust design most of the time.
- committed
- 35h
- leading
- 8h
- hands-on
- 7h
The balanced player-coach. What the org leaves of the week splits between the work and the design team, and both get squeezed.
Healthy
The design system runs as a product. Strategy is clear. A senior, steady design team with partners who bring design in early.
- committed
- 25h
- leading
- 9h
- hands-on
- 16h
The producing player-coach. It works here because the design system, rituals and strategy steer the design team, so the lead can design.
Even the healthy team holds about 16 of the 28 hands-on hours a mostly-player role is usually expected to give. The expectation describes the work, not the week the org leaves around it.
How the model worksEverything in hours per week
The lead’s week: 50 hours, the calendar
Every org takes its share first: the lead sits in about 2 of 4 squads’ standups, planning and reviews (4h each), plus a 1h leads sync with product and engineering. That counts as partners time. Then the design team’s conditions commit more: polishing screens on a drifting design system (5h), reviewing everyone’s AI output (4h, plus 3h aligning it on a drifting design system), re-aligning on an unclear strategy (6h), firefighting an over-capacity design team (6h). Good conditions still need upkeep, about 2h each a week. When designers leave, interviewing their replacements lands here too. The slider splits what’s left between leading and hands-on.
The design team’s week: 6 designers × 40 hours
Each condition costs the design team hours: a drifting design system up to 28h of one-offs and polishing, an unclear strategy up to 30h of restarts, an over-capacity design team up to 24h blocked. Every lead hour wins some back: 3 team hours per hour of direction, 2 per hour of craft, 2 per hour with partners. Work that ships below the bar comes back as rework, more when crit is thin. Velocity is the share of the design team’s hours that ship and stay shipped.
Every org ships some features without design. The design system decides what that costs: on a drifting one the lead spends about 3h a week cleaning up and 1h more answering for the drift; on a trusted one those features add about 8h a week to what ships.
People time and attrition
6 designers need about 12 hours of the lead’s time a week: 1:1s, crit, growth. A mostly junior team needs about half again as much; a mostly senior one, a quarter less. An unmentored design team works up to 24 team hours a week slower. Below 80% of the need, designers start to leave, up to 35% a year, more on an over-capacity design team. Each one costs the lead about 60 hours to replace, and the design team an empty seat for about 10 weeks.
Quality: the share of shipped work at the bar
It starts from the design system (48%, 58%, 66% for drifting, partial and trusted) and adds percentage points: up to 12 for crit that covers the design team, 0.6 per hour of craft, 0.3 per hour of the lead’s papercut fixes. Everyone’s own AI on a drifting design system takes 8 away. A lead with less than 8 hours of hands-on work gets less weight in crit.
Team health: points out of 100
45 to start, up to 40 more as the people need is met, minus 25 for an over-capacity design team, 0.5 for every hour the lead spends fixing what’s broken, and 10 when the lead produces more than 18 hours a week.
Rebalance searches the week for the best split under these rules, for your design team and what you tune for, with team health as a floor it won’t trade away. Where it’s probably wrong: it doesn’t count reorgs or launches, which can swallow a lead’s week on any team.
The hours come from leading design teams, checked against the research linked on each event. Read them for the shape of the trade, not the decimals.
Reading behind this: Will Larson on tech lead management and team sizing, Charity Majors on the engineer/manager pendulum, Peter Merholz on who owns design quality, and Sparkbox’s design system maturity model. The stages are a synthesis; none of them publishes hours.
One person can do both jobs when the org gives them the hours.Hire the player-coach your org can support today, and build the ground for the one you want next.
Need a design leader who works like this?
Design and engineering
Kustomer
“He didn’t just make things look better — he changed how the team thought about the problem.”
David Drucker, Founding Engineer, Kustomer