Discovery-Option-Action Cycle

Pick metrics before you understand the problem and you'll optimize the wrong thing with great precision.

Metrics should follow outcomes, not lead them.

Our Discovery-Option-Action (DOA) Cycle starts with a hunch about what matters, then validates it through discovery: data analysis, interviews, surveys, or direct observation.

At the decision gate, either the hunch holds and you move to target an outcome, identify metrics, act, and measure; or it doesn’t, and you frame an experiment to learn more before looping back. The cycle keeps teams from locking onto vanity metrics before they understand the problem. Compare two teams: one mandated to track velocity immediately starts optimizing story points; another that runs the DOA Cycle first discovers their actual bottleneck is deployment wait time and picks a metric that reflects it.

Most failed metrics programs confuse three things: productivity (how much a team produces), performance (how skillfully they execute), and outcomes (results someone wants to achieve or influence). Teams that pick metrics first optimize output without ever asking whether outcomes change.

The DOA Cycle breaks this pattern by making outcome identification the precondition for metric selection. It also shifts ownership: teams empowered to choose their own metrics outperform teams handed dashboards from above. Transparency matters more than comparison; the moment a metric becomes a tool for ranking teams, Goodhart’s Law kicks in and the number stops meaning anything, at best, or becomes or creates undesired second order effects, at worst.

This is the core argument behind the Output-Activity Trap: measuring activity feels productive but teaches you nothing about whether you’re moving toward the right result.

Resources

• Using Metrics Responsibly — the full playbook for implementing outcome-first measurement
• Leading and Lagging Indicators — choosing metrics that predict vs. confirm progress
• Impact-Outcome Model — the broader framework for connecting work to outcomes
• By What Method — Deming’s challenge to outcome claims without process understanding
• Goodhart’s Law — why metric mandates backfire
• DORA Metrics — a well-known metric set anchored on software delivery performance and capability