communication · teams · offline
Paper Tower.folder
Twenty sheets, one meter of tape, twelve minutes — the tallest tower that survives the book test wins. The build is short; what they say while building is the lesson.
// kit v2: a stage-ready HTML deck (presenter drawer, run-of-show timer, built-in QR codes) · poker-spec print-and-cut cards with backs and blanks · an A3 activity poster · manuals in A4 and US Letter with bookmarks · three license tiers (CC BY free / single event / organization).
The classic paper-tower challenge, rebuilt as a complete workshop folder: a minute-by-minute run sheet, printable builder and judge cards, and a pre/post measure that shows each team how its planning, information flow and recovery actually behaved — not just how tall the tower stood.
The props are poker-spec print cards (63.5 × 88.9 mm, bleed and cut guides included) — builder, judge, timing — sized so one sheet covers a team. Nothing needs a projector, nothing needs an account, and the paper for the towers comes from any recycling bin.
the run sheet
// this is the guide file, word for word — read it here, run from it here. the .md at the bottom of the page is the same text, offline.
Folder:
paper-tower· Category: communication · 3–5 per team · 30 min · offline · print props · assessment-typeLicense: CC BY 4.0
Teams get twenty sheets of paper and one meter of tape. Twelve minutes later, the tallest tower that holds a book for ten seconds wins. The build is loud and fun — and it quietly records how the team plans, shares information and recovers when things lean.
Objectives
By the end of the activity, participants will have:
- Watched their team's planning behavior under time pressure — who talks, who builds, who is silent.
- Experienced the trade between height and stability — the same trade their projects make weekly.
- Practiced one recovery move: stop, diagnose, change one thing — when the tower starts to lean.
Setup
Space: one table per team, two meters between tables (towers need judging room).
Materials per team:
| Item | Source |
|---|---|
| 20 × A4 sheets | any recycling bin — used paper is fine |
| 1 m × masking tape | one strip, pre-cut, on the table |
| 1 × builder card | paper-tower-prop-cards.pdf (card 1) |
| 1 × judge card | paper-tower-prop-cards.pdf (card 2) |
| 1 × timing card | paper-tower-prop-cards.pdf (card 3) — for you |
Forbidden: scissors, rulers, extra tape, phone towers. Hands only. Paper may be torn, folded, rolled, crushed — not cut.
Grouping rule: teams of 3–5. Mix departments if the group allows — the debrief question "what did you assume about your teammates?" only works across silos.
Minute-by-minute script
| Time | Phase | Facilitator does | Participants do |
|---|---|---|---|
| 0–2 | Frame | "Twenty sheets, one meter of tape, twelve minutes of building. The tallest tower that holds this book for ten seconds wins. No scissors — hands only." | Take cards, form teams |
| 2–5 | Silent planning | "For three minutes: plan on paper. No building, no tape." | Teams sketch and argue on paper |
| 5–17 | Build (12 min) | Float. At minute 10 announce: "two minutes left." Do not help with structure | Build, test, tear down, rebuild |
| 17–20 | The book test | Each team places the book on top, counts to ten out loud. Judge card scores each tower | Watch other towers fail or hold |
| 20–23 | Self-score | "Score your own team on the judge card — including the arguments." | Teams self-score honestly |
| 23–30 | Bridge to debrief | "Keep the towers standing until after the debrief — they are the data." | Towers stay up |
Then run the debrief — see paper-tower-debrief.md.
Known failure modes & rescues
- One engineer, four spectators. The loudest builder takes over; others hold tape. Rescue: at minute 8, freeze the room: "hands off — everyone names one thing the tower needs next." Then build resumes.
- The team builds a column and hopes. No folding, no triangles — a rolled sheet stands alone. Rescue: none needed. The collapse is the debrief's best exhibit. Restart is allowed inside the 12 minutes.
- Silent planning was skipped. Someone starts rolling paper at minute three. Rescue: enforce it gently — "planning is a round too." The contrast between planned and un-planned towers is the lesson.
Variations
- Mid-build rule change: at minute 10, announce the book test for the first time. Teams that over-invested in height now scramble for stability — exactly like a requirement change.
- Online: teams build at home with identical kits (10 sheets + 1 m tape, mailed or self-supplied); measuring happens on camera with a household book.
- Assessment-type: run the pre-measure before teams form, and the post-measure right after the debrief — see
paper-tower-assessment.json. The interesting number is the delta, not the score.
the debrief sheet
// the debrief questions, in full — the .md version prints on one page for the room.
8 questions, 3 failure modes, one rule: the tower is the transcript.
Use with
paper-tower-guide.md. Debrief runs 10–15 min after the book test.
How to run this debrief
- Keep every tower standing through the whole debrief. Point at them, don't describe them.
- Ask questions to one team first, then to the room. Start with the shortest tower that survived the book, or the tallest one that didn't.
- Write answers on this sheet or on the back of the judge card — teams keep them.
The 8 questions
1. The plan on paper.
"What did your team plan in the silent three minutes — and what actually survived contact with the tape?"
→ Targets: planning vs. improvising. Most teams abandon the sketch by minute seven.
2. Hands and voices.
"Whose hands were on the tower, and whose voices were around the table? Were they the same people?"
→ Targets: participation structure. The tape-holder who never spoke is the finding.
3. The lean.
"When the tower started to lean, what did your team do first — diagnose, or build faster?"
→ Targets: recovery behavior. "Build faster" under pressure is the daily default.
4. Height vs. the book.
"Your tower chose height or stability before you knew the book was coming. Where does your team make that same bet on real projects?"
→ Transfer question. Expect: features vs. tests, launch scope, tech debt.
5. The one change.
"If you could restart with one change — materials, roles, or plan — which single change would you make?"
→ Commitment question. Make it singular — one change survives Monday.
6. The silent teammate.
"To the quietest builder: what did you see that the team didn't ask about?"
→ Perspective question. Ask this gently; it usually surfaces the best observation in the room.
7. The other towers.
"Which other team's tower taught you something? What was it?"
→ Cross-team learning. Breaks the silo the grouping rule built on purpose.
8. The daily version.
"Where in your actual week does your team build 'as tall as possible, as fast as possible' — and where is your book test?"
→ Closing question. It ends the debrief on their own deadlines, not on paper.
3 known failure modes of the debrief itself
- The collapse becomes comedy. A dramatic collapse gets laughs; the room wants the blooper reel.
Rescue: laugh once, then stand next to the fallen tower and ask question 3. The wreckage is the exhibit.
- Blame lands on the builder. "If only Alex had folded the base…"
Rescue: reframe — "the tower is 20 sheets of evidence about a team, not a person." Question 2 is the pivot.
- Winners disengage. The winning team thinks the debrief is for the losers.
Rescue: ask them question 7 first. Winners analyzing other towers is the strongest close.
If you are running the pre/post measure (paper-tower-assessment.json), note these observables during the build — they justify the delta in the report:
| Observable | Points to |
|---|---|
| Team sketches before touching tape | Shared planning habit |
| Roles named out loud in minute one | Role clarity |
| A silent member's idea gets built | Information flow |
| After a collapse: pause, then a changed approach | Recovery from failure |
The report your participants receive is a self-comparison, never a team ranking — keep it that way when you present it.
who it's for · what it leaves behind
Who is the Paper Tower activity for?
Trainers and team leads who need a collaboration exercise with visible evidence: the towers stay standing, so the debrief can point at them. It works for cross-department offsites, project kickoffs and any team that argues about scope — the height-versus-stability trade mirrors real project decisions.
What results does it produce?
Three things stay after the session: the towers themselves — visible evidence of each team's build strategy — the judge-card scores including how the team rated its own arguments, and a pre/post team-level delta from the assessment preset. It measures working habits, not engineering talent.
Can my AI agent use this folder?
Yes. Every folder ships a SKILL.md skill file: frontmatter for matching, plus runnable prep commands — fetch the props, pull the debrief, build the live pre/post measure with formlm-cli. The three-step workflow (discover, install, run) lives on the skills page, every folder ships a one-command zip bundle, and the machine index is skills.json.
Is it really free?
Yes — CC BY 4.0, no account, no email wall inside a folder. Download it, run it, copy it, rebrand it for your own workshop. Attribution keeps everything free.
make it live
The folder's paper pre/post measure is built for rooms with nothing but markers. If you want the digital version — the same 6 items as a live form, each participant's before/after delta computed automatically — two ways:
for AI agents
$ formlm-cli smart generate --input "Pre/post measure for the Paper Tower team challenge: 6 Likert items on shared planning, role clarity, information flow and recovery from failure — the same 6 items before and after the activity, so each participant's delta is computed automatically"
Step 4 of the agent workflow: npm install -g @formlm/cli, log in once, and the prep above runs itself. The form and its data live in your own workspace.
— or, with a mouse —
Open the free pre/post training quiz template on FormLM
and paste the 6 items from paper-tower-assessment.json — the template already runs the before/after comparison and scores it.
// optional, not required — the paper version in this folder is complete on its own. free account on their side.
put it on the wall
The folder ships a single-file HTML deck that presents full-screen from one laptop. To run the activity on the room's big screen — submissions land on the wall in real time, the countdown and the spotlight stay in your hands, and the whole room joins with one scan — the scan-and-project companion is QRCard-AI:
See the trainer live-screen mode on QRCard-AI — one QR code on the wall, participants join and follow from their own seats.
// optional, not required — the deck in this folder already runs full-screen on a single laptop.
take this folder with you
// every file downloads as a plain file. no account, no email wall inside a folder.