Preserve class counts
Owner role · Evaluation owner
Evidence: The eight/two split is retained with the ten-case cohort.
Forecast evaluation / Delivery leads, planning owners and acceptance reviewers
Drafting workbenchCompare a task classifier with a simple base-rate rule
Check whether high accuracy hides failure to recognize the less frequent required outcome.
The artifact tests an apparently strong accuracy claim against an explicit majority-class reference.
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
Overall accuracy is 8/10=80%. Ready-case detection is 0/2=0%. The high accuracy follows the observed class mix and the constant rule, not evidence that A recognizes a ready case.
The bounded result
Rule A matches eight of ten labels but detects zero of two ready cases. Report the majority-outcome baseline and the required ready-case result before treating overall accuracy as useful.
01 · Inspect the inputs
Every record stays visible
| Observed class | Cases | A predicts | Correct | Ready cases detected |
|---|---|---|---|---|
| Not ready | 8 | Not ready | 8 | Not applicable |
| Ready | 2 | Not ready | 0 | 0 of 2 |
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.
Original worked-case definitions
Definitions, policy choices, records and calculations are authored for this worksheet. No external standard, statistical validation or live product measurement is claimed.
External references checked 6 October 2026. Demand for these topics has not been measured.
Prepare a brief for human review
Drafting workbenchSynthetic planning case: A ten-case evaluation contains eight not-ready outcomes and two ready outcomes. Rule A always predicts not ready and advertises 80% accuracy as evidence that it detects readiness.
Write the constant reference rule
Owner role · Reviewer
Evidence: Always-not-ready is an explicit comparator rather than hidden in an accuracy claim.
Check the decision-relevant class
Owner role · Planning lead
Evidence: The two required ready detections remain visible before selecting the rule.
Decision to make: Rule A matches eight of ten labels but detects zero of two ready cases. Report the majority-outcome baseline and the required ready-case result before treating overall accuracy as useful.
Use the downloaded brief as planning input. AI suggestions remain proposals; review scope, owners and acceptance evidence yourself.
Filled manual planning note
Invented planning text. Adapt it to your evidence and confirmed owners.
Rule A matches eight of ten labels but detects zero of two ready cases. Report the majority-outcome baseline and the required ready-case result before treating overall accuracy as useful. Overall accuracy is 8/10=80%. Ready-case detection is 0/2=0%. The high accuracy follows the observed class mix and the constant rule, not evidence that A recognizes a ready case. This tiny synthetic cohort does not validate a classifier, class distribution or live task readiness model.
Put the outline to work
- Preserve class counts. Check: The eight/two split is retained with the ten-case cohort.
- Write the constant reference rule. Check: Always-not-ready is an explicit comparator rather than hidden in an accuracy claim.
- Check the decision-relevant class. Check: The two required ready detections remain visible before selecting the rule.
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.
Questions about this workflow
Is 80% accuracy necessarily bad?
Its usefulness depends on the actual decision and error consequences; it does not alone demonstrate readiness detection.
Does the eight/two split apply to future tasks?
No. It describes only these invented evaluation cases.
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.