A,C,D reductions
- Observed condition
- Two,three and one minutes
- Next-cycle check
- Keep each matched case
Process pilots / Delivery leads, planning owners and acceptance reviewers
Retrospective deskCompare matched work cases in a process pilot
Retain paired changes and exceptions rather than comparing unmatched averages.
The guide preserves matched differences and exceptions rather than comparing unrelated aggregate groups.
Opens the current invite-request page. Access is subject to approval; this example is not imported automatically.
Original worked case · Manual planning resource
Inspect the decision, not just the summary.
Start with the invented evidence, follow the reasoning, and retain its limits when adapting the brief.
02 · Follow the reasoning
How the case leads to a decision
Total paired reduction=2+0+3+1=6 minutes over four tasks; mean reduction=1.5. Before mean 13 and after 11.5 preserve the same matched cases.
The bounded result
The paired reductions are two, zero, three and one minutes, averaging 1.5. Keep the unchanged B case and the practice limitation rather than claiming every task improved because of the change.
01 · Inspect the inputs
Every record stays visible
| Matched task | Before minutes | After minutes | Before minus after |
|---|---|---|---|
| A | 10 | 8 | 2 |
| B | 12 | 12 | 0 |
| C | 14 | 11 | 3 |
| D | 16 | 15 | 1 |
Use horizontal scrolling for wide tables. These records are invented, not customer data.
Definitions and method context
Records, decisions and policies are original synthetic examples. External references supply context; they do not validate these cases or TeamBoostAI capabilities.
NIST combinatorial testing ↗
Combination-coverage context. Invented review/state examples do not prove full fault coverage, certification or product behavior.
External references checked 6 October 2026. Demand for these topics has not been measured.
Turn a retrospective into a follow-up
Illustrative retrospective deskSynthetic planning case: Four matched rehearsal tasks are timed before and after a process change. Times in minutes are A10→8,B12→12,C14→11,D16→15; repeated practice may also affect the result.
B unchanged
- Observed condition
- Twelve minutes both times
- Next-cycle check
- Do not claim universal improvement
Practice unresolved
- Observed condition
- Repeated rehearsal may affect timing
- Next-cycle check
- Review sequence and context in the next pilot
Decision to make: The paired reductions are two, zero, three and one minutes, averaging 1.5. Keep the unchanged B case and the practice limitation rather than claiming every task improved because of the change.
Verify paired identity
Owner role · Pilot recorder
Evidence: Each before/after row concerns the same defined rehearsal task.
Retain case-level differences
Owner role · Reviewer
Evidence: The zero-change B row remains visible beside the other reductions.
Investigate alternative explanations
Owner role · Process lead
Evidence: Practice, order and changing conditions are considered before attributing the result.
Filled manual planning note
Invented planning text. Adapt it to your evidence and confirmed owners.
The paired reductions are two, zero, three and one minutes, averaging 1.5. Keep the unchanged B case and the practice limitation rather than claiming every task improved because of the change. Total paired reduction=2+0+3+1=6 minutes over four tasks; mean reduction=1.5. Before mean 13 and after 11.5 preserve the same matched cases. A four-case paired illustration is not a causal or statistically calibrated process evaluation.
Put the outline to work
- Verify paired identity. Check: Each before/after row concerns the same defined rehearsal task.
- Retain case-level differences. Check: The zero-change B row remains visible beside the other reductions.
- Investigate alternative explanations. Check: Practice, order and changing conditions are considered before attributing the result.
Questions about this workflow
May I compare unmatched before/after averages instead?
That answers a different question and can mix different task composition. Preserve pairing when it is the intended design.
Does a positive mean prove the process caused improvement?
No. These invented repeated rehearsals leave practice and other explanations unresolved.
Does this create tasks in the product?
No. The brief is a manual planning resource. Use the product access link to check onboarding and the workflows available in your account.
From a useful outline to team work
Explore TeamBoostAI for your team
Use the owned checks and downloaded brief to discuss this planning decision alongside your TeamBoostAI tasks. Confirm available fields, roles and account features separately. The example is manual; it does not calculate live analytics, create work or run an experiment in the product. Confirm the workflows available in your account before adopting this outline.
Request TeamBoostAI access
Opens the current invite-request page. Access is subject to approval; this example is not imported automatically.