Choose the reporting unit
Owner role · Delivery lead
Evidence: The week’s rule names accepted parent outcomes and excludes their children from that count.
Work measurement / Team leads and delivery coordinators
Task boardThroughput counts when work items are split
Define the counted delivery unit before comparing throughput across a task split. Keep parent outcomes and child-task counts separate.
A granularity change can raise a task count without increasing accepted outcomes; retain both views with an explicit unit.
Opens the current invite-request page. Access is subject to approval; this example is not imported automatically.
Turn the situation into owned work
Illustrative task boardSynthetic example: One customer outcome is represented by a parent and three child tasks. All children finish this week and the parent outcome is accepted. A draft counts all four records as deliveries.
Map split lineage
Owner role · Task owner
Evidence: Three child records link to the single outcome with distinct IDs.
Reconcile the week
Owner role · Report reviewer
Evidence: One outcome and three child completions appear in separate columns.
Decision to make: Report one accepted parent outcome or three completed child tasks as separate measures, never four equivalent outcomes.
Worked reporting note
Invented planning text. Adapt it to your evidence and confirmed owners.
Weekly note: one accepted outcome represented by three completed child tasks; no comparable earlier-period trend is inferred.
Put the outline to work
- Define what a counted item represents before the reporting period.
- Record parent/child lineage and the chosen accepted-finish condition.
- Separate granularity changes from changed delivery volume.
A worked measurement study
Inspect the data. Trace the decision.
Every record here is synthetic. Use the rule to review your own evidence before taking action.
Keep evidence and inference separate
Observed
One accepted parent and three completed children
Supports separately labelled counts.
Unknown
Comparison under the prior period’s unit
Resolve the earlier policy before claiming growth.
Next check
Reconcile one split lineage before publishing totals
Hold mixed parent/child counts.
Invented records · inspect every count
| Record | Level | Observed finish | Reporting treatment |
|---|---|---|---|
| Outcome O1 | Parent | Accepted | Count 1 outcome |
| O1-A | Child | Finished | Count in child view |
| O1-B | Child | Finished | Count in child view |
| O1-C | Child | Finished | Count in child view |
On small screens, scroll a wide table sideways to see all columns.
Download example data (.csv) · Download method worksheet (.json)
Read units and denominators with the source table. These are invented example records.
Work through the rule
Parent-outcome count = 1. Child-task count = 3. The sum 4 mixes nested units and double-counts the represented outcome.
Weekly note: one accepted outcome represented by three completed child tasks; no comparable earlier-period trend is inferred.
Questions about this workflow
Can we count child tasks instead?
Yes, with a child-task unit and consistent inclusion policy. Do not compare it directly with parent outcomes.
Why preserve the parent-child mapping?
It lets the reviewer see whether several records represent pieces of the same accepted outcome.
Does this require a specific product rollup feature?
No. The supplied ledger is manual; native rollup availability has not been verified.
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 this manual measurement rule as context when planning or reviewing owned work in TeamBoostAI. Confirm the fields and reports available in your account; the worksheet is not imported automatically. 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.