Reconcile the work present with the work completed

Choose a trace that can be reconciled

MIT links average occupancy, throughput and elapsed time.

Identify one workflow and the event that admits a job to it. Name the event that removes the job, then keep those boundaries unchanged throughout the exercise. For an editorial operation, an internal draft might enter a defined review process only after its inputs are accepted. A publication timestamp from another process would not automatically be the matching exit.

Use a synthetic complete trace for learning before attempting to interpret a production export. Do not collect personal performance information merely to fill the example. Ask the process owner what an event means and whether cancellations, returns for revision or duplicate identifiers require separate treatment. The objective is to reconcile a defined flow, not to rank individual workers.

Count the same work two ways

Fictional jobs occupy days 0–2, 1–4 and 4–7 within an otherwise empty 0–8 window. Durations sum to 2 + 3 + 3 = 8 job-days. Occupancy areas are 1, 2, 2, 3 and 0 across intervals 0–1, 1–2, 2–4, 4–7 and 7–8: again 8.

Dividing area 8 by 8 days gives mean occupancy 1. Three completions divided by 8 days gives throughput 3/8 jobs per day; mean duration is 8/3 days. Multiplying 3/8 by 8/3 recovers 1. The final snapshot is zero, and stipulated touch time 0.5 days per job is not total elapsed time.

Walk a reviewer through the interval lengths and the jobs present in each one. At day 4, the departure and arrival occur at the same boundary; the calculation does not invent an extra day for either event. Preserve the original trace beside the result so the reviewer can inspect the accounting rather than trusting a chart label.

Investigate mismatches without forcing agreement

For an actual report, first check that the input records describe the same process and observation basis. A mismatch can arise because one source counts versions while another counts deliverables, or because an export omits a status transition. List the unresolved interpretation and the evidence needed from the system owner. Do not edit a timestamp to make the arithmetic balance.

The window has no carry-in or unfinished jobs. Do not reuse this finite calculation unchanged for incomplete windows. Preserve those cases for a qualified analyst’s appropriate treatment. A convenient weekly reporting schedule does not establish that the supplied records satisfy this example’s conditions.

If a record is missing, distinguish that absence from a verified event that did not occur. Keep the original export and any corrected interpretation separate. The team needs to know whether it has found a data defect, a definition mismatch or an operational pattern worth investigating. A single balancing adjustment would conceal that distinction.

Use the reconciliation for a bounded inquiry

Once the accounting is coherent, choose the operational question it can help investigate. Perhaps the team needs to examine a recurring approval gap or a handoff whose event is recorded inconsistently. State the question and the additional evidence needed. The reconciliation itself does not establish the cause of a delay or identify a person responsible for it.

Keep any proposed process change separate from the historical result. A different intake rule, staffing arrangement or service promise needs its own feasibility and authority review. Do not convert a descriptive relationship into a guarantee that changing one number will automatically produce a desired customer outcome.

Retain the boundary definition, trace, calculation and unresolved limitations together. When the workflow changes, revisit the definition before comparing periods. A release that changes what counts as admission or completion can alter the report without changing the customer experience. The useful deliverable is an inspectable explanation of this evidence, followed by a focused next question rather than an unsupported productivity claim.

Make the reasoning concrete.

A fictional content team reports an empty review board at the end of the observation. A manager interprets that screen as evidence that the team had little work, despite the complete trace above.

The team corrects its interpretation and requests a focused process review. It makes no staffing change or customer waiting promise.

Take the questions into your next brief.

Use these prompts in your own notes. Nothing is submitted from this page.

1. Boundary

   Which events admit and remove a job?

2. Identity

   Does each record represent the same kind of work?

3. Trace

   Can the complete synthetic history be reconstructed?

4. Mismatch

   What unresolved definition or missing event affects the report?

5. Inquiry

   What additional evidence would support the next operational question?

Watch for the wrong conclusion.

• Using a final screen as a substitute for the full history.
• Changing timestamps to produce agreement.
• Turning a historical reconciliation into a promised improvement.

Sources & scope

Original explicitly fictional traces and activity networks. Method definitions and calculation applications remain source-derived. No future guarantee, personnel assessment, scheduling change or purchase is made. Qualified owners review operational feasibility.

• MIT: Queueing Systems, Lecture 1 →Primary teaching material · Supports: Supports the flow relationship and boundaries.