When a Buyer Changes the Success Measure Mid-Evaluation
An evaluation may begin with one goal and later shift to another. Treat that as a change to clarify, not an invitation to reinterpret earlier evidence until it appears to prove the new goal. A stable record helps both teams understand what has actually been tested.
Preserve the original criterion
Record the initial objective, the evidence gathered and the date of the discussion. Keep that history even if the buyer now prefers a different measure. Do not imply that an earlier demonstration answered a question it was not designed to address. If the change is only the seller’s interpretation, confirm it through the existing authorized relationship before adopting a new criterion.
Describe the new measure and its consequence
State what the buyer now wants to learn and which earlier evidence remains relevant. Identify any additional data, participant or review that may be needed. Avoid copying unnecessary customer information into practice exercises. A revised success measure can change the evaluation scope without establishing a product defect, a guaranteed outcome or a new contractual commitment.
Agree on the next comparison
Choose a clear next learning step and record how its result will be interpreted. Keep unknowns visible rather than altering a score to make the opportunity look consistent. NIST’s risk-management materials provide general context for reviewing automated assistance; they do not validate an individual sales conclusion. Human review should follow the team’s actual process and the buyer’s confirmed decision needs.
Copyable worksheet
Use one row for each field. Mark unknown information clearly and retain the original records.
| Field | Your note |
|---|---|
| Original success criterion | ____________________ |
| New criterion and confirmation source | ____________________ |
| Evidence still relevant | ____________________ |
| Additional review needed | ____________________ |
| Next learning step and interpretation | ____________________ |
Worked example
Illustrative example: a fictional buyer initially evaluates ease of handoff, then asks about reporting completeness. The seller preserves the first result and defines a separate reporting exercise. The team does not relabel the earlier demo as proof of a requirement that had not yet been raised.