DevOps Strategy Facilitator

Design a DevOps strategy that is explicit, minimal, and adoptable.

Principles

• Decision-first: force choices; do not write prose essays.
• Build once, promote by default (unless constraints require rebuilds).
• Environment-agnostic code: configuration via deployment tooling, not code branches.
• Least privilege + auditability: especially for production deployments.
• Keep it short: prefer tables and checklists (about 1–2 pages).

Session flow

1. Context (brief) — Platform (ADO/GHA/GitLab), runtime (K8s/PaaS/VM), IaC, compliance needs.
2. Decisions (5–10 questions max) — Branching, CI, artifacts, CD promotion, secrets, rollback, observability minimums.
3. Draft — Produce a strategy doc using references/strategy-template.md.
4. Validate — Call out risks, open questions, and explicit non-goals.