THE DIRECT ANSWER

A tradeoff conversation starts once you know an addition does not fit. Put the current commitment and the new request side by side, then compare two or three feasible options using the same fields: what is delivered, when, how many hours, and who must approve it. Recommend one, ask the person who owns the scope to choose, and record what was given up. “If we add this, what comes out?” only works when you can name what comes out.

Start where the first reply ended

The first reply to a new request acknowledges it and checks its size. This conversation comes next: the request is understood, the estimate is known, and it does not fit the existing commitment. Your job now is to turn “it does not fit” into a small set of choices someone with authority can make.

In the fictional Scope Swap case, five hours remain. They are already allocated to four hours of core work and one hour of mandatory handoff. The requester wants a two-hour comparison page. Including it without another change means seven hours of work against five available.

Name what could come out

A swap is only a real option when you can name the work it removes. In the Scope Swap case, the scope owner’s record splits the four core hours into a two-hour data section and a two-hour recommendations section. In a real project, use the items in your own agreed record rather than inventing a convenient split.

The handoff is not a free hour to trade away. Removing it still leaves six hours of work against five, and it leaves the receiver without a usable transfer. If someone wants to reduce the handoff, treat that as a separate decision for the person who owns acceptance.

Compare the options on the same fields

Describe every option with the same four fields so the owner can compare them quickly: delivered outcome, timing, hours against hours available, and approval needed. Two or three options are usually enough. Do not include an option you already know is infeasible.

  • Option A, swap: data section, comparison page, and handoff. Two plus two plus one is five hours against five. The recommendations section leaves this delivery. Needs the scope owner to approve removing it.
  • Option B, defer: the original core and handoff, four plus one is five hours against five. The comparison page waits for a later window. Needs the owner to accept the delay; the later window is a proposal until confirmed.
  • Option C, add capacity: everything, seven hours. Feasible only if two extra hours are explicitly approved and actually available before the delivery.
  • Not an option: cutting the handoff to make room. It still needs six hours against five.

Recommend against the purpose, not your preference

A recommendation helps the owner decide faster, as long as you explain its criterion and do not present it as the decision. “I recommend B because it keeps the agreed package intact; if the comparison matters more for this delivery than the recommendations, A is the better swap.” That sentence tells the owner what would change your recommendation.

Close with a question that can be answered: “Which option do you approve?” If the person in front of you cannot approve any of them, ask them to pass the brief to the person who can, and keep the request pending until that person answers.

Record the choice and what it cost

Send a short confirmation: the selected option, what was removed or deferred, the delivery time, who approved it, and any capacity assumption. Name the item that left the delivery; a record that says only “scope updated” hides what was given up. Silence does not approve an option unless an existing agreed process says it does.

Employees may use this brief for internal requests their manager must rank. Freelancers may need the confirmation to cover fees or a change order under their actual agreement. People working across several roles should offer extra capacity only from hours that are genuinely free elsewhere. The wording can change; the arithmetic and the approval stay the same.

AUTHORED FICTIONAL EXAMPLE

A conversation you can rehearse

Authored fictional example, the Scope Swap case. Five hours remain, allocated to four hours of core work and one hour of mandatory handoff. The core is recorded as a two-hour data section and a two-hour recommendations section. You have already told the requester that the two-hour comparison page does not fit as the plan stands.

A first reaction

“So we can do the comparison if we drop something. What do you want to drop?”

A more specific response

“Three options for this delivery. A: swap the recommendations section for the comparison page. That is five hours, and the recommendations move out. B: keep the original package and schedule the comparison separately. Five hours, and the comparison waits. C: keep everything. Seven hours, only if two extra hours are approved and actually free. I recommend B because it keeps the agreed package intact; if the comparison matters more than the recommendations for this delivery, A is the better swap. Which do you approve?”

The first reaction hands the owner an open question with no information. The better response names what each option delivers and removes, uses the same arithmetic for each, and ends with a decision the owner can make.

Before you act

  • Confirm the addition and its estimate first.
  • Name the specific items that could come out.
  • Keep the handoff out of the trade unless its owner decides.
  • Compare options on the same four fields.
  • Recommend one and say what would change your recommendation.
  • Record the choice and the item that was given up.

Common questions

How many options should I present?

Usually two or three feasible options. Add another only if it is materially different. A long list of loosely described possibilities moves the analysis work to the owner instead of making the decision easier.

What if the owner picks parts of different options?

Treat the combination as a new proposal and recalculate it before agreeing. Keeping the recommendations and adding the comparison, for example, brings the work back to seven hours unless something else changes.

What if the person asking is not the scope owner?

Give them the same brief and ask them to route it to the person who can approve it, or ask who that person is. Keep the request pending until the owner answers; a requester’s preference is not the same as an approved change.

Original practice guidance using the fictional Scope Swap case. Decision rights and change processes vary by context. This guide is general practice material, not legal advice.

Source basis: an original scenario-based practice framework. The example is fictional, and no external research finding or measured effectiveness is claimed. Read the editorial method.