Per-Unit Service Standard¶
Service standard — instantiates Scale-Invariant Design
Fixes the quality each unit receives — per learner, per case, per ticket — as an explicit standard, so growth cannot silently dilute the service.
Growth erodes quality quietly, one unnoticed compromise at a time, because nobody wrote down what the quality was. Per-Unit Service Standard fixes the experience a single unit — a learner, a patient, a support ticket — is guaranteed to receive, and turns that guarantee into the acceptance criterion every expansion must meet. Its defining move is to pin the output: not how much resource is provisioned, but what each unit actually gets, expressed as a threshold that stays constant however many units there are. It is the counterweight to the temptation to let "we'll get to it" stretch the promise thinner as the population climbs.
Example¶
A tutoring nonprofit that serves 200 students runs beautifully: every essay comes back with feedback inside two days, and every student gets a half-hour one-to-one check-in each week. Scaled to 5,000 students the visible structure survives — there are still tutors, still check-ins — but "feedback soon" has silently become "feedback in two weeks," and nobody decided that; it just happened. The team writes a per-unit service standard: every learner receives graded written feedback within 48 hours and at least 20 minutes of one-to-one mentor contact weekly. A context-adaptation clause allows rural learners on unreliable connections to substitute asynchronous voice notes for the live session, so long as the 20-minute contact and 48-hour feedback still hold. From then on the standard, not the enrollment number, is what they staff, measure, and refuse to breach.
How it works¶
- Name the invariant experience. State the behavior each unit must keep receiving in observable terms — a turnaround time, a contact minimum, a resolution quality — not a vague aspiration.
- Set it as a per-unit threshold. Express the guarantee at the granularity of one unit, so it cannot be satisfied "on average" while individuals fall through.
- Bound the local variation. Attach an adaptation clause naming exactly which substitutions preserve the standard and which would break it.
- Gate growth on it. Make meeting the standard the pass/fail condition for adding units, so expansion stops when the guarantee would be broken.
Tuning parameters¶
- Unit definition — whether the standard applies per individual, per cohort, or per case; finer units protect the vulnerable but are costlier to guarantee.
- Threshold strictness — how demanding the guaranteed level is; tighter raises quality but lowers how many units can be served with fixed resource.
- Adaptation-clause width — how much local substitution is sanctioned; generous clauses fit varied contexts but risk hollowing the standard out.
- Measurement basis — whether compliance is judged on the mean or a worst-case percentile; the percentile is harder to hit but is what actually protects the tail.
When it helps, and when it misleads¶
Its strength is that it makes dilution visible and forbidden: a breach is a defined event, not a slow slide nobody can point to, and it gives leaders an honest reason to slow growth rather than degrade it.
Its failure mode is measuring the standard by the average, where a healthy district-wide mean feedback time can coexist with rural sites whose learners wait a fortnight — the mean is invariant while the experience is not. This is the flaw of averages:[n1] a single summary statistic hides the distribution that actually matters. The guarding discipline is to certify the standard at the worst-served percentile, not the mean, so the guarantee protects the unit most at risk of being sacrificed to scale.
How it implements the components¶
invariant_behavior— the standard is the named behavior each unit must keep receiving; it makes the preserved experience explicit and measurable.context_adaptation_clause— the clause defining which local substitutions are allowed without breaching the guarantee.
It does not size the resources needed to deliver the standard — normalized_ratio and capacity_scaling_rule are the job of Normalized Capacity Ratio, which provisions the inputs this standard specifies the target for.
Related¶
- Instantiates: Scale-Invariant Design — names the output behavior that must stay constant across scale.
- Sibling mechanisms: Normalized Capacity Ratio · Density-Preserving Layout Rule · Modular Design Rule · Recursive Cell Template · Interface Invariance Contract · Breakpoint Trigger Monitoring · Scale-Boundary Exception Rule · Pilot-to-Scale Design Probe
Editorial Notes¶
Form Classification¶
Form family: Rule, Policy & Commitment
Rationale: Per-Unit Service Standard operates as a standing rule, threshold, contractual commitment, or policy constraint governing future conduct because it fixes the quality each unit receives — per learner, per case, per ticket — as an explicit standard, so growth cannot silently dilute the service.
Independent corroboration: The frozen evidence defines Per-Unit Service Standard as 'Fixes the quality each unit receives — per learner, per case, per ticket — as an explicit standard, so growth cannot silently dilute the service', so its operative form is Rule, Policy & Commitment.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Public Administration & Policy
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Universal
Rationale: Explicit service entitlements per case or person are characteristic of public-service standards and policy administration.
Related originating lineages:
- Education & Pedagogy — Per-learner resource and quality commitments supplied an important service-standard lineage.
- Organizational & Management Science — Per-Unit Service Standard is rooted in organizational and management science: Service-management practice turns per-case quality into a protected standard against dilution at scale. Service operations developed workload-normalized service-level targets.
Review resolution: Light authoritative-source research resolves the primary-origin disagreement in favor of public administration and policy. GOV.UK Service Standard directly documents the defining practice or theory described in the selected origin rationale. Other listed domains are retained only where the blind reviews identify material co-development or translation; broader adoption remains separate as domain_reach=universal.
Attribution caveat: The generic per-unit formulation spans public, educational, and organizational service traditions.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Researched adjudication after independent review; high confidence.
Sources consulted:
Notes¶
[n1] The flaw of averages (Sam L. Savage) — plans built on average inputs systematically mislead when the underlying distribution is skewed or has a heavy tail, because the average case is not the case that fails. ↩