Skip to main content
A change has delivered value when the people who own the outcome accept a measured result, not when it goes live. Measuring it means going back to the baseline you set in Discover and Define and recalculating with like-for-like evidence.

Recalculate against the baseline

1

Use comparable cases

Compare the same kind of work before and after: the same segment, the same volume band, normal and peak cycles kept apart. A change measured on easier cases than the baseline overstates itself.
2

Count the full cost

Include what it takes to run the change: operating costs, the review burden on people, the exceptions that still go to a person, and the work that moved somewhere else rather than going away.
3

Label every number

Say where each figure came from and how confident it is. Combine the effects of several changes rather than adding them, because they overlap.
4

State the limits

Say what the measure doesn’t cover and what would change it. A bounded claim that holds up is worth more than a large one that doesn’t.
If the evidence isn’t there yet, collect comparable proof first and recalculate before anyone makes the claim.

Which numbers carry which case

The fields that carry a value case depend on what you’re proving. A cost case lives on Active Work Time × Annual Volume. SLA, revenue and risk cases lean on Cycle Time and the narrative fields. See How Advisor uses your process attributes for which attributes carry each case and how precise they need to be.

Who does what

When the value is verified, the first iteration is complete. What changes next is a decision, not a default. See Maintain and improve agents.

Where to go next

How Advisor uses your process attributes

Which attributes carry each kind of value case.

Maintaining your process attributes

Raise confidence in the numbers a decision depends on.
Need help? Use the in-app chat — click the chat bubble in the bottom-right corner of Within (staffed 24×5) — or email support@within.ai.