AIWorkDex
Operations Practice

Review active commitments by exception

Keep the operating review focused on dated evidence, specific exceptions, and decisions that need an owner.

Preparation
One setup review, then a recurring session sized to the active commitment set.
Difficulty
Moderate
Task
Run an operating review
Back to the Task: Run an operating review

Before you start

Get what you need before you start

  • List only active commitments and their authorised owners.
  • Record each agreed measure, source system, state definition, and next review date.
  • Ask domain owners to validate the evidence from their systems.

Steps

Work through the method

Use the listed inputs and tools. Check the evidence when you need to verify a step.

  1. Prepare current commitment records

    For each active commitment, record the owner, intended outcome, agreed measure, dated source evidence, current state, and previous decision.

    Why it matters: A review cannot distinguish drift from progress when the commitment or measure changes between meetings.

    Input
    The active plan, owner list, agreed measures, source systems, and prior review.
    Output
    A current commitment set with dated evidence and stable definitions.
    Tools in this stepAtlassian Goals

    Evidence for this step

  2. Identify specific exceptions

    Compare the current evidence with the agreed measure. State the concrete variance, missing evidence, dependency, or learning without inventing a score.

    Why it matters: A broad red or green status hides the condition that requires a decision.

    Input
    Current commitment records and domain-owner evidence checks.
    Output
    An exception list tied to a dated source and state definition.
    Tools in this stepAtlassian Goals

    Evidence for this step

  3. Make or assign each decision

    For every exception, record the authorised decision, owner, next action, required evidence, and decision due point. Escalate cross-domain conflicts.

    Why it matters: Discussing an exception without assigning its decision leaves the operating state unchanged.

    Input
    The exception list, authority map, dependencies, and available options.
    Output
    A decision record with owners, actions, evidence needs, and due points.
    Tools in this stepAtlassian Goals

  4. Retire stale work and schedule review

    Retire commitments that no longer belong in the plan with the authorised owner’s reason. Set the next evidence date for every active item.

    Why it matters: Keeping obsolete work active makes the review larger and weakens attention on current commitments.

    Input
    The reviewed commitment set and authorised decisions.
    Output
    An updated active set, retirement record, and next review schedule.
    Tools in this stepAtlassian Goals

    Evidence for this step

Success checks

Check the result before you finish

  • Every active commitment uses an agreed measure and dated source.
  • Each off-track state names a specific exception or evidence gap.
  • Every decision has an authorised owner and due point.
  • Obsolete commitments leave the active review through a recorded decision.

Failure modes

Watch for these problems

  • The meeting rebuilds status from memory. Pause and obtain the dated source from the domain owner.
  • A score changes without a stable definition. Restore the agreed measure or record an authorised change.
  • Every commitment receives equal discussion. Move on-track items to consent and focus on exceptions.
  • An item remains active without an owner. Assign one or retire it through the authorised decision path.

Tools

Choose the tools you need

Sources

Read the sources behind this practice

Check what each source supports and where the advice has limits.