5 min readDeliveryConcepts

Work Units: how to measure delivery in terms stakeholders understand

There is a persistent translation problem in software delivery. Engineering tools are organized around artifacts (repositories, branches, issues, sprints) but the people who fund and depend on the work think in outcomes: the payment system, the mobile release, the onboarding redesign. A board full of tickets is the right view for the team and the wrong view for everyone else.

What a Work Unit is

A Work Unit is a named outcome that you map a set of GitHub pull requests, issues, and Jira stories onto. Once activity is grouped this way, all of it rolls up into a single, legible unit of progress that a stakeholder recognizes. Instead of forty tickets, there is one "Payment System" with a clear state.

Why it changes what you can measure

Measuring at the artifact level tells you a team is busy. Measuring at the Work Unit level tells you whether an outcome is on track. From a Work Unit, LiveIndex derives the metrics that actually answer stakeholder questions:

  • Progress toward the outcome, not just ticket counts
  • Current blockers, with links to the responsible PR or ticket
  • Cycle time, how fast the outcome is actually moving
  • A forecast completion date from your team’s real pace

How to define good Work Units

The single highest-leverage thing a team does in LiveIndex is define Work Units well. The closer a Work Unit maps to how a client or executive describes the project, the more useful every downstream report and forecast becomes. A few principles help:

  • Name it the way a stakeholder would, "Checkout redesign", not "EPIC-1423"
  • Scope it to an outcome someone would ask about by name
  • Keep it stable; a Work Unit should outlive any single sprint
  • Let one Work Unit span repos and Jira projects if the outcome does

Get the Work Units right and everything downstream (the live status, the client report, the forecast) inherits that clarity. Get them wrong and you are back to measuring activity. It is worth the half hour it takes to define them deliberately.

Stop writing status reports

LiveIndex derives delivery reports from your real GitHub and Jira activity. Set up in under five minutes.