Build a Bike, Give It Away

Teams assemble children's bicycles from flat-packed parts, usually with some competitive element, and the finished bikes go to a local charity, school or shelter. The single most reliable large-group activity there is, because the output is real and leaves the room on a child's bike.

What it is good for

• CollaborationWorking a shared problem where no one person holds all the information.
• CommunicationPractising clear hand-offs, active listening and saying the hard thing early.
• WellbeingGiving the team a genuine break rather than another meeting with a theme.
• RecognitionMaking good work visible to people other than the manager.

What you need

• Flat-packed children's bicycles, one per team of four to six
• Basic tool kits
• A local charity partner who will take them

The run sheet

1. Find the recipient first (prep)

   Confirm the charity, the number of bikes, the sizes they need and the handover date before you order anything. A pile of bikes nobody can accept is a worse outcome than no activity at all.

2. Stagger the parts (prep)

   Deliberately distribute parts unevenly between teams so they have to negotiate and trade. This is what turns assembly into a team activity rather than parallel solo work.

3. Teams and roles (15 min)

   Four to six per bike. Ask each team to assign a parts manager, a quality checker and a build lead. Rotate the build lead halfway through.

4. Build (90 min)

   Run challenges between stages — a quick quiz, a relay — that earn missing parts or tool access. Keep music on.

5. Safety check, properly (20 min)

   Every bike checked by someone competent: brakes, headset, wheel nuts, pedal direction. This is non-negotiable and should be done by a person who knows bicycles, not the teams themselves.

6. The handover (15 min)

   The recipients arrive. Nobody is told in advance. This is the part people remember for years, and it does not need any facilitation at all — stand back.

Facilitator notes

• The surprise handover is the whole emotional architecture of the activity. Protect it; one leaked detail flattens it.
• Budget time for the safety check honestly. Rushing it is the one way this activity can do actual harm.
• If bikes are too much, the same structure works with wheelchairs, scooters, school supply packs or bunk beds for a shelter.

Debrief questions

Ask these immediately afterwards, not next week. Fifteen minutes of these is what turns the activity into something the team refers back to — see the debrief guide.

1. What did your team do when you discovered you were missing a part?
2. Who on your team turned out to be good at something you did not expect?
3. What would we do differently if we built twice as many?

Variations