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.
Learning roadmaps rarely slow down. They expand. New product rollouts. Compliance updates. Sales enablement cycles. Leadership programs. Platform changes. Localization requests. What used to be a manageable pipeline has become a constant stream of "must-deliver" moments. But team capacity doesn't expand at the same pace. That mismatch is why many enterprise L&D initiatives stall. Not because the strategy is wrong, or the vision is unclear, or the business doesn't value learning. They stall because execution bandwidth gets stretched past its limit.
Every January, leaders are told to do the same thing: set ambitious goals, map out the year, and commit to executing harder than before. We frame this as discipline or vision, but more often than not, it is a ritual of pressure. The assumption is that success comes from wanting more and pushing faster.
I can imagine where you might be coming from with this question. Like so many of us, you may have seen strategy processes consumed by envisioning what could be, heavy on big-picture vision but light on what it might take to get there. The resulting strategies can struggle to offer practical guidance. On the flip side, I have also seen strategy processes cling too tightly to what we're comfortable committing to, inadvertently reinforcing organizational inertia.
