Evidence-Based Management (EBM): Measure Value, Not Just Velocity

WHY IT EXISTS: Many teams "do Agile" but can't prove they're delivering value. EBM was created to move beyond activity-based metrics (like velocity or story points) and focus on measuring actual outcomes, enabling organizations to make strategic investments based on evidence, not intuition.

THE MENTAL MODEL: Think of EBM as a fitness tracker for your product and organization. Instead of just "feeling" productive, you track specific, vital signs across four key areas to get a holistic view of health. This data helps you set goals, run experiments (like trying a new process), and see if those changes actually improved your fitness.

HOW IT WORKS: EBM is built on four Key Value Areas (KVAs). First, Current Value (CV) measures the value your product delivers to customers today. Second, Unrealized Value (UV) identifies the potential future value by meeting new customer needs. Third, Time to Market (T2M) measures how quickly you can deliver new value. Fourth, Ability to Innovate (A2I) measures your effectiveness at delivering new capabilities without being bogged down by debt. You measure metrics in these areas, set goals, and run experiments in a continuous improvement cycle.

WHEN TO USE IT: Use EBM when you need to move from a "feature factory" to an outcome-driven approach. It's ideal for prioritizing work against strategic goals, justifying decisions to leadership, and creating a shared understanding of what "value" means across the organization. It helps answer the question, "Is what we are doing working?"

WHEN NOT TO USE IT: EBM is not a prescriptive process or a tool for performance management. Using its metrics to punish teams is a misuse that creates fear and gaming the system. It's also less effective in the earliest "zero to one" stages of a product where the problem space is too chaotic to establish stable metrics.

ONE CANONICAL EXAMPLE: A team notices their Ability to Innovate (A2I) is dropping because they spend 80% of their time on bugs. Their Time to Market (T2M) for new features is consequently very high. They hypothesize that dedicating 20% of their capacity to reducing technical debt for one sprint will improve A2I. After the sprint, they measure again. They find bug-fixing time dropped to 60% and their cycle time for a small feature improved. This evidence supports continuing the investment in technical debt reduction.