Transitioning to Trunk-Based Development in Large Software Orgs
Designed for Lead software engineers and senior engineering managers at enterprise organizations currently using long-lived feature branching who are tasked with improving release cadence and codebase stability. to spark real collaboration and high-energy learning.
A 90-minute hybrid workshop for engineering leadership cohorts in a Fortune 500 software org. Attendees are responsible for leading cross-team architecture changes and must reconcile developer autonomy with organizational demands for faster, safer releases. Common pain points include: perceived loss of code ownership, integration conflicts, and anxiety over breaking longstanding workflows.
Release Train Mystery Map
Kick off with an interactive visualization challenge: display a purposely scrambled release timeline from a real-world org that moved to trunk-based development. Participants, in small groups, decode which release model was used (feature branches vs. trunk), spotting clues in integration bursts and deployment frequency. The payoff: a-ha moments about the hidden costs of their current model.
Tap to view the full activity.
Why this works
Curiosity and surprise are powerful motivators—this activity exposes the unfamiliar benefits of trunk-based development by engaging analytical thinking and peer discussion.
Mythbusting Bingo Board
Quick-fire mythbusting: hand out bingo cards listing common misconceptions about trunk-based development (e.g., 'It’s only for startups,' 'We’ll lose all code review,' 'Integration hell gets worse'). As you read out statements, participants mark true/false and discuss in pairs why each is (or isn’t) a myth.
Tap to view the full activity.
Why this works
Addressing misconceptions openly creates trust and enables participants to recalibrate mental models before tackling practical content.
Seamless Merge Confidence Poll
Low-pressure digital poll: 'When was the last time your team merged a two-week-old branch without drama?' Participants answer anonymously, then review the group’s confidence levels. This normalizes anxieties and sets the stage for deeper sharing.
Tap to view the full activity.
Why this works
Low-stakes participation fosters psychological safety, inviting honest reflection without fear of judgment.
Integration Jenga Challenge
Liven the room with a Jenga (or virtual block-stacking) race: each group adds blocks for every new feature branch, but random integration cards force them to pull blocks at unpredictable moments. The stack’s collapse mirrors integration disasters in feature-branch-heavy orgs.
Tap to view the full activity.
Why this works
Physical simulation accelerates learning; visceral experience of system fragility makes abstract risks real.
The Code Freeze Dilemma
Present a dramatic, real-world scenario: a flagship product faces a critical bug two days before launch, but the codebase is mid-freeze and half the team’s work sits in isolated branches. In breakout groups, participants debate: stick to process, or risk a rushed integration?
Tap to view the full activity.
Why this works
Dilemmas build emotional investment and force practical reasoning about the consequences of branching strategies.
Commitment Reflection Wall
Close with a personal reflection wall: each participant writes (physical sticky or virtual board) one common trunk-based development challenge they will commit to address with their team, and one old habit they’re willing to leave behind.
Tap to view the full activity.
Why this works
Self-generated commitments boost ownership and bridge workshop learning with real-world action.
Sign up to unlock 3 more activities
Get the full pack, facilitation flow, and more ready-to-run ideas.