--- title: "Strengthening Mutual Support in Remote Teams" description: "Participants analyze realistic workplace help-seeking scenarios in small groups, reflect anonymously on real moments they hesitated to request help, and rewrite requests to lower friction." last_updated: "2026-09-07" canonical: "https://unitedwetransform.com/exercises/lack-of-mutual-support-workshopbank/" --- # Strengthening Mutual Support in Remote Teams Participants analyze realistic workplace help-seeking scenarios in small groups, reflect anonymously on real moments they hesitated to request help, and rewrite requests to lower friction. **Time:** 60 minutes. Source specifies a 60-minute duration across 5 stages. **People:** 4 to 24. Whole group introduction, breakout groups of 3 to 4, individual reflection, and whole room harvest ## Choose this exercise **Purpose:** Identify barriers to asking for or offering help within a distributed team and establish concrete behavioral commitments to address them. **Use it when:** Use when a team works in silos, hesitates to escalate bottlenecks, or expresses reluctance to interrupt colleagues for assistance. **Skip it when:** Skip when team conflict is active and unresolved, or when workload capacity is so overextended that helping peers is structurally impossible without leadership resource reallocation. ## Materials and tools - Digital whiteboard or shared collaborative document (e.g. Miro, Google Docs) - Anonymous live polling tool or integrated video chat poll - Timer visible to the facilitator - Support scenarios worksheet (provided in participant materials) ## Before participants arrive 1. Prepare the two live poll questions in your polling tool or chat. 2. Set up breakout spaces for groups of 3 to 4 people. 3. Load the support scenarios worksheet into the shared collaborative document with assigned breakout workspace sections. ## Say this to open Today we are looking at how our team asks for and offers support. Working remotely makes it easy to assume everyone else is busy or that asking for help signals trouble. We will examine three common scenarios, reflect on how we handle help requests, and identify practical adjustments we can test this week. ## How to run it ### 1. Baseline Poll and Context Setting (10 minutes) Facilitator reads the opening script and launches the anonymous poll: 'On a scale of 1 to 5, how supported do you feel by your team members right now?' Share the numeric aggregate without identifying respondents. Facilitator names three common remote barriers: hidden work queues, unclear protocols for interruptions, and reluctance to appear struggling. Invite brief chat comments on which barrier rings most familiar. ### 2. Breakout Analysis of Support Scenarios (15 minutes) Split participants into breakout groups of 3 or 4 (e.g. six groups for 24 people). Assign the three printed scenarios from the worksheet. Each group discusses: Would you ask for help in this situation? Who would you contact, and what channel would you use? What makes asking difficult here? Call groups back to the main room at the 12-minute mark and hear key points from two volunteers. ### 3. Examine Support Strategies and Team Norms (15 minutes) Facilitator presents three operational tactics: explicit help cues, scheduled check-ins before deadlines, and structured assistance channels. Post prompt in chat: 'What is one specific thing a coworker did recently that made asking for or receiving help easy?' Allow 2 minutes for typing. Facilitator reads 3 to 4 responses aloud, grouping them into proactive offers, clear availability signals, and non-judgmental responses. ### 4. Rewrite Real Hesitations (15 minutes) Prompt individuals to privately note a real, neutral moment from the last month when they needed assistance but chose not to ask. Neutral example: 'I needed a spreadsheet formula reviewed, but figured everyone was heads-down on quarterly close, so I spent three hours debugging it alone.' Participants paste their anonymized hesitation into the shared document or chat. Pick 2 or 3 submissions and invite the room to reframe them into an actionable, low-friction request. ### 5. Action Commitments and Exit Poll (5 minutes) Ask each participant to write one concrete action they will take in the coming week to either request help faster or offer help proactively. Participants may post in chat or keep it on their private notepad. Run final anonymous poll: 'How confident do you feel about applying these support habits in our team?' (Scale 1 to 5). Facilitator closes the session. ## Debrief questions - What team habit makes it easiest to know when someone genuinely has room to help? - What is the operational difference between a vague request for help and an easy-to-answer request? - Which communication channel in our team should be reserved for low-urgency questions versus time-sensitive blockers? **Finished output:** A shared document containing analyzed team barriers, rewritten help requests, and individual action commitments. ## Remote Run via video platform with breakout rooms. Use an anonymous polling tool for the entry and exit polls. Provide a shared workspace (Google Doc or digital whiteboard) divided into breakout stations so groups can capture their observations synchronously. ## Hybrid Pair in-person participants together in physical rooms using a shared laptop, or have each person join the meeting on their own device with headsets to ensure remote participants have equal visibility in breakout groups. All polling and scenario notes remain in the primary digital document. ## Access and participation choices - Anonymous polling allows participation without revealing individual sentiment. - Writing real hesitation moments is optional; participants may analyze the standard worksheet scenarios instead of disclosing personal work history. - Contributions to whole-room debriefs can be submitted via chat or voice. ## If the session gets stuck **Participants fear that rating team support low will offend colleagues or managers present.** Remind everyone before opening the poll that responses are completely anonymized and aggregated, intended to look at structural team habits rather than personal attacks. **Breakout discussions turn into venting sessions about overall workload.** Acknowledge the workload pressure directly, then redirect the prompt: 'Given that workloads are heavy, what exact signal tells you a colleague is open to a 10-minute question?' ## Terms used here - Support Channel: A designated digital space (such as a specific Slack channel or standing office hours) intended solely for asking non-urgent questions without direct messaging individuals. ## Participant material: Support Challenge Scenarios Worksheet Scenario 1: You are 24 hours away from a delivery deadline. Your remaining tasks will take roughly 8 hours, leaving no buffer for unexpected technical issues or client inquiries. - Would you ask for help? If so, when? - Who would you contact, and what specific medium would you use? Scenario 2: You are attempting to run an unfamiliar deployment or review process using documentation that seems outdated. You have tried troubleshooting for 45 minutes with no progress. - At what point do you stop self-troubleshooting? - What makes asking for assistance here difficult? Scenario 3: Your personal project queue is at capacity, and your manager assigns another mid-sized deliverable without removing existing commitments. - Would you ask a peer for help, consult your manager, or absorb the workload? - What team norms affect your decision? ## Sources and adaptation Observed in WorkshopBank under the title 'Lack of Mutual Support' / 'Strengthening Mutual Support in Remote Teams'. Retained the 5-stage workshop architecture, specific scenario themes, polling mechanics, and group sizing from the WorkshopBank source. Added explicit timing per step summing to 60 minutes, detailed facilitation instructions, an explicit neutral example for step 4, hybrid room configurations, and specific debrief prompts. [WorkshopBank](https://workshopbank.com/tools/lack-of-mutual-support-in-remote-teams) Current run sheet: https://unitedwetransform.com/exercises/lack-of-mutual-support-workshopbank/