{
  "operations_strand": {
    "workshop_meta": {
      "framework_version": "operations-strand-v1.0",
      "source_templates": [
        "Operational Purpose",
        "Org Structure",
        "Rituals & Cadences",
        "Cross-Functional Collaboration",
        "Execution Systems",
        "Release & Deployment Process",
        "Internal Communication",
        "Incident Management",
        "Vendor & Partner Operations",
        "Security & Compliance Operations",
        "People Ops & HR Operations",
        "Finance & Legal Ops",
        "Risk & Decision Frameworks"
      ],
      "facilitation_notes": [
        "Run with COO, operations leadership, product, engineering, HR, legal, security.",
        "Start with real workflows: incident response, shipping new features, onboarding employees, fiscal planning.",
        "This JSON defines *how the company actually works every day* — the OS of internal execution."
      ]
    },

    "purpose_and_role": {
      "question": "Why does Operations exist?",
      "answer": "Operations ensures that Slack runs predictably, safely, and efficiently. It coordinates people, processes, tools, and decision-making structures so the company can scale without chaos. Operations is the connective tissue that synchronizes product, engineering, sales, success, finance, people, and security.",
      "objectives": [
        "Create processes that scale with the company.",
        "Remove friction from cross-functional work.",
        "Ensure predictable shipping, reliability, and support.",
        "Protect the company through compliance, security, and risk management.",
        "Maintain operational clarity as the organization grows."
      ]
    },

    "org_structure": {
      "question": "How is the operational organization structured?",
      "departments": [
        {
          "name": "Product Operations",
          "responsibilities": [
            "Roadmap coordination",
            "Product launch readiness",
            "User feedback systems",
            "Cross-functional alignment"
          ]
        },
        {
          "name": "Engineering Operations (EngOps)",
          "responsibilities": [
            "Developer productivity",
            "CI/CD & tooling",
            "On-call processes",
            "Infrastructure coordination",
            "Incident response frameworks"
          ]
        },
        {
          "name": "Customer Operations (CustOps)",
          "responsibilities": [
            "Support systems",
            "Service workflows",
            "Customer health and adoption"
          ]
        },
        {
          "name": "Security Operations (SecOps)",
          "responsibilities": [
            "Threat detection",
            "Compliance enforcement",
            "Access management",
            "Security incident response"
          ]
        },
        {
          "name": "Revenue Operations (RevOps)",
          "responsibilities": [
            "Sales forecasting",
            "Pipeline health",
            "Billing + monetization systems"
          ]
        },
        {
          "name": "People Operations (PeopleOps)",
          "responsibilities": [
            "Hiring systems",
            "Onboarding",
            "Career frameworks",
            "Compensation modeling"
          ]
        },
        {
          "name": "Business Operations (BizOps)",
          "responsibilities": [
            "Strategic analysis",
            "Goal planning",
            "Cross-company prioritization"
          ]
        }
      ]
    },

    "operational_rituals": {
      "weekly": [
        "Team stand-ups",
        "Cross-functional syncs (product + eng + design)",
        "Incident review meetings",
        "Support + product friction reviews",
        "Goal progress updates"
      ],
      "monthly": [
        "Roadmap review",
        "Business health metrics",
        "Customer insights analysis",
        "Security review",
        "Recruiting pipeline review"
      ],
      "quarterly": [
        "Company-wide OKR review",
        "Planning for next quarter",
        "Budget & resource allocation",
        "Technical debt prioritization",
        "Compliance & audit check-ins"
      ]
    },

    "cross_functional_collaboration": {
      "question": "How do teams collaborate effectively?",
      "systems": [
        "Shared Slack channels for each initiative",
        "Slack Connect for external partners",
        "Asana/Jira for project management",
        "Google Workspace for documents",
        "Centralized internal wiki for knowledge"
      ],
      "rules": [
        "One owner per initiative, many collaborators.",
        "Decisions documented in Slack channels or internal wiki.",
        "Cross-functional leads meet weekly during high-impact launches.",
        "Slack-first communication before meetings."
      ],
      "anti_patterns": [
        "Multiple owners",
        "Decision-making inside private DMs",
        "Undocumented cross-team agreements",
        "“Shadow” processes outside shared tools"
      ]
    },

    "execution_systems": {
      "product_development_framework": "Modified dual-track agile: continuous discovery + continuous delivery.",
      "tools": [
        "Jira for engineering execution",
        "Figma for design",
        "Slack for alignment",
        "Github for code reviews and version control"
      ],
      "stages": [
        "Problem definition",
        "Design exploration",
        "Technical scoping",
        "Implementation",
        "Testing",
        "Launch readiness",
        "Release",
        "Post-release monitoring"
      ],
      "definition_of_done": [
        "Meets acceptance criteria",
        "Passes accessibility checks",
        "Docs updated",
        "Support ready",
        "Logs + metrics instrumented",
        "Feature flags available",
        "Incident alerting configured"
      ]
    },

    "release_and_deployment": {
      "pipeline": [
        "Commit → CI → Automated tests",
        "Staging environment → QA",
        "Gradual rollout via feature flags",
        "Monitoring + rollback capability",
        "Full deployment after stability confirmation"
      ],
      "principles": [
        "Small, frequent releases reduce risk.",
        "Feature flags for all user-facing changes.",
        "Automated tests prevent regressions.",
        "Rollback must be instant and safe."
      ],
      "responsibilities": {
        "product": "Owns definition, acceptance, launch messaging.",
        "engineering": "Owns quality, deployment, monitoring.",
        "support": "Prepared with macros, scripts, troubleshooting guides."
      }
    },

    "internal_communication": {
      "channels": [
        "Company-wide announcements channel",
        "Team channels with weekly summaries",
        "Project-specific channels",
        "Docs in internal wiki",
        "Asynchronous updates via Slack canvases"
      ],
      "principles": [
        "Document decisions in public channels, not private chat.",
        "Over-communicate during high-risk or high-impact projects.",
        "Summaries over raw message threads.",
        "Async-first: meetings only when truly needed."
      ]
    },

    "incident_management": {
      "incident_severity_levels": [
        "SEV0 — complete outage or security breach",
        "SEV1 — severe degradation",
        "SEV2 — functional but impaired",
        "SEV3 — minor impact"
      ],
      "response_process": [
        "On-call engineer paged automatically",
        "Incident lead + scribe assigned",
        "Dedicated Slack channel created",
        "Status page updated (if needed)",
        "Customer communication through predefined templates",
        "Root-cause analysis within 48 hours"
      ],
      "post_incident_practices": [
        "Blameless postmortems",
        "Actionable follow-up tasks",
        "Engineering retro",
        "Documentation updates"
      ]
    },

    "vendor_and_partner_operations": {
      "critical_vendors": [
        "Cloud providers",
        "CI/CD services",
        "Security scanning tools",
        "Observability platforms",
        "Support ticketing systems",
        "Payment processors"
      ],
      "vendor_management": [
        "Annual reviews",
        "Security questionnaires",
        "SLA monitoring",
        "Cost optimization",
        "Compliance audits"
      ]
    },

    "security_and_compliance_operations": {
      "responsibilities": [
        "Access management (SSO, role-based access)",
        "Pen tests and vulnerability management",
        "Privacy reviews of new features",
        "Compliance audits (SOC2, ISO, FedRAMP)",
        "Data residency enforcement",
        "Security training for employees"
      ],
      "principles": [
        "Security embedded early in development.",
        "Privileged access reviewed weekly.",
        "Zero-trust network assumptions.",
        "Data minimization everywhere possible."
      ]
    },

    "people_operations": {
      "hiring_process": [
        "Role definition",
        "Structured interviews",
        "Skill evaluation",
        "Values & collaboration assessment",
        "Offer approval",
        "Onboarding checklist"
      ],
      "onboarding": [
        "Slack workspace setup",
        "Tooling access",
        "Team intro",
        "Role-specific training",
        "First week goals"
      ],
      "performance_management": [
        "Quarterly reviews",
        "Career ladders",
        "Compensation cycles",
        "Promotion criteria",
        "Performance improvement processes"
      ],
      "culture_principles": [
        "Empathy",
        "Courtesy",
        "Craftsmanship",
        "Playfulness without distraction",
        "Transparent communication"
      ]
    },

    "finance_and_legal_ops": {
      "finance": [
        "Budget planning",
        "Cost control",
        "Scenario modeling",
        "SaaS vendor consolidation",
        "Revenue forecasting",
        "Expense approvals"
      ],
      "legal": [
        "Contract review",
        "Regulatory compliance",
        "Data processing agreements",
        "Risk management",
        "IP protection",
        "Vendor security terms"
      ]
    },

    "risk_and_decision_frameworks": {
      "decision_making": [
        "RACI for major initiatives",
        "Docs for all decisions above medium risk",
        "Async-first decisions with clear deadlines",
        "Escalate when blocked >48 hours"
      ],
      "risk_types": [
        "Technical risk",
        "Operational risk",
        "Security risk",
        "Legal/compliance risk",
        "Reputational risk"
      ],
      "risk_controls": [
        "Checklists for major launches",
        "Performance/load testing pre-release",
        "Security reviews pre-launch",
        "Runbooks for outage scenarios"
      ]
    },

    "operations_archetype": {
      "question": "What character best represents Operations?",
      "primary_archetype": "Architect",
      "secondary_archetype": "Orchestrator",
      "rationale": "Operations designs the invisible structures and keeps all moving parts synchronized, ensuring stability and clarity as the company scales."
    }
  }
}