Implementing Progressive Delivery with Canary Deployments and Blue-Green
Designed for Senior DevOps engineers and Platform Leads at mid-to-large SaaS companies responsible for reducing deployment downtime and risk while accelerating delivery. to spark real collaboration and high-energy learning.
A 90-minute hybrid workshop. Audience members are highly technical, have partial experience with CI/CD, but struggle with aligning speed of delivery with reliability due to failed rollouts or lack of automated rollback. Many are skeptical about the overhead of new processes and need to see direct value for their specific business-critical releases.
Deployment Detective Cold Open
Kick off with a mysterious, anonymized post-mortem Slack thread snippet: “At 2:17am, user signups dropped by 70%. Only 1% of traffic was exposed to the new feature—yet rollback took an hour. Why?” Participants silently hypothesize what happened, then share quick takes via chat or sticky notes.
Tap to view the full activity.
Why this works
Mystery scenarios spark anticipation and highlight gaps in intuitive reasoning, priming curiosity for the core content.
Canary ≠ Risk-Free! Quick Quiz
Present a rapid-fire myth-busting quiz: 'Can canary deployments prevent all production outages? True or False?' Continue with 2 more common misconceptions (e.g., 'Blue-green always doubles infrastructure costs'). Discuss instant poll results as a group.
Tap to view the full activity.
Why this works
Surfacing and correcting myths removes blockers, clears cognitive bias, and opens participants to nuanced practices.
Zero-Stress Rollout Map
Invite participants to collectively assemble a physical or digital flowchart depicting a progressive delivery process, using color-coded cards or drag-and-drop tiles. Each person contributes one step—no right or wrong answers, just sequence brainstorming.
Tap to view the full activity.
Why this works
Low-pressure co-creation makes the process tangible, supports psychological safety, and warms up the room for deeper technical dives.
Release Race: The 2-Minute Challenge
Divide into small teams and run a gamified, simulated deployment: Teams have 2 minutes to choose between canary and blue-green strategies for a fictional release scenario—balancing risk, speed, and user impact. Fastest thoughtful decision wins!
Tap to view the full activity.
Why this works
Timed challenge energizes, encourages quick synthesis of new concepts, and makes decision tradeoffs concrete.
PagerDuty Nightmare—What Would You Do?
Present a gripping true-to-life Slack screenshot: 'PagerDuty: Latency spike detected in blue environment!' Participants must choose: rollback, pause, or move ahead. After votes, debrief what an on-call engineer actually did—and the fallout.
Tap to view the full activity.
Why this works
Anchoring with authentic dilemmas confronts participants with the emotional and strategic weight of deployment failures.
Personal Delivery Debrief
Invite each participant to privately jot down (or type) the last time their deployment process failed—or nearly did. Then, in pairs or trios, share what they wish they’d had in place (e.g., observability, automated rollback) and identify one concrete next step for their team.
Tap to view the full activity.
Why this works
Active reflection grounds learning in personal experience, increases emotional investment, and drives actionable commitment.
Sign up to unlock 3 more activities
Get the full pack, facilitation flow, and more ready-to-run ideas.