Files
documentation/docs/strategy/measurement/workflow-specific-business-acceptance.mdx
T
jarvis-at-skic 85852f0744
Build and publish Eldorado documentation / build (pull_request) Successful in 41s
docs: [verified] move metric contracts under Measurement
2026-10-06 23:25:30 +00:00

37 lines
2.3 KiB
Plaintext

---
id: workflow-specific-business-acceptance
slug: /measurement/workflow-specific-business-acceptance
title: Workflow-specific business acceptance
description: Definition, collection evidence and limitations for workflow-specific business acceptance.
---
<div className="strategy-content">
**Target operating model — recommended contracts, not installed collection.** All owner and cadence entries below are proposals to confirm before the pilot, not assigned responsibilities or approved schedules.
**Unimplemented metric — no live telemetry.** This is a prospective contract, not an implemented calculation or collector.
{/* contract:start */}
Independently accepted domain outcomes against a predeclared business rubric, separate from technical completion.
| Contract | Definition |
| --- | --- |
| Numerator | Eligible completed-observation task_ids meeting the department-specific outcome rubric |
| Denominator | All eligible initiated workflow task_ids with matured business-outcome horizon |
| Expression | N / D * 100 |
| Aggregation | percent |
| Unit | % |
| Eligible population | One named departmental workflow and predeclared start cohort; never pool unlike rubrics. |
| Exclusions | Cancelled-before-start and unrelated workflows; unsuccessful or abandoned eligible work remains. |
| Events and source | task.started; business.accepted; departmental case/content/reconciliation/onboarding review record |
| Owner / cadence | Product Management / Each pilot cycle with owning department |
| Missing evidence | Unknown follow-up stays denominator with unresolved count; no claim actual business outcome changed without source evidence. |
| Gaming and limits | Weaken rubric or count drafts as customer benefit; lock rubric and independently audit acceptance. Descriptive signal, not causal AI productivity attribution. Source completeness, task mix and sampling limit inference; report uncertainty. Domain owner signs acceptance: Operations service accuracy; Marketing claims/rights; Finance reconciliation accuracy; HR policy correctness; Product usability/value. Not revenue uplift. |
{/* contract:end */}
Read the shared [collection and safeguards](./collection-and-safeguards.mdx) before collecting data; see the [synthetic example and limits](./synthetic-example.mdx).
Return to [Skills Measurement](./index.mdx).
</div>