Everyone starts with a garden. The goal is simple: grow the most flowers and win.

What players discover — usually too late — is that the fastest way to a thriving garden isn't protecting it. It's investing in others.

What the Game Is

Bloom is a resource management and networking simulation. Players tend gardens, acquire new plants, buy upgrades, and compete to harvest the most flowers. On the surface, it looks like a straightforward competitive game.

Underneath, it's a live experiment in how resource-sharing compounds over time. Players who protect their resources aggressively and refuse to invest in others consistently fall behind those who build relationships and share strategically. The debrief reveals the garden as a precise metaphor for stakeholder management and professional networking.

What Happens in the Room

The first two rounds feel individual. Players are focused on their own garden — planting, upgrading, counting. The game looks like a solo puzzle. Then the compounding mechanic kicks in.

By round 4 or 5, one or two players have figured out that investing in someone else's garden returns more than spending the same resources on their own. Their gardens start pulling ahead. Other players notice, but most assume it's luck or better starting cards. They keep protecting what they have.

By round 6, the players who hoarded in the early rounds are calculating and realising they can't catch up. Some pivot — but it's late, and the relationships they'd need aren't there because they didn't build them earlier. By round 7, there's usually one player who tried to win entirely alone. They played a clean, efficient, solitary game — and ended up near the bottom. The debrief uses that player's story, anonymised, to show exactly what transactional thinking costs.

What It Reveals

Bloom surfaces how people think about relationships when something valuable is at stake.

• Who approaches others with an offer first versus who waits to be asked — and how long they wait before giving up and going solo.
• The player who only trades equal-for-equal, every time, with everyone. Technically fair. Strategically limiting — because the best returns come from asymmetric investments where you give more than you get in the short term.
• Who invests in players who can't immediately return the favour — the person who's new to the room, the one with fewer resources — versus who only cultivates relationships with obvious near-term upside.
• Whether early collaboration breaks down under resource pressure in rounds 6-8 when stakes feel higher. The players who held their network together under pressure and the ones who quietly stopped reciprocating are both visible.
• Who shifts strategy mid-game when the evidence is clear, and who doubles down on a solo approach because changing would feel like admitting the first approach was wrong.

These patterns map directly onto how leaders manage stakeholders, build influence across the organisation, and weigh the long-term value of relationships against short-term resource protection.

When to Bring This In

• Frontline managers being promoted to roles where they need cross-functional influence for the first time — people who were strong individual performers and are now discovering that authority doesn't travel outside their team.
• Technical teams that are high-performing in their lane but isolated from the broader organisation. The game makes the cost of that isolation visible in a way that's hard to dismiss.
• Teams where people know intellectually that relationships matter but don't actually invest in them — the gap between belief and behaviour is what Bloom closes.
• Pre-360 feedback programmes, to give participants a real-time data point about their own networking and relationship investment patterns before they see what colleagues say about them.

When This Isn't the Right Fit

• Groups where the networking problem is structural — no cross-functional meetings, no shared platforms, no opportunity to connect — rather than behavioural. The game changes behaviour; it can't fix an org design problem.
• Very small groups under 10. Network effects need density to be visible. Below that threshold, the compounding dynamics don't have enough players to develop properly, and the debrief loses its sharpest comparisons.
• Teams where relationships are already strong and the dynamic is genuinely healthy — Bloom works best when there's something to surface. It's diagnostic, not celebratory.

Who It's For

Bloom works well for leaders who need to operate through influence rather than authority — people managers, project leads, business partners, and anyone whose success depends on relationships they don't directly control.

It's also effective for technically strong teams who struggle with the relationship and networking side of their work. The game makes the value of that investment visible in a way that no amount of "you should network more" ever does.

What Happens in the Room

The first two rounds look like individual games. Players focus on their own gardens, make conservative trades, protect what they have. By round four, the pattern splits: participants who invested in others early are compounding returns. Those who played alone are falling behind and don't yet understand why.

By round six there's usually one player who has tried to win entirely alone — trading only when forced, never investing in anyone else's garden. The debrief uses that player's trajectory (anonymised) to show what transactional thinking costs over time. It's one of the clearest demonstrations in any game of how relationship investment compounds.

The moment most participants remember: realising, too late, that the person they declined to help in round three is now the person everyone else is trading with.

Specific Patterns That Surface

• Who approaches others with an offer before being asked — versus who waits to receive
• Who invests in players who can't immediately benefit them — versus who only trades with strong players
• Who shifts strategy mid-game when the early approach stops working — versus who holds the original approach and blames bad luck
• Who tracks what others need and proactively brings it to them — versus who only responds to direct requests
• Whether initial collaboration breaks down under competitive pressure in later rounds — which groups stay loyal to allies when the stakes rise

When to Bring This In

• Frontline managers transitioning into roles where they need cross-functional influence they don't yet have
• Technical teams who are high performers individually but isolated — the game makes the cost of that isolation visible in a way that no feedback conversation does
• Teams where "you should network more" is a known piece of feedback that hasn't changed behaviour — the game gives people their own data instead of someone else's opinion
• Before 360-degree feedback programmes — participants arrive with clearer self-awareness of their relationship patterns

When This Isn't the Right Fit

• Groups where the networking problem is structural — no cross-functional opportunities exist — rather than behavioural
• Groups smaller than 10 — not enough network density to generate meaningful relationship dynamics
• When the development need is around authority and decision-making rather than influence and relationships — Ripple Effect or Planetfall would be a better fit

The Debrief

Every session ends with an EPPA debrief: Experience, Patterns, Principles, Application. Participants don't leave with general reflections — they leave with a named behaviour to change and a specific situation to apply it in. The debrief is facilitated by the same person who ran the game. That continuity is what makes the insight land.

Bring This Game to Your Team

WhatsApp Arvindh Call +91 99458 61640