Team offsite opening deck with goals, agenda and ground rules
Builds the opening slides for a one or two day team offsite: why the team is there, the three decisions the offsite must reach, the agenda by session, ground rules and how the output will be used afterwards, with speaker notes for the person opening. Use it when an offsite risks turning into a holiday with a few talks instead of a working session.
The output this prompt produced, unedited.
The prompt
Fill in these first
Team and size: [e.g. a 22-person product and engineering team]
Dates, place and length: [e.g. two days at a resort near Lonavala]
Why now: [e.g. a new year plan, a reorganisation, a missed target]
Decisions the offsite must reach: [list two to four]
Sessions already planned: [paste titles, owners and lengths, or none]
Person opening the offsite and their role: [e.g. head of product]
Slides to produce
Title: the offsite name and one line on what the team leaves with.
Why we are here: the situation in three short points, taken from the inputs.
What we must decide: each decision as a question, with who owns the final call.
Agenda: | Day | Time | Session | Owner | Output of the session |
How we will work: five ground rules, such as laptops closed in sessions and one conversation at a time.
Parking lot: how off-topic issues are captured and when they are handled.
After the offsite: what gets written up, by whom, and the date it is shared.
First exercise: a ten-minute warm-up that feeds the first decision, not an icebreaker game.
For each slide
A headline under ten words that states the point.
No more than four short lines of slide text.
Speaker notes of 60 to 100 words in a plain spoken voice.
Guardrails
If no decision is given, ask for one before writing the deck; an offsite with no decision has no agenda.
Keep every session in the agenda tied to one of the decisions, and flag any that is not.
Copy the prompt and paste it into Gemini, then set the aspect ratio to 3:4. No reference photo is needed for this one.
The prompt is written in Markdown with each part under its own heading, which is what the copy action hands over. Change one section at a time, keeping the rest intact, so you can tell which change did the work.