How to Deal with Quiet Quitting Dynamics in Engineering Teams
Designed for Senior engineering managers leading cross-functional development teams in mid-to-large tech companies, who are noticing engagement dips but lack formal HR training. to spark real collaboration and high-energy learning.
A 90-minute hybrid learning session held in a tech firm’s innovation hub, with senior managers joining both in-person and via Zoom. Participants have observed subtle drops in team energy, code quality, and initiative but report that traditional HR-driven solutions feel tone-deaf or are met with skepticism from their technically-minded teams.
The ‘What’s Missing?’ Backlog
Display an anonymized sprint board or Jira backlog with subtle indicators of disengagement (e.g., stories with zero comments, repeated unclaimed tasks, PRs with overdue reviews). Ask participants to scan and guess: what’s missing here? Prompt for observations that spark curiosity about invisible team dynamics.
Tap to view the full activity.
Why this works
Engineers are natural pattern-spotters; leveraging real artifacts taps into their analytical curiosity and primes them to see hidden disengagement clues.
Mythbusting the ‘Checked Out’ Engineer
Present three widely-held beliefs about disengaged engineers: 1) 'They’re just lazy,' 2) 'They don’t care about the company,' 3) 'Technical work means less emotion.' Poll the group live: which do you feel is most true, least true, or have heard around you? Reveal research/statistics debunking each myth.
Tap to view the full activity.
Why this works
Challenging mistaken assumptions helps shift from blame to understanding, opening space for empathetic leadership.
Slack Emoji Pulse-Check
Invite everyone to react to a series of emoji options (shared on-screen or in chat): 💬 = I’ve seen this, 🤔 = Not sure, 👀 = Want to know more, 🚫 = Not relevant. Use 2-3 real disengagement cues (e.g., repeated muted mic, minimal code review feedback, ‘just enough’ PRs). No pressure to speak—just click or hold up cards.
Tap to view the full activity.
Why this works
Reduces performance anxiety, allowing everyone to participate and signal resonance without spotlighting individuals.
Code Standup Energizer
Split into small groups, give each team a 2-minute challenge: ‘You’re the project lead and notice your top engineer is suddenly only giving 1-word standup answers. In 90 seconds, brainstorm as many *non-blame* causes as possible for this shift.’ Fast share-out, prizes for most creative answers.
Tap to view the full activity.
Why this works
The time pressure and competitive angle raise energy, while shifting focus from blame to curiosity about root causes.
The On-Call Dilemma
Present a real-world hook: ‘Your backend engineer, Raj, is always first to volunteer for on-call shifts, but his creative contributions in sprint planning have dried up. You learn he’s mentoring a junior at night and seems exhausted. Do you reduce his load (risking coverage gaps), or push for re-engagement?’ Invite the group to debate potential approaches live.
Tap to view the full activity.
Why this works
Anchoring in a messy, plausible dilemma encourages deeper engagement and challenges simplistic ‘fixes’—mirroring real leadership decisions.
Disengagement Antidotes—Personal Map
Invite each participant to draw (or type) a simple ‘Engagement Map’ of their current team: For each member, jot one thing that energizes them outside code. Then, write one specific thing you could try this month to re-engage someone at risk of quiet quitting. Wrap with a volunteer share.
Tap to view the full activity.
Why this works
Personal reflection cements learning and moves participants from theory to actionable next steps tailored to their real teams.
Sign up to unlock 3 more activities
Get the full pack, facilitation flow, and more ready-to-run ideas.