← Catalog
skill Business

Team Building Plan

team-building-plan

Plans team building activities and events with objectives, activity options, budget considerations, logistics, and follow-up evaluation. Use when organizing team bonding, offsites, or morale-boosting events.

Add this skill
  1. This skill, packaged and ready to upload. team-building-plan.zip
  2. In claude.ai or Claude desktop: Customize → Skills (+) → Create skill → Upload a skill, select the zip and toggle it on. Greyed out? Enable code execution under Settings → Capabilities.
  3. It’s live in your chats — no code, no setup. Want every Business skill at once? Add the whole plugin from the Business page (Customize → Personal plugins → Create plugin → Upload plugin).

When to Use This Skill

Use this skill when you need to:

  • Plan a team building event, offsite, or bonding activity
  • Design recurring team culture activities on a budget
  • Organize a morale-boosting event after a tough quarter or major project
  • Structure a new-team kickoff with icebreakers and collaboration exercises

DO NOT use this skill for individual performance coaching, HR conflict resolution, or formal training programs. This is for team bonding and culture-building events only.


Core Principle

EVERY TEAM BUILDING ACTIVITY MUST HAVE A CLEAR OBJECTIVE TIED TO A REAL TEAM NEED — NOT JUST "FUN FOR FUN'S SAKE."


Phase 1: Brief

Gather the inputs that shape the event plan. No brief, no plan.

Required Inputs

Ask the user for each. Use the default if not provided.

Input What to Ask Default
Team size "How many people will participate?" 5-10 people
Objective "What team challenge are you solving? (trust, communication, onboarding, morale)" General morale boost
Budget "What's your total budget for this event?" $500
Format "In-person, virtual, or hybrid?" In-person
Duration "Half day, full day, or recurring series?" Half day (3-4 hours)
Constraints "Any physical limitations, dietary needs, or scheduling restrictions?" None

Present the brief summary and wait for confirmation before proceeding.

GATE: Do not proceed until the user confirms the brief.


Phase 2: Plan

Design the event structure with 2-3 activity options per time block.

Plan Structure

  1. Event overview — date/time framework, venue type, theme
  2. Agenda with time blocks — each block has a primary activity and one alternative
  3. Activity descriptions — what it is, why it works for the stated objective, group size requirements
  4. Budget breakdown — venue, supplies, food/drink, contingency (10%)
  5. Logistics checklist — what to book, buy, prepare, and communicate in advance

Activity Selection Rules

  • Match activities to the stated objective (trust-building needs vulnerability; communication needs collaboration tasks)
  • Include at least one low-energy option for introverts
  • Never suggest activities that require specific physical ability unless confirmed with user
  • Budget-friendly alternatives for every premium suggestion

GATE: Present the plan and wait for approval before creating final deliverables.


Phase 3: Execute

Build the complete event package.

Deliverables

1. Run-of-Show Document

  • Minute-by-minute agenda with responsible person for each segment
  • Setup and teardown time included
  • Transition notes between activities

2. Communication Templates

  • Invitation message with date, time, location, what to bring
  • Reminder message (send 2 days before)
  • Post-event thank you message

3. Supply and Vendor List

  • Every item needed with estimated cost and where to source it
  • Vendor contact info placeholders for bookings

4. Facilitator Notes

  • Talking points for each activity
  • How to handle low energy or disengagement
  • Backup activities if something falls flat

Phase 4: Polish

Follow-Up Evaluation

Create a short post-event feedback form (5 questions max):

  • Rate overall enjoyment (1-5)
  • What was your favorite activity and why?
  • What would you change?
  • Do you feel closer to your teammates? (1-5)
  • Suggestions for next time?

ROI Summary Template

Provide a one-page template connecting the event back to the original objective with observable behavior changes to watch for over the next 30 days.


Example 1: Remote Team Quarterly Bonding (Virtual, $200 budget, 8 people)

Agenda:

  • 0:00-0:15 — Icebreaker: Two Truths and a Lie (builds personal connection)
  • 0:15-0:45 — Virtual Escape Room via free platform (collaboration under pressure)
  • 0:45-1:00 — Break + snack delivery (send $15 DoorDash gift cards)
  • 1:00-1:30 — Show and Tell: everyone shares something from their workspace
  • 1:30-1:45 — Shoutouts round + wrap-up

Example 2: In-Person New Team Kickoff (Full day, $1,500 budget, 12 people)

Agenda:

  • 9:00-9:30 — Breakfast + name-game icebreaker
  • 9:30-11:00 — Team charter workshop (define norms, communication preferences)
  • 11:00-12:00 — Collaborative problem-solving challenge
  • 12:00-1:00 — Catered lunch
  • 1:00-2:30 — Strengths mapping exercise (each person shares their superpower)
  • 2:30-3:00 — Wrap-up and 30-day action commitments

Anti-Patterns

  • Activity without objective — laser tag is fun but does not solve a communication problem. Always tie activities to the stated need.
  • Forcing extrovert energy — karaoke and improv alienate half the team. Include low-key options.
  • Skipping the budget — planning a $5,000 offsite when the budget is $500 wastes everyone's time.
  • No follow-up — an event without follow-up is a party, not team building. Always include evaluation.
  • Mandatory fun tone — frame events as opportunities, not obligations.

Recovery

  • No budget: Suggest zero-cost activities (potluck, park meetup, virtual game night using free tools).
  • Team spread across time zones: Recommend asynchronous activities (shared playlist, photo challenge, async Q&A) plus one overlapping-hours live session.
  • User unsure of objective: Ask "What's the biggest friction on your team right now?" and map that to an objective.
  • Past events flopped: Ask what went wrong. Usually it is forced participation or mismatched energy levels. Adjust accordingly.

View source on GitHub →