How to Manage Quiet Quitting Behaviors in Tech Teams
Designed for Tech team leads and first-line engineering managers noticing disengagement or 'coasting' behaviors among high-performing software engineers. to spark real collaboration and high-energy learning.
A 90-minute hybrid workshop for engineering managers at a mid-sized SaaS company. Many report difficulty detecting disengagement until it affects sprint outcomes; some feel ill-equipped to address root causes without sounding accusatory or out-of-touch. The session balances practical frameworks with live skills practice, catering to both in-person and remote participants.
Quiet Quitting in One Minute
Kick off with a quick-fire, curated set of 4 real-world vignettes: chat logs, Jira board screenshots, and email snippets showing subtle disengagement. Ask participants to jot down their gut reaction—'Is this quiet quitting or not?'—and share in a live poll.
Tap to view the full activity.
Why this works
Uncovering ambiguity and building curiosity primes attention and creates a safe space to explore this nuanced issue.
Mythbusting: What Quiet Quitting Isn’t
Share a provocative statement: 'Quiet quitting is just laziness.' Invite participants to post their gut reaction anonymously (using sticky notes in-person or an online whiteboard virtually). Reveal three data-backed counter-examples that bust common myths.
Tap to view the full activity.
Why this works
Directly addressing misconceptions clears cognitive roadblocks, making space for new understanding.
Silent Signals Bingo
Hand out bingo cards with subtle quiet quitting behaviors (e.g., 'Stops attending daily standup cam-on,' 'No comments on PRs'). As you read scenarios, participants mark their cards if they’ve noticed the behavior. First bingo gets a shout-out.
Tap to view the full activity.
Why this works
Low-pressure participation and pattern recognition lower barriers and build community among managers facing similar challenges.
The Engagement Energy Storm
Divide participants into groups. Give each a pack of emoji cards (physical or digital). Show a series of common team moments—like all cameras off after a failed sprint—and ask each group to hold up the emoji reflecting team energy. Groups then rapid-fire brainstorm 3 ways to boost engagement in that scenario.
Tap to view the full activity.
Why this works
Injecting energy breaks down tension, primes creative thinking, and models emotion-checking as a leadership tool.
Dilemma: Speak Up or Let It Ride?
Present a real-world dilemma: 'Your senior backend dev delivers all code on time, but never offers suggestions or joins mentoring sessions anymore.' Facilitate a whole-group debate: Should you address this directly now, or observe for another sprint? Why?
Tap to view the full activity.
Why this works
Grappling with gray areas enhances transfer of learning and builds real situational judgment.
Personal Action Pledges
Wrap up with a guided reflection: Ask each participant to write down one quiet quitting signal they’ve noticed but not addressed, and one specific action they’ll take this week. Collect pledges (on cards or via chat) to revisit in a follow-up email.
Tap to view the full activity.
Why this works
Personal commitment and articulation of next steps builds accountability and primes actual behavior change.
Sign up to unlock 3 more activities
Get the full pack, facilitation flow, and more ready-to-run ideas.