Context
A system must scale across people or teams without making every output identical or forcing expert work into a rigid script.
Problem
Organizations often standardize the visible work because it is easy to inspect, while leaving handoffs, authority, and evidence informal. The result is uniform output with brittle operations and reduced ownership.
Forces
- Consistency lowers coordination cost.
- Contextual judgment produces differentiated value.
- Controls must remain testable.
- Over-specification discourages learning and responsibility.
Pattern
Standardize contracts: inputs, outputs, boundaries, approval points, service expectations, and evidence. Inside those contracts, preserve bounded judgment and make outcomes observable. Tighten the interface when coordination fails; tighten the method only when evidence shows the method itself is unsafe or ineffective.
Apply it
Separate non-negotiable controls from preferred techniques and from individual style. Define a minimum viable contract for each handoff. Review exceptions as information about the interface rather than immediate proof of noncompliance.
Failure modes
- A “standard” encodes one expert’s personal workflow.
- Creative freedom is used to avoid evidence or boundaries.
- Every exception creates a new mandatory rule.
- Teams optimize their local step while the end-to-end outcome degrades.
Evidence needed
Comparisons of rework, handoff failures, cycle time, outcome quality, and practitioner autonomy across different levels of standardization.