Integrating UX into capacity planning

"Capacity Planning is the process of right-sizing the 'Total Project Demand' with the forecasted Team Capacity. Most UX teams have no idea what their capacity is. Fewer still have a process for calculating it and using it during quarterly planning activities with their counterparts in Product Management & Engineering to ensure teams don't commit to more work than they can handle."

"There's almost never enough UXers to staff 1 per engineering team. It creates siloes within the UX org that require a lot of effort (and meetings) to overcome. It results in early career UXers being thrust into projects they're not ready for and Lead UXers doing low level mockup work. Most relevant to our discussion here: Capacity planning, dependency management, and throughput tracking gets extremely messy."

Capacity planning matches total project demand with forecasted team capacity, yet most UX teams lack clear capacity calculations or processes for quarterly planning coordination with Product and Engineering. Beyond capacity calculation, quarterly planning requires strategy and OKR alignment, work prioritization and estimation, and executive input. The traditional embedded UX model, where individual designers join engineering squads, creates organizational challenges including insufficient UX staffing ratios, organizational silos requiring extensive coordination, misalignment of career-level designers with project complexity, and complicated capacity planning and dependency management. A recommended alternative treats the UX team as a separate squad assigned to specific sub-domains rather than embedding individual designers within engineering teams.

Read at Medium