Index
All insights
Everything we have written, newest first.
The Human Layer & AI
"What AI changes about team work — and what it can't"
The question has moved from whether AI takes jobs to how work changes. As tools absorb the task layer, the human layer decides outcomes — and that is exactly the layer most teams have never measured.
The Human Layer & AI
"As AI absorbs task-work, the human layer becomes the differentiator"
When every organisation runs on similar tools, the tools stop being the edge. What separates one company from another is the quality of its human layer — and whether it can prove that layer is getting stronger.
Measurement & Proof
Why measurement changes the team-investment conversation
Most team building is bought as a day out and judged by whether people enjoyed it. Measurement turns it into an investment with a before and an after — which is the only version that survives a budget review.
Measurement & Proof
"What a Day 14 / 30 / 60 follow-up actually tells you"
Measuring only on the day captures mood, not change. Reading a team again at fourteen, thirty and sixty days separates the improvement that stuck from the glow that faded — and tells a leader what to reinforce.
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.
Industries
"GCCs: one company, two continents, one team"
A global capability centre is one company operating across two continents at once. That is its strength and its hardest problem — and it is exactly the seam where team health is won or lost.
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.
Roles & Decisions
"For the HR leader: proving the ROI of culture spend"
People leaders are asked to justify culture spend in a language the finance team respects, with tools that were never built to speak it. Here is how to close that gap without pretending team health is a spreadsheet.
Moments That Matter
"Onboarding at scale: making new hires belong faster"
Most onboarding teaches people how the company works and forgets to make them feel part of it. The second one is what decides whether they stay — and it is the one that gets skipped at scale.
Team Health
The eight dimensions of a healthy team
"Healthy team" is a phrase everyone uses and few can define. We read a team across eight specific dimensions, because a vague word cannot be improved and a specific one can.
Team Health
"The communication a team actually runs on"
Most teams think they have a communication problem and respond with more talking. The real question is narrower: does the true signal reach the person who needs it, in time to act on it.
Functions & Units
"Sales teams: high energy, high churn, and what they actually need"
Sales teams get the loudest events and the least genuine connection. The energy is easy to manufacture and quick to fade. What holds a sales team together is quieter, and almost never on the agenda.
Team Health
"Alignment is not agreement"
Teams that agree in the room still pull apart in practice. Alignment is not everyone nodding — it is everyone actually pointed the same way once the meeting ends and no one is watching.
Team Health
"Trust inside a team: the dimension everything rests on"
Trust is the quietest of the eight dimensions and the one the other seven depend on. It is also the one that cannot be built with a speech — only with how a team handles being wrong.
Moments That Matter
"Post-merger: two cultures, one team"
A merger is legal on day one and cultural for a long time after. The org chart combines two companies instantly. The people take much longer, and that gap is where most deals quietly underdeliver.
Roles & Decisions
"For the CXO: the retention math nobody puts on a slide"
The cost of losing good people is one of the largest numbers in a company and one of the least examined. It rarely appears on a slide, because the thing that drives it is treated as unmeasurable. It is not.
Team Health
"Collaboration is built, not assumed"
Sharing a goal does not make a group collaborate. People can work on the same thing and never actually work together — and the difference is where a team's real output is won or lost.
Functions & Units
"The leadership team sets every other team's weather"
The executive team is a team too — usually the least examined one in the company. Its health cascades. When the team at the top does not trust or align, every team below inherits it.
Team Health
"How teams actually decide"
A team's ability to move from a question to a committed choice is a distinct capability — and one of the quietest determinants of how fast and how well it executes. Most teams decide worse than they think.
Industries
"Technology teams: talent that can leave, work that needs safety"
Software teams combine two hard conditions: people who can leave easily, and work that only goes well when it is safe to be honest. The teams that hold both are the ones that ship and stay.
Team Health
"Energy: the dimension everyone feels and no one names"
A depleted team executes worse than a fresh one of the same skill. Energy is a team property, not just an individual mood — and running on empty is a performance problem, not a morale footnote.
Occasions
"Marking holidays inclusively: the value under the festival"
Companies get holidays wrong two ways — ignoring them, or celebrating some and not others. The way through is to mark the human value under each occasion, not the belief, so everyone is included and no one is made to feel default.
Team Health
"Belonging: the quiet dimension that holds people"
People can be present, productive, and quietly on their way out. Belonging is whether they feel genuinely part of the team — and it predicts who stays and who contributes more reliably than almost anything you can measure.
Occasions
"Employee appreciation, done so it actually lands"
Most appreciation is generic, and generic appreciation reads as an obligation met, not a thing felt. What lands is specific, from someone who matters, for something that mattered — and it is a belonging act, not a budget line.
Team Health
"Leadership, read as a dimension of the team"
Leadership is not only something a person is. It is something a team has — the direction, the conditions, and the climate that either let the other seven dimensions form or quietly prevent them.
Behind the Work
"What we look for in a facilitator"
The facilitator is the variable that decides whether a well-designed experience actually works. We hire for craft over credentials — the ability to read a room, hold a group, and get out of the way at the right moment.
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.