{"id":"pattern.standardize-interfaces-not-judgment","slug":"standardize-interfaces-not-judgment","type":"pattern","version":"0.1.0","maturity":"hypothesis","status":"published","title":"Standardize interfaces and controls, not creative judgment","summary":"Make handoffs, boundaries, and evidence predictable while preserving judgment where context and craft create value.","audiences":["leader","designer","operator"],"relationships":{"supports":["pattern.boundaries-increase-agency","pattern.reduce-heroics"],"contradicts":[],"depends_on":[]},"disclosure":"green","approved_by":["chrisleeddotcom"],"license":"CC-BY-4.0","created":"2026-08-21","updated":"2026-08-21","canonical_url":"https://intentarium.com/patterns/standardize-interfaces-not-judgment/","source":{"repository":"https://github.com/Intentarium/canon","commit":"a8b303818e72c20505bd9ef56f5fb2d0448aa6f3","path":"patterns/standardize-interfaces-not-judgment.md"},"body_markdown":"## Context\n\nA system must scale across people or teams without making every output identical or forcing expert work into a rigid script.\n\n## Problem\n\nOrganizations 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.\n\n## Forces\n\n- Consistency lowers coordination cost.\n- Contextual judgment produces differentiated value.\n- Controls must remain testable.\n- Over-specification discourages learning and responsibility.\n\n## Pattern\n\nStandardize 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.\n\n## Apply it\n\nSeparate 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.\n\n## Failure modes\n\n- A “standard” encodes one expert's personal workflow.\n- Creative freedom is used to avoid evidence or boundaries.\n- Every exception creates a new mandatory rule.\n- Teams optimize their local step while the end-to-end outcome degrades.\n\n## Evidence needed\n\nComparisons of rework, handoff failures, cycle time, outcome quality, and practitioner autonomy across different levels of standardization."}