The Trade-Off Exercise Every Leadership Team Avoids

A leadership team agrees to a new priority. The goal is worthwhile. The opportunity is real. Everyone understands why it matters.

Then the meeting ends, and the people responsible return to calendars and work plans that are already full.

What changed?

The organization added a commitment. Whether it created the capacity to deliver on that commitment is a separate question.

That is the question this exercise is designed to surface:

If we say yes to this, what will we stop, delay, or reduce, and whose capacity will that actually free?

It sounds straightforward. Answering it requires a leadership team to make its choices visible.

A proposal can fit within a budget while still placing demands on people who have little room to absorb them. It may require the same manager who is leading another launch, the same analyst supporting three departments, or the same executive whose approval every team needs.

Capacity includes the time to perform the work, the attention to make decisions, and the coordination needed to move it across organizational boundaries.

A manageable opportunity can still exceed capacity

Consider an illustrative nonprofit preparing to launch a new partnership. The launch requires no additional hiring, and the direct expenses are manageable. But it also needs communications support, changes to participant intake, staff training, and recurring leadership decisions.

Each request looks reasonable on its own. Taken together, they compete with existing commitments.

The leadership decision is therefore larger than "Should we pursue this partnership?" It includes "What can we realistically deliver alongside it?"

Here is a practical exercise to work through before approving the next significant initiative.

1. Name the outcome you are trying to achieve.

Begin with the result that matters. "Launch a partnership" describes an activity. "Expand access for a particular community" describes an intended outcome.

That distinction creates room to consider different approaches. A smaller pilot, a later launch, or an improvement to an existing program might serve the goal with different demands on the organization.

Ask: What evidence supports this need, and what would meaningful progress look like?

2. Identify the people and decisions the work depends on.

List the functions involved, including those contributing behind the scenes. Ask the people doing the work to estimate the demands and flag uncertainty.

Where will implementation require shared staff, specialized knowledge, approvals, or changes to someone else's workflow? What are those people already committed to delivering?

Avoid treating "the team will absorb it" as a capacity estimate. Name what absorption would mean in practice.

3. Compare a few feasible choices.

Consider proceeding at the proposed scope, reducing the scope, sequencing the work differently, or deferring it.

For each option, discuss the likely benefit, the capacity required, the work displaced, and the consequences for affected stakeholders.

Keep the options open to challenge. Someone may identify an approach the initial proposal overlooked. The way the question is framed should not quietly decide the answer.

4. Make the displacement explicit.

Complete this sentence:

To pursue ______ during ______, we will stop, delay, or reduce ______, freeing capacity from ______.

Then check whether the trade-off works.

Canceling a meeting does not necessarily free the specialist needed to implement a new system. Delaying one department's project may do little to relieve a bottleneck elsewhere.

The capacity released needs to match the capacity required, in the right people, with the right skills, at the right time.

If the team cannot identify a workable trade-off, it needs to revisit scope, timing, or resourcing.

5. Record the decision and when you will reconsider it.

Name the decision owner, the commitments being changed, and the people who need to know. Explain why the chosen trade-off is justified, including who will bear its costs.

Set a review point and identify what would prompt reconsideration: a missed milestone, a workload assumption that proves wrong, or evidence that the expected benefit is unlikely to materialize.

An explicit decision can still be mistaken. Recording its assumptions gives the team something concrete to learn from.

The useful output is a shared commitment: this is what we will pursue, this is what will change to make it possible, and this is how we will assess whether the choice is working.

That is part of the thinking behind Chase Pack: helping organizations connect priorities to the decisions, ownership, and operating routines required to carry them out.