SKILL.md

--- frontmatter

name: pilot-to-production-scaler
description: Use when transitioning AI pilots to enterprise deployment. Use after successful pilot. Produces scaling plan, readiness assessment, and rollout strategy.

Pilot to Production Scaler

Overview

Transition successful AI pilots to enterprise-wide production deployment. Assess readiness, plan scaling, and execute rollout while maintaining quality.

Core principle: What works in pilot doesn't automatically work at scale. Systematic scaling prevents costly failures and builds confidence.

When to Use

•Pilot demonstrates success
•Stakeholders want broader rollout
•Capacity for scaling exists
•Compliance for production approved

Output Format

yaml

scaling_plan:
  initiative: "[Initiative name]"
  pilot_summary:
    start_date: "[YYYY-MM-DD]"
    end_date: "[YYYY-MM-DD]"
    scope: "[Pilot scope]"
    users: "[N users/transactions]"
    results: "[Key outcomes]"
    success_criteria_met: [true | false]
  
  readiness_assessment:
    overall: "[Ready | Ready with conditions | Not ready]"
    
    dimensions:
      - dimension: "Technical"
        status: "[Green | Amber | Red]"
        items:
          - item: "[Assessment item]"
            status: "[Pass | Needs work | Fail]"
            notes: "[Details]"
      
      - dimension: "Operational"
        status: "[Green | Amber | Red]"
        items: []
      
      - dimension: "Organizational"
        status: "[Green | Amber | Red]"
        items: []
    
    blockers:
      - blocker: "[What's blocking]"
        resolution: "[How to resolve]"
        owner: "[Who]"
        timeline: "[When]"
  
  scaling_plan:
    target_state:
      users: "[N]"
      volume: "[Transactions/period]"
      timeline: "[Target date]"
    
    phases:
      - phase: 1
        name: "[Phase name]"
        scope: "[Who/what included]"
        duration: "[Weeks]"
        success_criteria:
          - "[Criterion]"
        rollback_trigger: "[When to stop]"
      
      - phase: 2
        name: "[Phase name]"
        scope: "[Who/what included]"
        duration: "[Weeks]"
    
    infrastructure:
      current: "[Pilot infrastructure]"
      target: "[Production infrastructure]"
      changes_needed: ["[Change]"]
    
    support:
      model: "[Support model for scale]"
      resources: "[Team/headcount]"
      escalation: "[Path]"
  
  risk_mitigation:
    - risk: "[Scaling risk]"
      likelihood: "[H/M/L]"
      impact: "[H/M/L]"
      mitigation: "[Plan]"
  
  communication:
    stakeholders: ["[Stakeholder group]"]
    messaging: "[Key messages]"
    timeline: "[Communication schedule]"
  
  success_metrics:
    - metric: "[Metric]"
      pilot_value: "[Value]"
      target_at_scale: "[Value]"
      measurement: "[How tracked]"

Readiness Dimensions

Technical Readiness

yaml

technical_checklist:
  performance:
    - "Load tested at 2x projected volume"
    - "Latency acceptable under load"
    - "Error rates within tolerance"
  
  reliability:
    - "High availability configured"
    - "Disaster recovery tested"
    - "Monitoring and alerting live"
  
  security:
    - "Security review completed"
    - "Access controls configured"
    - "Audit logging enabled"
  
  integration:
    - "All integrations production-ready"
    - "API contracts stable"
    - "Data flows validated"

Operational Readiness

yaml

operational_checklist:
  support:
    - "Support team trained"
    - "Runbooks documented"
    - "Incident process defined"
  
  processes:
    - "Change management in place"
    - "Release process defined"
    - "Feedback loop established"
  
  governance:
    - "Production approval obtained"
    - "Compliance requirements met"
    - "Risk register updated"

Organizational Readiness

yaml

organizational_checklist:
  stakeholders:
    - "Executive sponsorship confirmed"
    - "Business owners engaged"
    - "Change champions identified"
  
  users:
    - "Training developed"
    - "Communication plan ready"
    - "Support channels established"
  
  resources:
    - "Team capacity allocated"
    - "Budget approved"
    - "Vendors contracted"

Scaling Patterns

Phased Rollout

code

Phase 1: Power users (2 weeks)
    └── 50-100 users
    └── Validate at small scale
    └── Refine based on feedback

Phase 2: Department (4 weeks)
    └── 500-1000 users
    └── Validate support model
    └── Stress test integrations

Phase 3: Enterprise (6-8 weeks)
    └── All target users
    └── Full production operation
    └── Steady state

Geographic Rollout

code

Phase 1: Single region/office
Phase 2: Additional regions
Phase 3: Global rollout

Feature Rollout

code

Phase 1: Core functionality
Phase 2: Additional features
Phase 3: Full feature set

Common Scaling Challenges

Challenge	In Pilot	At Scale	Mitigation
Performance	Works fine	Latency issues	Load test, right-size
Data quality	Curated data	Real-world messiness	Data validation, feedback
User adoption	Enthusiasts	Reluctant users	Training, change management
Support	Ad hoc	Unsustainable	Formal support model
Edge cases	Few	Many	Gradual rollout, monitoring

Rollback Planning

yaml

rollback_plan:
  triggers:
    - "Error rate exceeds 5%"
    - "Critical bug affecting users"
    - "Security incident"
    - "Unacceptable user feedback"
  
  procedure:
    immediate:
      - "Stop rollout to new users"
      - "Notify stakeholders"
    
    if_needed:
      - "Revert affected users to previous process"
      - "Document issues"
      - "Plan remediation"
  
  decision_authority: "[Who decides to rollback]"
  
  communication:
    internal: "[Template]"
    users: "[Template]"

Success Metrics at Scale

yaml

scale_metrics:
  adoption:
    - metric: "Active users"
      target: "[N]"
      measurement: "[How tracked]"
    
    - metric: "Adoption rate"
      target: "[% of eligible]"
  
  performance:
    - metric: "System uptime"
      target: "99.9%"
    
    - metric: "Response time p95"
      target: "<2 seconds"
  
  quality:
    - metric: "Error rate"
      target: "<2%"
    
    - metric: "User satisfaction"
      target: ">4.0/5.0"
  
  value:
    - metric: "Time savings per user"
      target: "[Hours/week]"
    
    - metric: "Process improvement"
      target: "[% improvement]"

Checklist

Pre-Scaling

• Pilot success confirmed
• Technical readiness assessed
• Operational readiness assessed
• Organizational readiness assessed
• Blockers identified and planned
• Phases defined with criteria

During Rollout

Post-Rollout

• Steady state achieved
• Handoff to operations complete
• Lessons learned documented
• Value tracking in place