Are You Measuring What Matters—or Just What's Easy to Count?

Most government software programs can tell you exactly how many features they shipped. Far fewer can tell you what changed because of it.

The honest answer for most programs is that no one has agreed on what "done" actually looks like—in terms of user behavior, mission capability, or measurable change in the field. Features get shipped. Demos get applauded. And the mission stays roughly where it was.

The fix isn't more process. It's a better question: not "what did we build?" but "what changed because of it?"

In this Mission O/S Live, Rise8 VP of Delivery Max Reele and Josh Seiden—author of Outcomes Over Output and Lean UX—bring that question to the table from two angles. Josh has helped top global organizations stop optimizing for activity and start delivering measurable change. Max has done the same inside some of the most constrained delivery environments in the federal government.

What they'll cover:

• How to shift from output metrics to outcomes your team can actually act on
• Why discovery is an ongoing delivery practice, not a pre-work phase
• What gets in the way of outcome-thinking in government programs, and how to work around it
• How to know if your AI initiatives are contributing to your outcome or just creating activity

If you're leading or delivering on a government software program and you're tired of measuring progress in features shipped rather than mission moved, this conversation is for you.