# Implement a Business System

Status: draft · v0.1.0 · Operating System
draft reference — not a fitted standard

Turn an approved process and system decision into a controlled, adopted, measurable operating capability.

## Purpose
Coordinate process, data, technology, controls, ownership, change, and measurement so a system implementation improves the work rather than merely going live.

## Steps
1. Authorize the implementation — Create one mandate connecting the business outcome, process change, technology scope, authority, and economics.
2. Establish baseline and readiness — Surface the operating, data, technical, control, and adoption conditions the plan must address.
3. Design the transition and delivery plan — Sequence changes according to dependencies and operating risk.
4. Configure, connect, and prepare — Build the approved operating design without losing traceability to requirements.
5. Validate operating readiness — Test the end-to-end mechanism, including failure and recovery—not only software functions.
6. Deploy and support the passage — Move work and users into the new mechanism under controlled conditions.
7. Stabilize and transfer ownership — Make client operation durable and close the implementation without hiding residual risk.

## Connections
- upstream: Redesign Work and Workflow (/processes/redesign-work-and-workflow) — trigger: The approved design requires system configuration, integration, migration, or automation.
- upstream: Select a Business System (/processes/select-business-system) — trigger: A system and implementation path are approved.
- downstream: Operate and Improve a Process (/processes/operate-and-improve-process) — trigger: Stabilization and operational-acceptance criteria are met.

## Measures
- Business outcome movement: Change in the chartered outcome from baseline, reported with assumptions and other influences explicit.
- Acceptance pass rate: Acceptance criteria passed without unresolved material defect divided by all acceptance criteria.
- Decision latency: Elapsed time from decision-ready escalation to authoritative decision, segmented by type and impact.
- Active workflow use: Eligible users and cases completing the required workflow during the period divided by eligible population and demand.
- Production exceptions: Exceptions by severity, source, affected process step, cause, owner, and age per unit of demand.
- Transition guardrails: Context-specific measures compared with baseline throughout cutover and stabilization.