Managing Engineering Velocity Without Sacrificing Code Quality
Designed for Engineering leaders new to team management, responsible for delivering features fast but struggling to balance velocity with maintaining high code quality—typically recently promoted tech leads or first-time managers overseeing multiple developers. to spark real collaboration and high-energy learning.
A 90-minute virtual workshop for recently promoted engineering managers at a SaaS company facing pressure to ship features rapidly. Their teams consist of strong developers who resist process changes, and leadership is demanding faster time-to-market. The managers feel torn between ‘move fast’ directives and their intuition that code quality is slipping.
Velocity vs Quality Quiz
Kick off with a 5-question interactive poll (e.g., Mentimeter or Zoom poll) asking participants to guess, for each scenario, whether the outcome was high velocity, high quality, or both. Scenarios are real company situations: ‘A team ships a new API in 2 weeks, but spends 3 months fixing bugs’, etc. Immediate results spark curiosity and surprise.
Tap to view the full activity.
Why this works
Curiosity-driven polls trigger participants' prior beliefs and create immediate engagement, priming the brain for deeper learning.
Myth Busting Lightning Round
Facilitator presents three common beliefs (‘Velocity always means sacrificing quality’, ‘Code reviews slow everything down’, ‘Tech debt is unavoidable if you want speed’) and invites participants to quickly vote ‘Fact or Fiction’. After each vote, facilitator reveals evidence or counterexamples.
Tap to view the full activity.
Why this works
Explicitly surfacing and challenging misconceptions leverages cognitive dissonance, clearing mental roadblocks for new learning.
Silent Sticky Note Priorities
Each participant silently writes down (virtual sticky note or physical Post-It) their top pain point about velocity vs quality on their team. Facilitator collects and displays notes anonymously, then guides a low-pressure discussion around common themes.
Tap to view the full activity.
Why this works
Low-pressure, anonymous input encourages candid participation from even introverted learners, and surfaces shared struggles.
Velocity Rituals Relay
Divide the group into two teams (breakout rooms or physically). Each team drafts a 3-step ‘velocity ritual’ they’ve seen work (e.g., daily standups, squad code reviews, feature toggles), then races to pitch their ritual in 60 seconds. Facilitator gives instant feedback and awards fun prizes.
Tap to view the full activity.
Why this works
Collaborative, competitive activities energize the room and help encode learning through peer-to-peer sharing.
Dilemma: Release Night Decisions
Facilitator presents a real dilemma: ‘It’s 6pm, product lead wants to ship a feature, but the last round of QA flagged a risky bug. What do you do?’ Participants break into small groups and debate choices (ship, delay, patch, escalate), then share their reasoning to the full group.
Tap to view the full activity.
Why this works
Real-world dilemmas anchor learning in authentic stakes and invite critical thinking, connecting theory to practice.
Personal Code Quality Commitment
Close by prompting each participant to write (chat or paper) a one-sentence commitment: ‘This week, I’ll…’ related to maintaining code quality while driving velocity. Invite volunteers to share theirs, then optionally post commitments to a shared board for follow-up.
Tap to view the full activity.
Why this works
Active reflection and goal-setting solidifies learning, making it personally relevant and actionable.
Sign up to unlock 3 more activities
Get the full pack, facilitation flow, and more ready-to-run ideas.