Plan a Team Offsite Where Every Session Ends in a Clear Decision

You get a timed offsite agenda where each session has a named decision or output, plus facilitation questions, a short prework checklist and a two-week follow-up plan.

Prompt

Prompt
You are an experienced facilitator who designs team offsites and strategy days.

Your job: plan an offsite agenda where every session ends in a decision or concrete output, not open discussion.

Before planning, ask me these questions in one message, then wait for my answers:
1. Team size, roles, and who has final say on decisions?
2. Length of the offsite and start and end times?
3. The 2-4 topics or problems we must leave with answers on?
4. In person or remote, and any constraints (budget, travel, tension in the team)?

Rules:
- Each session names the exact decision or artifact it must produce, written as a finished sentence or document title.
- No working session runs over 90 minutes. Include a 15-minute break at least every 2 hours and a lunch of 45+ minutes.
- Give each session a method (silent writing, dot voting, pre-mortem) and 2-3 facilitation questions.
- Prework totals under 45 minutes per person, with owner and due date.
- Breaks, lunch and open buffer make up at least 20% of the day. End with a 30-minute session that assigns owners and dates.

Output format:
1. Offsite goal (one sentence)
2. Agenda table: Time | Session | Decision or output | Method | Lead
3. Facilitation questions per session
4. Prework checklist: Task | Owner | Due | Time needed
5. Follow-up plan for the first two weeks

End with one line naming the biggest risk to this plan and any missing information.

Example output

At a glanceOffsite day: sessions and the decision each producesOne in-person day, 9:00-17:00; breaks, lunch and buffer take 150 of 480 minutes (31%).
  1. Opening9:00-9:30"Today we decide X, Y, Z" posted on the wall
  2. Look back at Q39:30-10:45List of 3 things we stop doing
  3. Choose H1 bets11:00-12:15Ranked top 3 bets, Maya confirms
  4. Pre-mortem on bet #113:15-14:30Top 5 risks, each with an owner
  5. Release process14:45-15:45One-page "How we ship" agreement
  6. Commitments16:30-17:00Action list with owners and dates

Example for: a 9-person product team, one in-person day (9:00-17:00), deciding H1 priorities and fixing slow releases.

1. Offsite goal

Leave with three ranked H1 bets, owners for the top risks, and agreed team rules that cut release delays.

2. Agenda
TimeSessionDecision or outputMethodLead
9:00-9:30Opening"Today we decide X, Y, Z" posted on the wallRound-robin check-inMaya (Head of Product)
9:30-10:45Look back at Q3List of 3 things we stop doingSilent writing + groupingJonas
10:45-11:00Break
11:00-12:15Choose H1 betsRanked top 3 bets, Maya confirmsDot voting, 3 dots eachMaya
12:15-13:15Lunch (away from laptops)
13:15-14:30Pre-mortem on bet #1Top 5 risks, each with an ownerPre-mortemPriya
14:30-14:45Break
14:45-15:45Release processOne-page "How we ship" agreementFist-to-five voteDev (Eng Lead)
15:45-16:30Open bufferOverflow or free time
16:30-17:00CommitmentsAction list with owners and datesRead-backMaya

Breaks, lunch and buffer: 150 of 480 minutes (31%).

3. Facilitation questions
  • Look back: What did we spend time on that no customer noticed? What slowed us down more than once?
  • H1 bets: Which bet moves activation most? What would we drop to fund it?
  • Pre-mortem: It is June and bet #1 failed. What happened? Which warning sign would we see first?
  • Release process: Where does a ticket wait longest? What rule would we all actually follow?
4. Prework checklist
TaskOwnerDueTime needed
Share Q3 metrics one-pagerJonas5 days before30 min
Each person submits up to 2 bet ideasEveryone3 days before15 min
List the last 5 delayed releases and causeDev3 days before20 min
Book room, lunch, sticky notesPriya7 days before20 min
5. Two-week follow-up
  • Day 1: Maya sends decisions and action list.
  • Day 3: Bet owners draft one-page briefs.
  • Day 7: Risk owners give a 5-minute update in standup.
  • Day 14: 30-minute review: what moved, what is stuck.

Biggest risk: the H1 vote stalls if leadership has not shared budget limits; confirm headcount before the day.

Written by AI from this prompt. Your results will vary.

Tips and common edits

Why this works

  • Requiring a named decision per session stops the common offsite failure of long talks with nothing agreed.
  • Caps on session length and a minimum share of breaks keep the day realistic instead of crammed.
  • Timed prework and a two-week follow-up plan connect the day to real work before and after.

Use this 2-3 weeks before an offsite or strategy day. Have your team size, timing and must-decide topics ready. Works in ChatGPT, Claude or Gemini; answer the four questions in one reply.

Common edits

  • Ask for a two-day version with a team dinner and a lighter second afternoon.
  • Adapt it for a remote offsite with shorter 60-minute sessions and online tools like Miro.

Prompt details

By
Prompts-GPT editors
Published

Did this prompt work?

Keep exploring

More in Business