Transitioning Manual Deployments to Fully Automated GitHub Actions
Designed for Senior DevOps engineers responsible for modernizing legacy deployment practices in mid-sized SaaS companies to spark real collaboration and high-energy learning.
A 90-minute physical workshop in the company’s main conference room. Attendees are experienced with manual scripts but face growing frustration with inconsistent release outcomes, error-prone handoffs, and deployment delays. Leadership has mandated a move to GitHub Actions, but teams feel overwhelmed and doubt automation reliability.
Deployments: Then vs. Now
Kick off with a side-by-side visual timeline showing ‘Manual Deployment Day’ vs. ‘GitHub Actions Deployment Day’. Each participant annotates what’s missing, risky, or improved in the automated version, sparking curiosity and a sense of discovery.
Tap to view the full activity.
Why this works
Visual storytelling and annotation foster cognitive engagement and highlight gaps, priming curiosity. It grounds abstract automation in relatable daily reality.
Automation Mythbusters
Present three classic misconceptions (“Automated deployments are always error-free”, “You can’t rollback easily”, “Manual oversight is safer”). Invite the group to vote ‘Fact or Myth’ via colored cards, then review real failure cases and true rollback stories.
Tap to view the full activity.
Why this works
Misconceptions block adoption and learning; surfacing them reduces resistance and corrects mental models. Interactive voting lowers defensiveness.
Workflow Sketch Pad
Low-pressure, collaborative sketching: In pairs, participants draw their current manual workflow steps and brainstorm how each could map to an automated step. No coding—just sticky notes, arrows, and imagination.
Tap to view the full activity.
Why this works
Removing code and pressure allows creative exploration and safe participation, especially for those unsure about automation.
Action Race Challenge
Divide the room into two teams. Each team is given a broken deployment scenario (e.g., missing environment variable, failed build). Race: Build the shortest possible GitHub Actions workflow fixing the problem, using magnetic tiles or digital cards. Winning team shares their solution.
Tap to view the full activity.
Why this works
High-energy competition activates collective focus, speeds up problem-solving, and provides immediate payoff. Fast rounds reinforce teamwork.
Release Day Dilemma
Present a real-world dilemma: ‘It’s Friday afternoon. Your manual deployment succeeded, but a bug appears in production. With GitHub Actions, how would your automated rollback protect you differently?’ Groups discuss, then role-play their response.
Tap to view the full activity.
Why this works
Rooting learning in authentic dilemmas makes new concepts personally relevant and memorable. Role-play builds empathy and practical understanding.
Deployment Story Reflection
Invite each participant to share a personal deployment story—‘One time a manual deployment went sideways, and what you wish automation could’ve done.’ Participants jot down what part of their story they’d want GitHub Actions to tackle first.
Tap to view the full activity.
Why this works
Personal reflection connects abstract learning to lived experience, deepens motivation, and drives behavior change.
Sign up to unlock 3 more activities
Get the full pack, facilitation flow, and more ready-to-run ideas.