The short version: I put your managers somewhere they have to lead for real, under pressure, tangled up with each other. Then I show them what they actually did, which is usually not what they think they did. Then we turn that gap into commitments they carry back to the job.

It works because leadership is a set of behaviours and not a body of knowledge. And behaviour only shifts by doing, being told the truth about it, and doing it again.

This page is the hub. Six competencies, the game behind each one, and how I run and measure a programme.

Facilitated tabletop role-playing session with an engaged group of players

Key takeaways

IdeaWhat it meansWhy it matters
Leadership is behaviourIt is what you do under pressure, not what you knowYou cannot lecture a behaviour into someone
Practice beats contentPeople change by doing, then being shown what they didLearning survives past the workshop
The debrief is the productThe game surfaces behaviour, the debrief converts itNo debrief, no change
Start from the behaviourPick the game after you name the target behaviourDesign serves the outcome, not the reverse
Measure what changesTrack observable commitments, not smile sheetsBehaviour change is the only real result

Why most leadership training slides straight off

Here's the uncomfortable thing about my own industry. Most leadership training transfers knowledge to people who already have it.

A room of managers hears a genuinely good explanation of delegation. They nod. They ask decent questions. Then they go back and delegate exactly the way they always did. The content was fine. The format was the problem.

You cannot lecture a behaviour into existence. Same as you cannot teach anyone to swim with a slideshow.

Leadership is not knowledge. It is a set of behaviours that either show up under pressure or don't. Nobody has ever frozen on a decision because they hadn't heard of reversible versus irreversible calls. They froze because in the moment, with something real on the table, the old habit fired faster than the new idea.

So you have to reach the person where the habit actually lives. Under stakes, with feedback arriving fast enough to matter. That is the whole job.

How I actually build the behaviour

It is a loop, and I keep it deliberately simple.

Put people into a designed experience that forces the target behaviour to show up. Let them lead it for real, with pressure and consequences, so they act on instinct instead of performing the answer they think the facilitator wants. Then debrief hard. Mirror up. What you did, versus what you believe you did. Turn that gap into something specific they carry out of the room.

The game is never the point. It exists to make behaviour visible in front of peers, which a normal workday will never do for you.

The debrief is where development actually happens. Which is exactly why a weak experiential programme runs a fun activity and quietly skips the hard conversation afterwards. Everyone leaves happy and nothing changes.

This is the core of the Put The Player First framework. Your people's real behaviour is the curriculum. Everything else is scaffolding for getting at it. It is also why this is a different thing from classroom training rather than a livelier version of it.

The six competencies I build - start with the one that names your real problem

Almost every challenge a client brings me boils down to one or two behaviours under pressure. Here are the six I train most, each with a page of its own and a game built to stress it. Start with whichever one names the problem you actually have, not the one that sounds best in a board update.

Decision making under uncertainty

How your managers learn to decide well on incomplete information - process over outcome, reversible versus irreversible calls, and when to stop analysing and just move. Built with Chaos in the Kitchen.

Cross-functional collaboration

Getting teams that do not report to each other to move as one - and killing the silos that quietly wreck delivery while every dashboard still shows green. Built with Ripple Effect.

Influence and stakeholder management

How to lead without authority - reading stakeholders, building coalitions, and getting to yes when you cannot simply give the order. Built with Bloom.

Team communication

Making sure the right thing gets said, heard and acted on - and pulling disagreement into the room instead of leaving it to fester in the corridor. Built with Sticky Fingers.

Leading change

How a leader carries a team through uncertainty and resistance when the ground is moving and nobody has the full map. Built with Planetfall.

Negotiation and workplace politics

Navigating competing interests, trading well, and handling the politics of getting things done - without turning either naive or cynical. Built across the game portfolio.

A related competency, structured problem solving for teams, sits alongside these when the issue is how a group thinks together rather than how one leader behaves.

The games behind the programs

Each competency gets the game that forces exactly that behaviour into the open. The games are the how, never the headline. Nobody buys a game. They buy managers who decide faster, or influence better, or hold a team together through a mess. The game is just the instrument.

Chaos in the Kitchen runs a kitchen under genuine time and resource pressure, forcing triage, optionality and owning calls made on incomplete data. Ripple Effect makes interdependence visible so cross-functional trade-offs stop being abstract. Bloom puts influence and stakeholder reading under the microscope. Sticky Fingers stresses communication and coordination. Planetfall drops a crew into an unknown world where they must lead change and act on sparse information. If none fits your problem cleanly, I build one - see custom serious game design. The full landscape is laid out in the serious games for leadership development guide.

How I design and run a program - backwards from the behaviour

Every programme gets built backwards from the behaviour you want changed. Never forwards from a game I happen to enjoy running. Same five steps, every time:

I run these for first-time managers learning the fundamentals, for experienced managers unlearning habits that stopped serving them years ago, and for executive teams who already know all the theory and just need somebody to hold up the mirror.

And here's the counter-intuitive bit. The more senior the room, the better this works. Content has almost nothing to offer people who have heard it all. The mirror has everything.

Team deeply engaged in a tabletop workshop game around a wooden table

How I measure whether anything actually changed

The honest measure is not how the room felt at 5pm. Satisfaction scores tell you the day went well. They tell you nothing about whether one single person leads differently on Monday.

Because every programme starts from a named behaviour, it can end with named, observable commitments. Then those get checked over the following weeks, with the manager and with their team.

Did the reversible decisions actually get faster? Did the disagreement move into the room? Simple questions. Slightly terrifying ones. And the only results worth paying for.

Which is why this holds up on exactly the terms classroom training struggles with. What people do, not what they scored.

Get my facilitation and program playbooks by email

One short email whenever I have something you can actually use. A new game, a debrief move that worked, an honest look at a real session. No schedule, no filler.

Leadership playbooks, by email

New serious games, facilitation techniques, and session notes. No spam.

    Unsubscribe any time.

    Straight answers

    Basics

    What is experiential leadership development?
    Building leadership by doing it rather than hearing about it. Your managers go into a designed situation where they have to lead under pressure, and then we look honestly at what they did. Leadership is behaviour, and behaviour is learned by doing, getting told the truth, and doing it again.

    How is it different from a classroom workshop?
    A classroom transfers knowledge. This changes behaviour. The models still turn up, but in the debrief, attached to something the person in front of you actually did forty minutes ago.

    Scope

    What can it build?
    Deciding under uncertainty. Cross-functional collaboration. Influence and stakeholder management. Team communication. Leading change. Negotiation. All six are behaviours that only surface under pressure, which is exactly what a game creates and a debrief makes coachable.

    Does it work for executives?
    Yes, and better than it works anywhere else. Senior leaders already know the theory, so lecture bores them. An experience shows them their own habits in front of their peers, which is feedback almost nobody at that level gets any more.

    Delivery

    How is a programme structured?
    Start from the behaviour you want changed. Pick the game that stresses it. Run it for real. Debrief hard into commitments. That can be one intensive day or a sequence across several competencies, spaced so people go and try it at work in between.

    Can behaviour change actually be measured?
    Yes, by tracking observable commitments rather than satisfaction scores. The debrief produces specific ones - deciding reversible calls inside a day, for instance - and those get checked with the manager and the team over the following weeks.

    Related reading

    Design a programme with me Write to me

    With love from Bengaluru, this is Arvindh saying over and out.