Was the agreed capability made available?
Delivery does not show whether the customer changed how they operate or achieved the result.
PromiseArc Methodology
Keep the customer Promise connected to the decisions that follow.
The Promise Arc is a six-stage operating model for defining the result a customer bought and deciding what to do when the Evidence does not support it.
It gives everyone responsible for the relationship a shared way to discuss success and what needs attention next.
- 01
Promise
Why the investment was made
- 02
Outcome
What success must look like
- 03
Value Path
What has to happen
- 04
Evidence
What proves progress and Value
- 05
Cadence
When teams review
- 06
Decide & Act
What happens next
Start with the Promise
Start with the business result that justified the investment.
The commercial record shows what was purchased. The customer Promise explains why the purchase mattered: the business change or result the customer expected to achieve.
The Promise remains the reference point as responsibility moves from sale to post-sale operation. An Outcome definition can change when customer priorities change, but the original Promise and earlier definitions stay visible. Record why it changed and recheck alignment rather than rewriting the history.
The operating cycle
Six stages keep the customer story connected.
Each stage answers a different operating question without losing sight of why the customer invested.
- 01
Promise
Keep the business result that justified the investment visible across teams.
- 02
Outcome
Express it as an observable result and how the customer will recognize success. Agreement on the definition does not prove it occurred.
- 03
Value Path
Connect the work, adoption, dependencies, and stakeholders required to reach the Outcome.
- 04
Evidence
Keep support, gaps, and contradictions visible for the next decision.
- 05
Cadence
Review the Outcome, Value Path, and Evidence throughout the relationship.
- 06
Decide & Act
Make the Risk, decision, Action, and owner clear.
Three different conditions
Delivery, Adoption, and Value answer different questions.
Implementation, usage, and business results are different conditions. Delivered is not adopted. Adopted is not Value realized.
Is the customer operating in the intended way?
Adoption can support an Outcome without proving it was realized.
Does the Evidence show the result the customer bought?
Value requires supportable Evidence tied to the Outcome, not delivery or activity alone.
Evidence over scores
Evidence before assertion.
Establish what the Evidence supports, make uncertainty visible, and act on what remains unresolved.
Evidence can come from existing systems, operational records, delivery facts, customer stakeholders, financial measures, or other relevant sources. Keep its source and date, match it to the conclusion, and leave people responsible for judging whether it is sufficient.
A baseline may exist, be reconstructed from credible sources, or remain unknown. When history cannot be established, work can continue from the current condition and track what changes next; earlier improvement remains unproven.
An Outcome does not have to be expressed as financial ROI. It can be measured numerically or through supported observation. For example, check whether every priority handoff reaches a named owner with the required context inside the agreed window. Qualitative does not mean unsupported, and quantitative does not automatically mean credible.
Evidence can show progress, achievement, uncertainty, or a result that falls short. Keep gaps and contradictions visible. An internal assessment is not customer confirmation. Agreement on the Outcome definition establishes the intended result; customer recognition records the benefit they see. Realized Value still requires validation against Evidence for that same Outcome. A before-and-after change alone does not prove its cause.
Risk, Action, and cadence
Turn gaps into accountable Action.
Evidence matters when it changes what the team does. Regular reviews give the people responsible for the next customer-facing or commercial decision time to respond before a gap becomes a renewal surprise.
- 01
Detect
Review what supports progress, what contradicts it, and what is missing.
- 02
Diagnose
Explain the gap against the Outcome or Value Path. Keep hypotheses labeled until Evidence supports them.
- 03
Act
Choose the next accountable Action and make the owner clear.
- 04
Verify
Return to the Evidence and record what, if anything, changed.
Before renewal
Renewal starts long before the renewal date.
Regular reviews build the Value record and give teams time to address gaps before renewal.