I designed management systems that connected leadership bench, role and skill gaps, capacity planning, geographic coverage, development pathways, and team listening.
A growing distributed UX organization needed intentional systems for developing leaders and allocating limited capacity. I designed and operated planning, capability, coverage, development, and listening mechanisms with leadership peers; the work made leadership pathways, skill-gap choices, and resource tradeoffs more explicit.
The UX organization was distributed across product areas, roles, levels, and geographies. Product demand exceeded available design and research capacity. Newer practitioners needed onboarding and upskilling while experienced practitioners needed credible leadership pathways.
The management problem was systemic: how to build bench strength, identify capability gaps, plan coverage, support readiness decisions, listen to the team, and adapt without fragmenting the organization.
Develop leads before growth made the gap urgent.
Identify role and skill gaps without reducing people to a matrix.
Match limited UX capacity to changing product and regional demand.
Use structured check-ins to detect friction and adjust the model.
I authored leadership-planning and organizational-scenario artifacts, co-hosted skill-gap work, developed capacity and coverage models, supported lead ramp-up and readiness evidence, and used structured check-ins to inform management decisions.
The work involved UX leaders, managers, team leads, practitioners, recruiting partners, and product leadership. I focus here on the operating system while keeping individual decisions confidential.
I evaluated where the organization needed stronger mentoring, onboarding, research and design support, product-area coverage, and continuity. The models considered interest, experience, readiness, growth timing, and the work a lead would actually need to do.
The aim was not to fill boxes on an org chart. It was to define a structure that could develop people while supporting the work.
A structured leadership session examined gaps in visual design, content, interaction design, UX strategy, and related capabilities. The group considered alternatives such as hiring, coaching, communities of practice, specialist support, and role development.
The value was the connection between capability and action. Each gap led to a decision about development, staffing, or operating support.
Coverage planning compared role mix, product demand, geography, onboarding cost, leadership capacity, and hiring constraints. Scenarios made tradeoffs visible without pretending that one ratio could describe every team.
Structured check-ins added a qualitative feedback layer. They helped test whether the planned structure was supporting people and where coaching or operating adjustments were needed.
The operating rhythm linked organizational demand to leadership development and team health.
Gather product demand, manager input, practitioner feedback, and team-health signals.
Describe capacity, role mix, capability gaps, leadership bench, and coverage pressure.
Compare leadership, staffing, and geographic support scenarios.
Create lead pathways, ramp-up support, coaching, and capability plans.
Evaluate readiness and operating health through structured management review.
Change coaching, staffing, coverage, or structure as the organization evolves.
The clearest outcome was planning infrastructure that made leadership pathways, capability choices, and resource tradeoffs explicit.
Planning connected organizational need with lead responsibilities, development, and readiness evidence.
Hiring, coaching, specialist support, and role development could be compared as choices.
Scenario planning connected role mix, geography, product demand, and leadership capacity.
Privacy boundary: outcomes are reported only at the aggregate system level; no individual or confidential organizational detail is used as a public result.
Leadership bench, role clarity, capability, coverage, and team listening are interdependent. Optimizing one in isolation creates pressure elsewhere.
The durable lesson is to make the tradeoffs visible while protecting the dignity and privacy of the people inside the system.
Dated leadership, planning, capability, coverage, development, and listening artifacts establish the work. None is reproduced here.
Official MathWorks pages provide only public organizational context. Every case visual is an original anonymized redraw, and no identifiable or confidential organizational detail is published.