# KimberLyte — A delivery measure under review Source: https://kimberlytegroup.com/inside-the-work/ Authored fictional example. Not a client result, certification, or finding about your organization. ## Situation An operating review is approaching. Customer service and operations disagree about delivery performance. Before anyone replaces a dashboard, we’d want to know whether the disagreement belongs in the data, the definition, or the decision. ## Scope An authored example with 12 fictional commitments, each originally due from 2–22 October 2026. One commitment per row; equal weight; no cancellations, partial deliveries, time zones, or contract-specific exceptions. This is a bounded reconciliation, not an estimate of enterprise performance. ## Evidence snapshot: After receipt · 24 Oct 2026 Evidence cutoff: 2026-10-24, inclusive, date-only synthetic records. Original promise: 9/12 confirmed on time (75%). Accepted commitment: 11/12 confirmed on time (91.7%). Definition bridge: 2 commitments; same cohort, different approved promise dates. Unconfirmed: 0. These remain in the denominator and are not classified as late. Confirmed late against both definitions: 1. K-09’s receipt confirms delivery on 20 Oct. The evidence arrived on 23 Oct. The delivery itself hasn’t changed. ## Measure contract Denominator: all 12 commitments originally due 2–22 October 2026; rescheduling never moves a row out of this cohort. Numerator: a delivery receipt available by the selected cutoff, with delivery on or before the original / accepted promise date respectively. Original promise and amendment approval date are retained. A changed date is not a changed delivery. ## Recommendation Keep both measures, name them for the decisions they support, and publish the reconciliation beside them. Preserve the original promise and the evidence available at each review. A revised date should never silently replace either. ## The reasonable objection A single headline is easier to govern and explain. That’s a reasonable objection. Here, however, collapsing the measures would either hide the changed customer promise or penalize an operating team for missing a date the customer had already revised. We’d carry the extra measure until the sponsor explicitly resolves that tradeoff. ## People and incentives ### Customer service “We’re still explaining why the original date moved.” Keep original-promise reliability visible. Acceptance of a new date doesn’t prove the disruption was costless. Evidence request: Review the reschedule history and customer explanation for K-04 and K-08. ### Operations “We delivered against the date we were told to work to.” Retain accepted-commitment performance, with dated approval evidence. Don’t treat a legitimate reschedule as a data-quality defect. Evidence request: Confirm who could approve each amendment and when that authority applied. ### The accountable sponsor “Which number will people be judged on?” Don’t let a reporting release decide an incentive policy by accident. Keep compensation and contractual use outside this release until their owners agree. Evidence request: Record the intended use, effective date, and the person authorized to resolve exceptions. ## AI use Permitted in this example: prepare an internal explanation from the selected evidence snapshot, retaining measure names, cohort, cutoff, record references, and uncertainty for human review. Unsupported: infer that service improved from a difference between definitions; infer customer satisfaction from an accepted reschedule; infer performance of the wider business from this sample. Requires a separate human decision: publish externally, change a promise date, change an incentive rule, or overwrite a prior report. No AI service is called by this page. ## Release responsibilities ### Define — Service owner + operations owner Sign off both definitions, the cohort, and the amendment rule. Resolve which measure supports each decision. Evidence to retain: Versioned measure contract and decision-use register. ### Reconcile — Data owner Run both measures on the same bounded cohort. Preserve event dates separately from the dates evidence became available. Evidence to retain: Row-level bridge, receipt history, and unresolved exceptions. ### Rehearse — Delivery lead + operating backup Test a late receipt, a withdrawn amendment, and an absent approver. Check that the backup can act within documented authority. Evidence to retain: Observed results, defects, and the escalation route used. ### Release — Accountable sponsor Approve the intended uses and explain the change to the people evaluated by it. Retain the previous version for comparison and recovery. Evidence to retain: Release decision, effective date, and rollback instructions. ## What would change the recommendation If the governing agreement defines delivery differently, if reschedule approvals cannot be evidenced, or if partial deliveries matter, this example’s rules aren’t sufficient. Rebuild the definition and rerun the reconciliation before using it. ## Source records at this cutoff ID | Original promise | Accepted date | Approval | Delivery known at cutoff | Receipt known at cutoff K-01 | 2026-10-02 | 2026-10-02 | Unchanged | 2026-10-02 | 2026-10-02 K-02 | 2026-10-04 | 2026-10-04 | Unchanged | 2026-10-03 | 2026-10-03 K-03 | 2026-10-06 | 2026-10-06 | Unchanged | 2026-10-06 | 2026-10-06 K-04 | 2026-10-08 | 2026-10-10 | 2026-10-07 | 2026-10-09 | 2026-10-09 K-05 | 2026-10-10 | 2026-10-10 | Unchanged | 2026-10-10 | 2026-10-10 K-06 | 2026-10-12 | 2026-10-12 | Unchanged | 2026-10-11 | 2026-10-11 K-07 | 2026-10-14 | 2026-10-14 | Unchanged | 2026-10-14 | 2026-10-14 K-08 | 2026-10-16 | 2026-10-19 | 2026-10-15 | 2026-10-18 | 2026-10-18 K-09 | 2026-10-20 | 2026-10-20 | Unchanged | 2026-10-20 | 2026-10-23 K-10 | 2026-10-21 | 2026-10-21 | Unchanged | 2026-10-21 | 2026-10-21 K-11 | 2026-10-19 | 2026-10-19 | Unchanged | 2026-10-21 | 2026-10-21 K-12 | 2026-10-22 | 2026-10-22 | Unchanged | 2026-10-22 | 2026-10-22 Open for internal use and adaptation. Replace the fictional scope and assumptions with approved evidence before applying this format to a live decision. --- # Earlier evidence snapshot # KimberLyte — A delivery measure under review Source: https://kimberlytegroup.com/inside-the-work/ Authored fictional example. Not a client result, certification, or finding about your organization. ## Situation An operating review is approaching. Customer service and operations disagree about delivery performance. Before anyone replaces a dashboard, we’d want to know whether the disagreement belongs in the data, the definition, or the decision. ## Scope An authored example with 12 fictional commitments, each originally due from 2–22 October 2026. One commitment per row; equal weight; no cancellations, partial deliveries, time zones, or contract-specific exceptions. This is a bounded reconciliation, not an estimate of enterprise performance. ## Evidence snapshot: At review · 22 Oct 2026 Evidence cutoff: 2026-10-22, inclusive, date-only synthetic records. Original promise: 8/12 confirmed on time (66.7%). Accepted commitment: 10/12 confirmed on time (83.3%). Definition bridge: 2 commitments; same cohort, different approved promise dates. Unconfirmed: 1. These remain in the denominator and are not classified as late. Confirmed late against both definitions: 1. The receipt for K-09 hasn’t arrived. Its commitment stays in the denominator; its outcome remains unconfirmed. ## Measure contract Denominator: all 12 commitments originally due 2–22 October 2026; rescheduling never moves a row out of this cohort. Numerator: a delivery receipt available by the selected cutoff, with delivery on or before the original / accepted promise date respectively. Original promise and amendment approval date are retained. A changed date is not a changed delivery. ## Recommendation Keep both measures, name them for the decisions they support, and publish the reconciliation beside them. Preserve the original promise and the evidence available at each review. A revised date should never silently replace either. ## The reasonable objection A single headline is easier to govern and explain. That’s a reasonable objection. Here, however, collapsing the measures would either hide the changed customer promise or penalize an operating team for missing a date the customer had already revised. We’d carry the extra measure until the sponsor explicitly resolves that tradeoff. ## People and incentives ### Customer service “We’re still explaining why the original date moved.” Keep original-promise reliability visible. Acceptance of a new date doesn’t prove the disruption was costless. Evidence request: Review the reschedule history and customer explanation for K-04 and K-08. ### Operations “We delivered against the date we were told to work to.” Retain accepted-commitment performance, with dated approval evidence. Don’t treat a legitimate reschedule as a data-quality defect. Evidence request: Confirm who could approve each amendment and when that authority applied. ### The accountable sponsor “Which number will people be judged on?” Don’t let a reporting release decide an incentive policy by accident. Keep compensation and contractual use outside this release until their owners agree. Evidence request: Record the intended use, effective date, and the person authorized to resolve exceptions. ## AI use Permitted in this example: prepare an internal explanation from the selected evidence snapshot, retaining measure names, cohort, cutoff, record references, and uncertainty for human review. Unsupported: infer that service improved from a difference between definitions; infer customer satisfaction from an accepted reschedule; infer performance of the wider business from this sample. Requires a separate human decision: publish externally, change a promise date, change an incentive rule, or overwrite a prior report. No AI service is called by this page. ## Release responsibilities ### Define — Service owner + operations owner Sign off both definitions, the cohort, and the amendment rule. Resolve which measure supports each decision. Evidence to retain: Versioned measure contract and decision-use register. ### Reconcile — Data owner Run both measures on the same bounded cohort. Preserve event dates separately from the dates evidence became available. Evidence to retain: Row-level bridge, receipt history, and unresolved exceptions. ### Rehearse — Delivery lead + operating backup Test a late receipt, a withdrawn amendment, and an absent approver. Check that the backup can act within documented authority. Evidence to retain: Observed results, defects, and the escalation route used. ### Release — Accountable sponsor Approve the intended uses and explain the change to the people evaluated by it. Retain the previous version for comparison and recovery. Evidence to retain: Release decision, effective date, and rollback instructions. ## What would change the recommendation If the governing agreement defines delivery differently, if reschedule approvals cannot be evidenced, or if partial deliveries matter, this example’s rules aren’t sufficient. Rebuild the definition and rerun the reconciliation before using it. ## Source records at this cutoff ID | Original promise | Accepted date | Approval | Delivery known at cutoff | Receipt known at cutoff K-01 | 2026-10-02 | 2026-10-02 | Unchanged | 2026-10-02 | 2026-10-02 K-02 | 2026-10-04 | 2026-10-04 | Unchanged | 2026-10-03 | 2026-10-03 K-03 | 2026-10-06 | 2026-10-06 | Unchanged | 2026-10-06 | 2026-10-06 K-04 | 2026-10-08 | 2026-10-10 | 2026-10-07 | 2026-10-09 | 2026-10-09 K-05 | 2026-10-10 | 2026-10-10 | Unchanged | 2026-10-10 | 2026-10-10 K-06 | 2026-10-12 | 2026-10-12 | Unchanged | 2026-10-11 | 2026-10-11 K-07 | 2026-10-14 | 2026-10-14 | Unchanged | 2026-10-14 | 2026-10-14 K-08 | 2026-10-16 | 2026-10-19 | 2026-10-15 | 2026-10-18 | 2026-10-18 K-09 | 2026-10-20 | 2026-10-20 | Unchanged | Unconfirmed | Not available K-10 | 2026-10-21 | 2026-10-21 | Unchanged | 2026-10-21 | 2026-10-21 K-11 | 2026-10-19 | 2026-10-19 | Unchanged | 2026-10-21 | 2026-10-21 K-12 | 2026-10-22 | 2026-10-22 | Unchanged | 2026-10-22 | 2026-10-22 Open for internal use and adaptation. Replace the fictional scope and assumptions with approved evidence before applying this format to a live decision.