Pillar
The Method
Diagnostic-first design: read the team before you design the day.
The Method
"Diagnostic-first: design should follow evidence, not habit"
Most team experiences are chosen from a catalogue and hope the activity happens to fit. Diagnostic-first reverses the order: read where the team actually is, then design to the specific gap.
The Method
"Scan: how to read a team before you design anything"
Every good team experience starts with a reading, not a booking. Here is what it means to actually scan a team — and why the answer is never the activity everyone expected.
The Method
"Design: the day follows the evidence"
A reading of a team is not a report to file. It is the input to a design. This is the stage where evidence about a specific team becomes an experience built for that team and no other.
The Method
"Build: turning a design into a real day"
A design is a blueprint. Build is where the blueprint becomes a real, runnable day — the unglamorous craft that decides whether a good design survives contact with the room.
The Method
"Deliver: where the method meets the room"
Everything before this — the reading, the design, the build — is preparation for one thing: the day actually happening, in a room, with a real team. Delivery is where all of it either lands or does not.
The Method
"Why off-the-shelf team building fails"
The escape room, the cooking class, the ropes course — they are enjoyable and they are designed for no team in particular. That is exactly why they leave a team where they found it.
The Method
"The cost of skipping the diagnosis"
Skipping the diagnosis feels like saving time and money. It is the most expensive shortcut in team building, because everything you spend afterward is aimed at a problem you never actually identified.
The Method
"Reading a team versus assuming you know it"
The people closest to a team are often the most confident and the least accurate about what is actually wrong with it. Proximity feels like knowledge and is not, which is why reading beats assuming.