The problem
The team became smaller. The portfolio didn’t.
After a reduction in force, nine designers became six while critical programs across portable products, headphones, setup, configuration, and home theater still needed support. The change also exposed an existing weakness: software design often entered hardware programs after the most consequential decisions had already hardened.
I could spread specialists more thinly, or redesign how the team worked.
Before-and-after coverage map
Show the staffing change and unchanged product roadmap at a high level. Focus on disciplines and portfolio areas rather than identifiable employees.
Decision one
Make priorities, and tradeoffs, visible.
I established explicit criteria for dedicated staffing: a clear business objective, a blocking customer issue, or a committed roadmap date. Strategic commitments received embedded ownership; less-defined opportunities received office hours and targeted working sessions rather than automatic staffing.
This forced difficult choices, but it replaced hidden overload with transparent portfolio decisions. Teams could see what we were protecting, what we were releasing, and why.
Prioritization framework
A simple three-part model followed by two tiers of engagement: embedded partnership for commitments; guidance and limited working sessions for exploration.
Decision two
Move software expertise upstream.
Rather than treating hardware and software design as sequential specialties, I paired ownership earlier, through incubation, creation, and realization. Shared problem sessions and all-team critique replaced discipline-specific status reviews.
The new model let systems thinking influence component decisions, setup requirements, and launch scope before expensive constraints were locked in.
Development model
Before: hardware decisions, handoff, then software inherits constraints. After: paired hardware and software ownership across incubation, creation, and realization.
Decision three
Grow people differently, not uniformly.
I matched development opportunities to business need, individual readiness, and specialist strengths. Supported exposure became independent leadership: designers moved from smaller programs into strategic cross-system work with coaching that gradually shifted from answers to context and decision support.
That protected essential specialization while increasing the team’s ability to lead ambiguous, interconnected programs.
Development arc
An anonymized progression from smaller professional programs, to a supported strategic assignment, to independent priority and clarification decisions.
What changed
We maintained strategic coverage by making tradeoffs visible.
With roughly one-third fewer designers, the team continued covering the same strategic roadmap. We deliberately reduced support for lower-priority enhancements, while earlier cross-system collaboration improved the quality and realism of product decisions.
-
≈33% fewerDesigners after the organizational change.
-
Same coverageAcross the company’s strategic roadmap.
-
More capabilityThrough paired ownership, shared rituals, and targeted development.