Work Unit

A Work Unit is the central organizing concept in LiveIndex. Engineering tools are organized around artifacts (repositories, branches, issues, sprints) but stakeholders think in terms of outcomes. A Work Unit bridges that gap. It is a named outcome that you map a set of GitHub pull requests, issues, and Jira stories onto, so that all the underlying activity rolls up into a single, legible unit of progress.

Once activity is grouped into a Work Unit, LiveIndex derives its state automatically: percent complete, current blockers, cycle time, velocity, and a forecast completion date. None of this requires anyone to update a status field. As PRs merge and tickets transition, the Work Unit’s status moves with them in real time.

Work Units are also the unit of sharing. When you publish a client report, you choose which Work Units appear, and LiveIndex renders an executive-level summary of each one (what was delivered, what is in flight, and what is at risk) without exposing raw commits, internal tickets, or engineering diagnostics.

Defining good Work Units is the highest-leverage thing a team does in LiveIndex. The closer a Work Unit maps to how a client or executive describes the project, the more useful every downstream report and forecast becomes.