De-escalating Tensions Between Frontend and Backend Developers
Designed for Senior full-stack developers stepping into tech lead roles, mediating between established frontend and backend teams with recent project friction. to spark real collaboration and high-energy learning.
A 90-minute, in-person workshop during a quarterly engineering offsite, where recently merged frontend and backend teams have experienced misaligned priorities, ‘us vs. them’ language, and failed integrations. Participants want practical tools, not theory, and are wary of fluffy soft-skills training.
Assumption Auction
Kick off with an ‘Assumption Auction’—participants write down one thing they believe about ‘the other side’ (FE about BE, and vice versa) anonymously. These are rapidly ‘auctioned’ off as statements, prompting laughter and surprise. This playful reveal uncovers the invisible narratives fueling tension.
Tap to view the full activity.
Why this works
Engaging curiosity and reducing defensiveness opens minds to learning; surfacing assumptions makes the workshop relevant from minute one.
‘I Thought You Knew!’ Debunk
Reveal common but false beliefs fueling tension. Present 3 statements like, ‘Frontend never cares about security’ or ‘Backend always ignores UX implications,’ and invite participants to vote true/false using colored cards. Then, share real data or lived examples to bust these myths.
Tap to view the full activity.
Why this works
Quickly brings misconceptions into the light and primes participants for new information, reducing tribal thinking.
Silent Bridge-Builders
Use a low-pressure paired listening exercise: participants partner with someone from the ‘other side’ and take turns answering, ‘What’s one thing you wish more people understood about your work?’ The other only listens—no comments allowed.
Tap to view the full activity.
Why this works
Fosters psychological safety and empathy by letting each side be heard without rebuttal or debate.
The Blame Game Relay
Turn energy up with a ‘Blame Game Relay’: small teams get a (fictional) conflict scenario—e.g., 'The API broke the UI demo.' Each side must write down all their grievances, then swap and rewrite the story from the other perspective. Fast, competitive, and guaranteed laughs.
Tap to view the full activity.
Why this works
Transforms negative energy into creative problem-solving and highlights subjectivity in conflict stories.
Feature Launch Dilemma
Pose a juicy, real-world scenario: ‘The product team just announced a major feature launch in two weeks—neither FE nor BE was consulted, and current integration is buggy.’ Small groups must decide, under time pressure, how to proceed, what to communicate, and how to keep tensions from blowing up.
Tap to view the full activity.
Why this works
Applies de-escalation strategies to authentic, high-stress situations, reinforcing learning through practice.
Personal Truce Statements
Close by asking each participant to write one ‘Personal Truce Statement’—a commitment to a concrete action or phrase they’ll use at the next sign of tension (e.g., ‘I’ll ask for their perspective before escalating’). Optionally, share with a neighbor for mutual accountability.
Tap to view the full activity.
Why this works
Active reflection cements learning, turning insight into personal behavior change and ownership.
Sign up to unlock 3 more activities
Get the full pack, facilitation flow, and more ready-to-run ideas.