Capacity informs how well/fast you can execute through your priorities, which can sometimes mean that you should reprioritize according to your available throughput (“Capacity says we’ll have this 10th thing next year, we need it this year, let’s reprioritize). But unless you have specific time horizons for your wants/needs, capacity and priorities aren’t as related as most people think.

You should prioritize the things that will have the highest impact to your customers or your business. That could be:

- a mission critical infrastructure change - a small bug that is driving people nuts - a differentiating new feature - a whole new product that will take a long time to build

Good prioritization facts in multiple criteria. Bad (most common) prioritization is a function of loudest voices yelling.