Skip to main content

Phase 6 Playbook — Operate & Evolve

Duration: Ongoing | Agents: 12+ (rotating) | Governance: Studio Producer

Objective

Sustained operations with continuous improvement. The product is live — now make it thrive. This phase has no end date; it runs as long as the product is in market.

Pre-Conditions

1

Stable Launch

Phase 5 Quality Gate passed (stable launch confirmed)
2

Handoff Complete

Phase 5 Handoff Package received
3

Cadences Established

Operational cadences established
4

Metrics Baselined

Baseline metrics documented

Operational Cadences

Continuous (Always Active)

AgentResponsibilitySLA
Infrastructure MaintainerSystem uptime, performance, security99.9% uptime, < 30min MTTR
Support ResponderCustomer support, issue resolution< 4hr first response
DevOps AutomatorDeployment pipeline, hotfixesMultiple deploys/day capability

Daily

AgentActivityOutput
Analytics ReporterKPI dashboard updateDaily metrics snapshot
Support ResponderIssue triage and resolutionSupport ticket summary
Infrastructure MaintainerSystem health checkHealth status report

Weekly

Analytics Reporter

Weekly performance analysisOutput: Weekly Analytics Report

Feedback Synthesizer

User feedback synthesisOutput: Weekly Feedback Summary

Sprint Prioritizer

Backlog grooming + sprint planningOutput: Sprint Plan

Growth Hacker

Growth channel optimizationOutput: Growth Metrics Report

Project Shepherd

Cross-team coordinationOutput: Weekly Status Update

Monthly

  • Executive Summary Generator → Monthly Executive Summary
  • Finance Tracker → Monthly Financial Report (MRR/ARR, costs, unit economics, forecasts)

Quarterly

Studio Producer

Strategic portfolio reviewOutput: Quarterly Strategic Review

Workflow Optimizer

Process efficiency auditOutput: Optimization Report

Performance Benchmarker

Performance regression testingOutput: Quarterly Performance Report

Tool Evaluator

Technology stack reviewOutput: Tech Debt Assessment

Continuous Improvement Loop

Feature Development in Phase 6

New features follow a compressed cycle:
  1. Sprint Prioritizer selects feature from backlog
  2. Appropriate Developer Agent implements
  3. Evidence Collector validates (Dev↔QA loop)
  4. DevOps Automator deploys (feature flag or direct)
  5. Experiment Tracker monitors (A/B test if applicable)
  6. Analytics Reporter measures impact
  7. Feedback Synthesizer collects user response

Incident Response Protocol

Severity Levels

LevelDefinitionResponse TimeDecision Authority
P0 — CriticalService down, data loss, security breachImmediateStudio Producer
P1 — HighMajor feature broken, significant degradation< 1 hourProject Shepherd
P2 — MediumMinor feature issue, workaround available< 4 hoursAgents Orchestrator
P3 — LowCosmetic issue, minor inconvenienceNext sprintSprint Prioritizer
DETECTION (Infrastructure Maintainer or Support Responder) ↓ TRIAGE (Agents Orchestrator)
  • Classify severity (P0-P3)
  • Assign response team
  • Notify stakeholders ↓ RESPONSE
  • P0: Infrastructure Maintainer + DevOps + Backend Architect
  • P1: Relevant Developer + DevOps
  • P2: Relevant Developer
  • P3: Added to sprint backlog ↓ RESOLUTION
  • Fix implemented and deployed
  • Evidence Collector verifies fix
  • Infrastructure Maintainer confirms stability ↓ POST-MORTEM (Workflow Optimizer leads)
  • Root cause analysis documented
  • Prevention measures identified
  • Process improvements implemented

Growth Operations

Monthly Growth Review (Growth Hacker leads)

1

Channel Performance

  • Acquisition by channel
  • CAC by channel
  • Conversion rates by funnel stage
  • LTV:CAC ratio trends
2

Experiment Results

  • Completed A/B tests and outcomes
  • Statistical significance validation
  • Winner implementation status
  • New experiment pipeline
3

Retention Analysis

  • Cohort retention curves
  • Churn risk identification
  • Re-engagement campaign results
  • Feature adoption metrics
4

Growth Roadmap

  • Next month’s growth experiments
  • Channel budget reallocation
  • New channel exploration
  • Viral coefficient optimization

Strategic Evolution

Quarterly Strategic Review (Studio Producer)

1. Market Position Assessment
  • Competitive landscape changes (Trend Researcher)
  • Market share evolution
  • Brand perception (Brand Guardian)
  • Customer satisfaction (Feedback Synthesizer)
2. Product Strategy
  • Feature roadmap review
  • Technology debt (Tool Evaluator)
  • Platform expansion opportunities
  • Partnership evaluation
3. Growth Strategy
  • Channel effectiveness review
  • New market opportunities
  • Pricing strategy assessment
  • Expansion planning
4. Organizational Health
  • Process efficiency (Workflow Optimizer)
  • Team performance metrics
  • Resource allocation optimization
  • Capability development needs
Output: Quarterly Strategic Review → Updated roadmap and priorities

Phase 6 Success Metrics

MetricTargetOwner
System uptime> 99.9%Infrastructure Maintainer
MTTR< 30 minutesInfrastructure Maintainer

Phase 6 has no end date. It runs as long as the product is in market, with continuous improvement cycles driving the product forward. The NEXUS pipeline can be re-activated (NEXUS-Sprint or NEXUS-Micro) for major new features or pivots.

Build docs developers (and LLMs) love