Moving Goalpost

Renegotiate from learning, not blame.

Moving Goalpost

What this fixes

The customer keeps changing the requirements after work has started, and every conversation becomes “That’s not what we agreed.”

Customers often understand what they really need only after seeing the work. This tool surfaces that learning so both sides can renegotiate from today’s understanding instead of yesterday’s assumptions.

How this works

Imagine this: A client keeps “adding” to a dashboard build. Instead of arguing about scope changes, the team compares what the client understood at the start with what they understand now. They realise that seeing the first version taught the client what they actually needed. The discussion shifts from blame to renegotiation.

Capture then and now. Record what the customer understood at the start and what they understand now. Capture both privately first, so everyone gives an honest view before comparing.

Make the learning visible. Lay “then” beside “now”. The difference is the learning. Treat it as something both sides discovered, not something one side did to the other.

Renegotiate from today’s understanding. Use the shared learning to agree on any changes to scope, time or cost. The negotiation still happens-it simply starts from shared understanding instead of blame.

Time required

Team ✓   About 30–45 minutes, depending on how far the understanding has drifted and how much needs renegotiating. The then-versus-now capture is quick; the renegotiation takes the most time.

The time required is indicative and will depend on the scale of the change and the number of people in the conversation.

The facilitator should read the short facilitation guide first - about 6–8 minutes. It is a downloadable PDF on this page.

When to use

Bring a live situation where the customer’s requirements have shifted since you started - and the conversation is turning into a fight about scope.

Use it whenever:

  • the customer’s requirements keep changing, and it’s starting to feel adversarial
  • you’re about to have a “that’s not what we agreed” conversation
  • scope has grown, and you need to renegotiate without blame poisoning the relationship
  • the customer has seen the build and now wants something different
  • you suspect the change reflects real learning, not just indecision

What you get

  • A clear then-versus-now picture of what the customer now understands that they didn’t before
  • A shared understanding-shift that both sides agree changes the plan
  • A renegotiation grounded in learning, not blame - with the relationship intact

You’ve done it well when: the conversation has moved from accusation - “you’re changing scope” - to shared learning - “here’s what we both understand now, so here’s how the plan changes.”

What you’ll notice

  • How quickly the tone shifts once the change is framed as learning, not creep
  • That the customer usually did learn something real - the change wasn’t arbitrary
  • How much easier is renegotiation when no one is defending a position

Why this works

Customers often understand their real needs only after seeing the work. Capturing what they understood then and what they understand now makes that learning visible. Once the shift is recognised, the conversation moves from blame to shared understanding, making it easier to renegotiate scope, time or cost fairly. Understanding the learning comes first; deciding whether to accept the change comes second.

What you need

The people from the original conversation. Whoever was part of the first requirement discussion - on both sides. Without them, someone else reconstructs “then” from memory, and usually gets it wrong.

A live change to work with. A real, current situation where the customer’s requirements have shifted - not a hypothetical. The tool works on a specific change, not scope management in general.

Both understandings are captured honestly. What the customer understood then, and what they understand now - captured privately first, so neither side performs. This honest before-and-after is what the whole tool rests on.

A facilitator. One person holds the tone: never debating whether the requirement “really” changed, always asking what the customer understands now that they didn’t before. The capture sheet carries the then-versus-now and the renegotiation.

Steps

  1. Frame the conversation (3 min). Set the tone out loud: this isn’t “what did you change”; it’s “what have we learnt since we started.” Name that you’re here to understand the shift, not assign fault.
  2. Capture “then” privately (7 min). Each person writes independently what the customer understood at the start - the original shared picture of what was needed. Privately first, so no one performs for the room.
  3. Capture “now” privately (7 min). Each person writes independently what the customer understands now - what’s become clear since, and what changed it (often: seeing the build).
  4. Make the learning visible (8 min). Lay “then” beside “now” and name the gap together as learning - “here’s what we both understand now that we didn’t then.” Not “scope you added”; a shift that happened to both of you.
  5. Renegotiate from the learning (15 min). With the shift owned by both sides, renegotiate scope, time or cost from the new shared understanding. Agree on how the plan changes, and record the agreed change before moving on. This is where the tool pays off - don’t stop before it.
  6. Confirm the shift is shared (5 min). Check that both sides agree on what changed and how the plan now reflects it. If it still feels like one side is conceding, the learning wasn’t made visible - go back to step 4.

Output

  • A then-versus-now record of what the customer now understands that they didn’t before
  • A shared understanding-shift that both sides agree changes the plan
  • A renegotiated scope, time or cost - grounded in learning, not blame

Important rules

  • Never debate whether the requirement changed. That argument - “you changed it” / “no I didn’t” - ends the conversation. Ask instead what the customer understands today that they didn’t understand then. That question stays curious; the other one turns defensive.
  • Capture privately first. Have each side write “then” and “now” before comparing, so neither performs or is influenced by the other. The honesty of the before-and-after is what makes the learning legitimate.
  • Understand first, then negotiate. This tool does not remove negotiation - it makes negotiation start from shared understanding instead of blame. It is not a license to accept every request; it’s a way to renegotiate the real ones fairly.
  • Frame the difference as learning, not fault. The gap is “what we both understand now,” never “what you added.” The moment it becomes an accusation, the tone collapses and you’re back to defending scope.

Planning to facilitate this activity? Access the resources below to get started.

MIndn
Execution must be smooth. Not chaotic or stressful.
Built by Witmer.