Evidence-Based Management
EBM does not replace any framework; it sits above them and addresses a different question. Scrum describes how a team works, while EBM explains how an organization knows whether that work is actually achieving anything.
The Four Key Value Areas
| What they describe | Key Value Area | What they measure |
|---|---|---|
| Market Value | Current Value | The value that the product delivers today to customers and the organization. |
| Unrealized Value | The potential value that could be realized if the needs of all possible customers were met. | |
| Ability to Deliver | Time-to-Market | How quickly the organization delivers and learns from customer feedback. |
| Ability to Innovate | How effectively the organization delivers new capabilities. |
The four areas function as complementary lenses, and no single one is sufficient on its own. A high Current Value combined with a slow Time-to-Market or a limited Ability to Innovate describes an organization that is coasting on past success: it delivers value today, but is ill-equipped to continue doing so once the market shifts.
The empirical management cycle
EBM applies the same cycle to management that Scrum applies to the product. In each iteration:
- Formulate a value hypothesis and decide in advance which metric will be used to test it.
- Act by taking the smallest step that allows for learning, rather than executing the entire plan.
- Measure the actual impact on Key Value Areas.
- Adapt: continue, pivot (adjust course), or abandon the hypothesis.
Goals are organized into three levels with progressively shorter time horizons—a strategic objective, intermediate objectives, and immediate tactical objectives—such that each iteration of the cycle addresses a tactical objective which, in turn, serves the higher-level objectives.
Why activity is not enough
The number of features delivered, points completed, or releases made are all measures of output. They indicate what has been produced, but not the value generated or whether the organization will be able to continue producing it. A team could increase its velocity for an entire quarter without shifting any of the four areas—and this is precisely the scenario that EBM is designed to make visible.
EBM and the product operating model
EBM serves as the evidence anchor for the Scrum.org Agile Product Operating Model. Its guiding principles, published in 2026, link each principle to a concrete measure used to verify whether it is truly being upheld; the principle of "outcomes over outputs" is associated with the trend in Current Value.
The logic is the same as that within the framework itself: a principle without an associated metric is merely a statement of intent, and the EBM exists so that such statements of intent can be put to the test.
Common errors and anti-patterns
- Measuring activity instead of value. Replacing Key Value Areas with counts of deliverables sets the organization back to square one.
- Focusing on a single area. Optimizing Current Value at the expense of the Ability to Innovate leads to good quarters but bad years.
- Metrics without hypotheses. Measuring without first stating what was expected to happen turns data into an *ex post* justification.
- A dashboard that no one uses for decision-making. If no decisions change when the numbers change, the measurement system is merely decorative.
References
- Scrum.org. Evidence-Based Management Guide (2024). Framework page · Online guide.
- Scrum.org. The Guiding Principles of the Agile Product Operating Model (2026).
Resources
🏦 Agile Product Operating ModelSkill Arena · Scrum Manager