Retreat format
Team Hackathon
A retreat format in which teams build real work in short cycles, with a review from the whole room after each one.
- Length
- One to two days
- Group
- About forty people, in three teams
- Rhythm
- 90-minute build cycles
- Each team
- A one-page charter
- Ends with
- Task forces and a 90-day plan
What is a Team Hackathon?
A Team Hackathon is a retreat format in which teams self-organize around priority work streams and build usable work in short cycles.
Each team writes a one-page charter, then works through build cycles. Every cycle ends with a review from the whole room and a short retro, so the next cycle starts with what the team just learned.
FUSE facilitators use it when a retreat has to end with usable work on complex themes.
Ten things, half done
One small thing, finished
Before the first cycle
How the teams and their charters form
The sponsor frames the strategy
The leader sets out the priority work streams and the outcome expected from each one.
People choose a work stream
They self-organize toward the theme they care about most, in four-minute rounds, and adjust until every team has a balance of perspectives.
Each team writes its charter
Thirty minutes, one page. The charter says what the team will deliver by the end of the retreat.
Project charter
- Team name
- Team members
- Team lead
- Deliverable goal, by the end of the retreat
- Definition of done
Working agreements
- What does staying focused look like for us in the next few hours?
- When we disagree today, how will we handle it?
- How will we make sure all voices are included?
- What will we do if we get stuck or go in circles?
The rhythm
One turn of the wheel
Plan 10 minutes
A short retro on the last cycle, then a goal for this one.
Build 45 minutes
Work toward a small, finished piece of the outcome.
Review 35 minutes
A showing to the whole room, with feedback collected on sticky notes.
The timebox ends each phase. Whatever a team has when the time is up is good enough to carry into the next one.
A two-day agenda
Four turns, one piece
Every cycle produces a usable increment of the outcome. The room’s feedback shapes what the team does with the next turn.
Day one, afternoon
A first rough form
Each group shares what it has and receives feedback from the other groups.
Day two, first thing
The shape comes up
The review can run as a gallery walk, so people read each team’s work at their own pace.
Day two, late morning
The detail goes in
We ask the room which kind of review has worked better, and use that one.
Day two, after lunch
The finished piece
Each team presents its final work and its action plan for after the retreat.
The last afternoon
What the retreat ends with
A results wall fills up through the retreat, one column for each work stream. After the last review, the whole group forms task forces and each one writes a plan for the months that follow.
- Who is on the task force
- Who else needs to be reached
- Goals for the year
- A 90-day plan
- The data we need
- When the task force reports back
About forty surgeons, section leads and operational staff at a department’s annual retreat worked in three teams over two days.
Questions we often hear
How long is a Team Hackathon?
A Team Hackathon runs for one to two days. Each build cycle takes 90 minutes, and the number of cycles depends on the time available.
How are the teams formed?
People choose the work stream they care about most. We run a few short rounds, and the room adjusts until each team has a balance of perspectives and the capacity to deliver.
Is this a software event?
The name describes the rhythm: build, get feedback, learn. Teams produce principles, plans and decisions, mostly on paper and flip charts.
Why work in cycles?
The themes are complex: they involve trade-offs, different perspectives and an environment that keeps changing. Short cycles give each team feedback while there is still time to use it.
What happens to the work afterward?
The group forms task forces before it leaves. Each one has named members, goals for the year, a 90-day plan and a date to report back to the larger group.
End your retreat with work your teams can use
Tell us about your group and the themes it needs to move forward. We’ll design the retreat with you.
Book a discovery call