Purpose
Standardized 6-stage field manual for AI Ops custom solution builds, approved 2026-09-09. Defines the engagement model and explicit responsibility boundaries: the business unit owns the problem/value case/KPIs, while AI Ops owns solution delivery.
The 6-Stage Model
- Intake / Triage: 15-question process. Hard rejects for missing BPO (Business Process Owner), KPI owner, or baseline metric.
- Scoping: Definition of build commitment, with firm dates for demos, UAT, and launch.
- Build: Execution phase featuring weekly BPO demo checkpoints and peer developer reviews.
- UAT: Explicit distinction between defects (fixed in-sprint) and change requests (deferred to future iterations).
- Deploy / Handoff: Required delivery of a formal runbook.
- Operate: L+30 and L+90 performance reviews, plus a quarterly portfolio review (renew / refactor / retire).
Standing Rules
- Mandatory Expiration: Every application must have a set expiration date.
- Telemetry: Required implementation of monitoring/telemetry on every custom build.
- UI/UX: Design constraints must be captured at intake for customer-facing builds (contribution: Preet Patel).
Governance
- Trial Period: September–December 2026.
- Responsibility: Business units own the problem and outcome; AI Ops provides delivery.