Purpose

Instructions

1. Define the offsite's purpose (most important step).

   • Not "team building" (vague). Instead: "Align on 2026 product roadmap and resolve the conflict between platform vs. custom builds."
   • Or: "Build trust in the new team structure after the merger; agree on decision-making norms."
   • Or: "Solve our distributed onboarding problem; design a solution we can pilot next quarter."
   • One sentence. Clear.

2. Assess team context before planning.

   • Ask: Is there unresolved conflict? If yes, name it. You'll address it directly, not dance around it.
   • Is there remote/co-located inequality? If yes, design the offsite to be inclusive (laptops-down for everyone, not just the in-person people).
   • What's the biggest decision or problem the team is wrestling with? Make that the centerpiece, not a side session.
   • How much budget and time do you have? (2 days? 3 days? One afternoon?)

3. Pre-work (1–2 weeks before).

   • Send participants required reading or data. "Before the offsite, read the competitor analysis." "Watch these three recorded demos."
   • Ask people to submit one question or concern anonymously (Google Form). You'll use this to design agenda and ensure the real issues get air time.
   • Share the agenda and purpose: "Here's why we're meeting. Here's what we're solving."

4. Design the agenda in three parts.

   Part A: Warm-up and connection (0–2 hours, day 1 morning).

   • 30 min: Arrival, coffee, settle.
   • 30 min: Opening from leadership. "Here's why we're here. Here's what I hope happens. We're going to disagree, and that's good."
   • 30 min: Icebreaker or low-stakes conversation. NOT a team-building game (cringey). Instead: "What's one thing you're excited about in your work right now?" Go around the room (literal or virtual). Builds empathy, not awkwardness.

   Part B: Deep work (4–6 hours, day 1 afternoon + day 2).

   • This is the hard stuff. Laptops down (literally put them away).
   • Use whiteboards (or virtual whiteboards if distributed). Capture thinking visibly.
   • Structure the work as:
     • Hour 1: Frame the problem. "Here's the question we're solving: Should we build platform or stay custom?"
     • Hour 2–3: Brainstorm or debate. Different formats:
       • Structured debate: Assign teams to argue for/against a position. Hear both sides fully. Reduces groupthink.
       • Round-robin input: Each person has 10 min uninterrupted time to share their view (recorded if distributed so you don't lose voices).
       • Working groups: Divide into 2–3 small groups working on sub-problems, then regroup to synthesize.
     • Hour 4–5: Synthesis or decision. "Here's what we heard. Here's what we're deciding. Here's the trade-off."
     • Hour 6: Action items and clear next steps. Assign owners, deadlines.

   Part C: Connection and closing (1–2 hours, day 2 afternoon or end of day 1).

   • 30 min: Celebrate. Share one win from the past quarter. Acknowledge someone's contribution.
   • 30 min: Social or low-key time. Dinner, walk, game (optional, not mandatory).
   • 30 min: Closing from leadership. "Here's what we decided. Here's what's changing. Here's how it affects you."

5. Address conflict directly if it exists.

   • Before the offsite, if you know there's tension (e.g., product vs. eng have different roadmap views), name it in the pre-work: "One thing we'll resolve at the offsite is the product vs. platform debate."
   • Don't bury it under soft skills training. Soft skills won't fix strategic misalignment.
   • Create space for people to voice concerns async before the offsite (Google Form), so leadership has heard the unspoken tensions.
   • At the offsite, use a structured debate format: each side gets 20 min uninterrupted time. Then synthesis.

6. Make it safe for remote people.

   • If some people are co-located and some are remote, everyone dials in from their own laptop (even if sitting in the same room). Laptops-down, whiteboards on screen.
   • If facilitating breakout groups, ensure remote people are in every group (not all remote, all co-located).
   • Use shared Google Docs or Miro boards so everyone sees what's being captured in real time.
   • For voting or ranking ideas, use async (Slack poll, anonymous Google Form) so quiet people have equal voice.

7. Set a hard stop on each session (time-box rigorously).

   • Deep work sessions often run over because people are engaged. But overrunning kills momentum for the next session.
   • Use a visible timer. Facilitator calls "We're at the 5-minute mark; wrap up your thought."

8. Capture outputs clearly.

   • For each deep work session, one person (not the facilitator) takes notes. What problem did we frame? What were the options? What did we decide?
   • Photo of whiteboards. Shared doc updated in real time.
   • No surprises on decision clarity; people leave knowing what changed.

9. Post-offsite (within 1 week).

   • Send a summary: "We decided X. Here's the rationale. Here's who owns the next step."
   • Schedule follow-up 1:1s to ensure everyone feels heard (especially people who were quiet or remote).
   • Create action items in your tracking system (Linear, Asana) with clear owners and deadlines.
   • Solicit feedback: "How was the offsite? What worked? What should we change next time?"

10. For distributed teams, consider quarterly "bursts".

    • Instead of annual 3-day offsite, do quarterly 1–2 day sessions with a rotating location or consistent remote setup.
    • Build relationships incrementally; easier to maintain trust than rebuild it annually.
    • Quarterly cadence aligns with business cycles, making offsites strategically timely.

Output Format

# [TEAM] Offsite Plan
**Date**: [DATES] | **Location**: [LOCATION/Virtual] | **Purpose**: [ONE SENTENCE]
**Owner**: [NAME] | **Budget**: [AMOUNT] | **Participants**: [NUMBER + NAMES/ROLES]

---

## Why We're Doing This
[One paragraph on the purpose and what problem you're solving.]

---

## Pre-Work (Due 1 week before)
- [ ] Read: [Document or article]
- [ ] Watch: [Recording or video]
- [ ] Submit concern/question (anonymous form, link)

---

## Agenda

### Day 1

**Morning (9:00 AM – 12:00 PM)**
- 9:00–9:30 AM: Arrival, coffee, settle
- 9:30–10:00 AM: Opening from [LEADER]. "Here's why we're here. Here's what success looks like."
- 10:00–10:30 AM: Icebreaker. Go-around: "What's one thing you're excited about in your work?"
- 10:30–12:00 PM: **LAPTOPS DOWN.** Whiteboards active. Frame the problem: [SPECIFIC TOPIC]. Input round-robin.

**Lunch: 12:00–1:00 PM** (catered, informal)

**Afternoon (1:00 PM – 5:00 PM)**
- 1:00–2:30 PM: **Deep work: Debate or working groups.** [SPECIFIC ACTIVITY, e.g., "Structured debate: Platform vs. custom. Each side has 15 min uninterrupted."]
- 2:30–2:45 PM: Break
- 2:45–4:30 PM: **Continued deep work or synthesis.** [e.g., "Hear both sides; identify what we agree on; decide."]
- 4:30–5:00 PM: Recap decisions. "Here's what we decided. Owner: [NAME]. Next step: [ACTION]."

**Evening: 5:00 PM onward** (optional dinner or free time)

### Day 2

**Morning (9:00 AM – 12:00 PM)**
- 9:00–9:30 AM: Coffee, informal
- 9:30–11:30 AM: **Deep work (continued or new topic).** [e.g., "Design the Q2 roadmap. Working groups by area."]
- 11:30 AM–12:00 PM: Regroup and synthesize. Capture decisions.

**Lunch: 12:00–1:00 PM**

**Afternoon (1:00 PM – 3:00 PM)**
- 1:00–1:45 PM: Celebration and connection. Recognize wins. Acknowledge contributions.
- 1:45–2:15 PM: Leadership closing. "Here's what changes. Here's how it affects you."
- 2:15–3:00 PM: Optional: Walk, social, game. Not mandatory.

---

## How We're Handling Remote People

- Everyone dials in from their own laptop (even if co-located in the same room).
- Shared Google Doc or Miro board for all whiteboarding; remote people see in real time.
- Breakout groups: Remote people in every group.
- Voting: Use async (Google Form, Slack poll) so all voices heard equally.

---

## Success Metrics

- [ ] Everyone can articulate the decision(s) we made and why.
- [ ] Action items are clear; owners and deadlines captured.
- [ ] Remote people felt included and heard.
- [ ] At least one uncomfortable conversation happened and was resolved (if conflict was the purpose).
- [ ] Team leaves feeling energized, not drained.

---

## Post-Offsite (1 week after)

- [ ] Send summary email: decisions, owners, next steps.
- [ ] Create action items in [TRACKING SYSTEM].
- [ ] 1:1s with people who were quiet or remote (ensure they felt heard).
- [ ] Feedback survey (Google Form): "What worked? What should we change next time?"

---

## Notes and Decisions

[Facilitator captures big decisions, trade-offs, and assumptions made during offsite.]

Example

Velocity Motors (fictional 22-person hardware + software org, distributed across Austin HQ and Berlin office, post-Series A)

# Velocity Motors Q2 Offsite Plan
**Dates**: April 14–16, 2026 | **Location**: Austin HQ (Berlin team on Zoom)
**Purpose**: Resolve the platform vs. custom components debate; align on Q2 roadmap and delivery targets.
**Owner**: Sarah (VP Eng) | **Budget**: $12K | **Participants**: 22 people (14 in Austin, 8 in Berlin)

---

## Why We're Doing This

Velocity Motors is at an inflection point. We're growing the team fast (hired 5 people in Q1), and the engineering org is debating a fundamental strategic choice: do we invest in a platform approach (shared components, faster shipping long-term) or stay custom (slower but more optimized per-customer)? This debate has played out in async channels for 6 weeks with no resolution. The sales and product teams are also unclear on the roadmap impact, which is slowing hiring and customer conversations.

We're using this offsite to:
1. Hear both sides of the platform vs. custom debate fully (no drive-bys).
2. Align on Q2 roadmap with clear delivery targets.
3. Build trust in the new, larger team (post-hiring).
4. Decide on team structure and who owns what area.

Success looks like: everyone leaves with a clear roadmap they believe in, understands the platform trade-off, and knows their role in Q2.

---

## Pre-Work (Due April 7)

- [ ] Read: Platform vs. Custom whitepaper (Google Doc link) — 15 min read. Both perspectives included.
- [ ] Watch: Q1 demo reel (5 min video). What did we ship? What was hard?
- [ ] Submit 1–3 questions (anonymous Google Form): "What concerns do you have about Q2? What do you want to see resolved at the offsite?"
- [ ] Mandatory attendees confirm by April 10.

---

## Agenda

### Day 1: Monday, April 14

**Morning (8:30 AM – 12:30 PM Austin time / 5:30 PM – 9:30 PM Berlin time)**
- **8:30–9:00 AM**: Arrival. Coffee. People get settled. (Remote people on Zoom, camera on.)
- **9:00–9:15 AM**: Opening from Sarah (VP Eng): "Here's why we're here. Platform vs. custom has been a live debate for 6 weeks. Today, we're not compromising. We're deciding. We're also not pretending this will be comfortable—some people have strong views. But we're committing to the outcome. That's what matters. Let's go."
- **9:15–9:45 AM**: **Icebreaker (LAPTOPS DOWN).** Go-around: "What's one thing you shipped in Q1 you're proud of?" Gives people a win, not a heavy topic.
- **9:45–12:30 PM**: **DEEP WORK: Platform vs. Custom Debate.** (Laptops away, whiteboards on.)
  - **9:45–10:15 AM**: Frame the question. Sarah shows the two options on a whiteboard: (A) Build shared platform (6-month investment, 30% faster shipping in year 2), (B) Stay custom (faster to ship Q2, customer-specific, scaling risk).
  - **10:15–10:45 AM**: **Platform team presents their case** (15 min uninterrupted). Marcus (platform lead) + 2 engineers. Whiteboard what the platform would look like, timeline, risks, upside.
  - **10:45–11:15 AM**: **Custom team presents their case** (15 min uninterrupted). Yuki (customer engineering lead) + 2 support people. Whiteboard what staying custom means for customer ability to customize, support load, scaling risk.
  - **11:15–11:30 AM**: Break. (Stretch, bathroom, coffee.)
  - **11:30 AM–12:15 PM**: **Structured Q&A and debate.** Facilitator (Sarah) guides:
    - "Platform team: what's your risk mitigation if we lose a customer while building?"
    - "Custom team: what's the support headcount risk in year 2?"
    - Remote people get equal voice (Slack raised hands or direct Zoom input).
  - **12:15–12:30 PM**: Sarah decides. "We're going platform. Here's why: long-term, it's the right bet. Here's the trade-off: Q2 shipping slows for platform work. Here's what we need: Marcus owns the platform team. Yuki, you own customer success and we're hiring a support role to take scaling risk off you. That's the decision."

**Lunch: 12:30–1:30 PM** (catered at HQ; Berlin team eats at their own desks at their time).

**Afternoon (1:30 PM – 5:30 PM Austin / 10:30 PM – 2:30 AM Berlin)**
- **1:30–2:00 PM**: 30-min break. (Coffee, walk, chill.)
- **2:00–5:30 PM**: **Q2 Roadmap Working Sessions.** (Laptops OK here; collaborative drafting.)
  - Three working groups, mixed (co-located + remote together):
    - **Group 1 (Platform)**: Marcus, Yuki, 2 engineers, 1 product person. "Design the platform roadmap. Q2 goal: [SCOPE]. What are the milestones?"
    - **Group 2 (Customer Features)**: Sales lead, 3 engineers, 1 designer. "What custom features ship Q2? Prioritize."
    - **Group 3 (Infrastructure / Hiring)**: Sarah, 2 ops people, 2 engineers. "What infrastructure do we need? How many hires?"
  - Each group has a shared Google Doc. Facilitator (Sarah) bounces between groups to resolve dependencies.
  - **5:00–5:30 PM**: All regroup. Each group presents their roadmap (5 min each). Identify conflicts or overlaps. Resolve.
  - Decision: "Here's Q2 roadmap. Here are the owners and dates. Everyone clear?"

**Evening: 5:30 PM onward** (casual dinner for those staying, optional). Berlin team logs off.

### Day 2: Tuesday, April 15

**Morning (8:30 AM – 12:30 PM Austin / 5:30 PM – 9:30 PM Berlin)**
- **8:30–9:00 AM**: Coffee, informal chat.
- **9:00–10:00 AM**: **Org Structure & Roles Discussion.** (Laptops down.)
  - With the platform decision, team structure is changing. Sarah presents the new structure: Platform team (5 people), Customer team (6 people), Ops/Infra (3 people).
  - Ask for input: "Does this make sense? Who's excited? Who has concerns?"
  - (Berlin people join on Zoom for this part.)
- **10:00–10:30 AM**: **Breakout: What I Need From You.** (Small groups, 10 min.) People pair up with cross-functional partners. "What do you need from me to do your job well?" Platform person + customer person, etc. Builds connection. Captures dependencies.
- **10:30–11:00 AM**: Regroup. Share key dependencies. Facilitator captures.
- **11:00 AM–12:00 PM**: **Future-State Whiteboarding.** (Laptops down.) "In Q3, what does the org look like? What's possible with the platform?" Blue-sky thinking. Not commitment, just exploration.
- **12:00–12:30 PM**: Recap and clarity. Sarah: "Here's what we decided. Here's what's changing. Here's what stays the same."

**Lunch: 12:30–1:30 PM**

**Afternoon (1:30 PM – 4:00 PM Austin / 10:30 PM – 1:00 AM Berlin)**
- **1:30–2:15 PM**: **Celebration.** Sarah reads aloud Q1 wins from team Slack.
  - "Marcus shipped the first iteration of the platform 2 weeks ahead of schedule."
  - "Yuki onboarded three new customers with zero issues; they're already expanding."
  - "The ops team implemented the new DevOps pipeline; we've cut deploy time 40%."
  - Each win: 1-min description, then the team applauds. (People feel seen.)
- **2:15–2:45 PM**: **Connection & Food.** Informal time. Some people play a game (optional). Some just hang out. Not mandatory.
- **2:45–3:30 PM**: **Leadership Closing.** Sarah + Marcus (new platform lead).
  - Sarah: "Here's what we decided. Platform is our bet. It's a 6-month bet. If it's working in Q3, we go all-in. If it's not, we revisit. You're not risking your career on this. You're risking a learning."
  - Marcus: "I'm honored to lead the platform team. Here's how I'm thinking about it. I'll be checking in weekly. I want your ideas. I'll be wrong sometimes; I'll learn from you."
  - Open Q&A: "Anything you need to ask?"
- **3:30–4:00 PM**: Optional walk or free time. End of offsite.

---

## How We're Handling Remote People (Berlin Team)

- **Everyone on video.** Even Austin people are on Zoom from their laptops; no "we're here, you're not" dynamic.
- **Shared Google Docs and Miro board.** All whiteboarding happens on screen so remote people see in real time.
- **Breakout groups:** Remote people in every group. If working on a specific topic, rotate so no one feels stuck in a single perspective.
- **Voting and decisions:** Use async methods (Google Form, anonymous Slack poll) so early speakers don't dominate. Remote people, introverts, and people processing time all get equal voice.
- **Time zones:** Day 1 afternoon (Austin 1:30 PM = Berlin 10:30 PM) is rough. We're explicit: Berlin team can take a break and rejoin for the recap, or go to bed and catch up on recordings. We're not asking them to stay up all night.

---

## Success Metrics

- [ ] Everyone can articulate the Q2 roadmap and the platform decision.
- [ ] No one is surprised by the decision (heard both sides, understands the trade-off).
- [ ] Action items are clear: Platform roadmap owner (Marcus). Customer feature owner (Yuki). Hiring owner (Sarah). Dates and milestones.
- [ ] Remote people (Berlin team) felt heard and included.
- [ ] At least one uncomfortable conversation happened (the platform vs. custom debate) and people feel resolved, not resentful.
- [ ] Team leaves energized, not drained. (Survey it.)

---

## Post-Offsite (Week of April 21)

- [ ] **Monday, April 21**: Sarah sends summary email with:
  - Decision: Platform investment, 6-month bet.
  - Q2 roadmap with owners and dates.
  - Org structure changes.
  - Link to all docs, recordings (for those who missed parts).
- [ ] Create action items in Linear with clear owners and deadlines.
- [ ] **Week of April 21**: Sarah does 1:1s with anyone who was quiet or remote. "How did the offsite feel? Do you have concerns I should know about?"
- [ ] **Friday, April 25**: Send feedback survey (Google Form). "What worked? What should we change next time?"
  - Example questions: "Did you feel heard?" "Was the offsite worth the time/cost?" "What one thing should we do differently next time?"

---

## Notes & Decisions Made

**Decision 1: Platform Investment**
- Rationale: Long-term scalability. Custom model hits ceiling at 20–30 customers; platform model scales to 100+.
- Trade-off: Q2 shipping slows. Some custom features delayed.
- Owner: Marcus. Timeline: 6 months to MVP. Re-evaluate in Q3.

**Decision 2: Org Structure**
- Three teams: Platform (5), Customer (6), Ops (3).
- New hire needed: Support role (1).
- Marcus reports to Sarah. Yuki reports to Sarah. Clear.

**Decision 3: Q2 Roadmap**
- Platform: Shared data layer (core). Feature flags. Component library (MVP).
- Customer: Three custom integrations. Onboarding improvements. Performance work.
- Infra: DevOps pipeline II. Monitoring upgrades.
- All dates and owners in Linear.

**Assumption**: Berlin team's input on the platform debate was equal. (Verified: Yuki and Marcus both felt heard, even though they argued different sides.)

**What to Watch**: Is platform timeline realistic? Are we losing custom work bandwidth? Check in Marcus + Sarah weekly in May.

Edge Cases

• Conflict is too deep to resolve in one offsite: You may not solve the core tension in 2 days. That's okay. Use the offsite to surface the conflict, ensure both sides are heard, make a decision, and commit. Follow-up 1:1s will help people process afterward.
• Remote people feel excluded even with Zoom setup: Sometimes the issue is power dynamics, not logistics. If quieter remote people stay quiet even with shared docs, assign them a specific role: "Yuki, you're the decision synthesizer. You tell us what you're hearing." Gives them voice.
• Offsite agenda is too packed; not enough white space: If you're scheduled every minute, people don't decompress. Plan for 20% downtime (breaks, meals, optional social). Overbooked offsites feel exhausting, not energizing.
• Travel is expensive or impossible for some people: Hybrid offsites (some remote, some in-person) reduce energy. Consider all-remote offsites (everyone on Zoom) or rotating location quarterly so the burden isn't always on one geography.
• After the offsite, decisions aren't actioned: An offsite is only valuable if decisions become action. Assign owners immediately. Create items in tracking system. Check in the week after. If action stalls, revisit why the decision wasn't real.
• Offsite surfaces new conflicts or resignations: Sometimes intense days together reveal problems people have been hiding. That's data. Don't be surprised if someone opens up in a 1:1 after the offsite saying "This role isn't for me." That's actually the offsite working.