Simone Tabellini
iten
#community#legacy

How to build a legacy

An active community isn't a resilient community. They're two very different things.

At play2match the product isn't the app and it isn't the events: it's the community. At some point I asked myself a simple question. If I disappeared for three months, would the community survive?

The honest answer was no.

  • Matches only worked if we were there.
  • Our Lead Matchers were good, but they had no tools to read the mood of the community.
  • The most loyal people felt like guests: “but I'm nobody, you're the ones who count”.
  • There was no shared story, no language, no symbolic place.
  • Someone who'd played dozens of matches looked no different from someone showing up for the first time.

In sport, legacy is a jersey everyone pulls on when they join the club. A community needs the same thing. To build it, we took everything apart and put it back together around three levers.

Lever 1

Mythology and identity

A community needs a story people can tell. Without a “before”, nobody can say “I was there”.

  • Canonise the first ones

    Celebrate the people who were there at the start, in public. Build an archive of photos, messages and stories: the origins corner.

  • Build a language

    We say crew and matcher, not users and participants. Words decide who feels like they're in.

  • Make the pact explicit

    Whoever joins signs a manifesto. Not a click on the terms and conditions: a deliberate gesture.

Lever 2

Status and distributed leadership

Behaviour, recognition, emulation, culture. Culture isn't declared: it's emulated.

  • Make the hierarchy visible

    Newcomer, Matcher, Super Matcher, Lead Matcher. A status recognised in front of everyone, not just a discount in private.

  • Invent rotating micro-roles

    The photographer of the night, the one who welcomes newcomers, the one who picks the newsletter title. Anyone can feel useful.

  • Amplify the small gestures

    Every day look for a gesture of leadership, give it a voice with a shoutout or a small responsibility, and watch what happens.

Lever 3

Closing the loop on feedback

Collect, analyse, change, tell everyone publicly what you changed, collect again.

  • Once a month, per city

    At least one “we changed this thanks to you”, visible, specific and direct.

  • Turn whoever speaks up into a co-author

    When people see their feedback become reality, the next round of feedback is richer and comes more often.

The test

Three questions to ask yourself about any community project.

  1. 1. Does the community have a story that lives without me?
  2. 2. Is status distributed or centralised?
  3. 3. Am I closing the loop with the people who give me feedback?

If the answers are no, the problem isn't growth: it's architecture.

An honest note: we're still putting these practices into action. They're a method, not results we've already measured.

This guide comes from the article I wrote with CommunityLand, which made it into the top 10 of their most-read chapters.

Read the full article on CommunityLand (in Italian)

FAQ

What does it mean to create a legacy in a community?

It means building a community that keeps existing even without the people who founded it: with a shared story, status distributed among its members and a recognisable way of being together that newcomers inherit.

What is the difference between an active community and a resilient one?

An active community works as long as the team is there and keeps proposing things. A resilient community holds up even if the team disappears for a few months, because the members propose, organise and recognise one another.

What are the three levers for building a legacy?

Mythology and identity (a shared story, a language, an explicit pact), status and distributed leadership (a visible hierarchy and rotating micro-roles), and closing the loop on feedback (telling people in public what has changed thanks to the members).

How do I know if my community would survive without me?

Ask yourself three questions. Does the community have a story that lives without you? Is status distributed or centralised? Are you closing the loop with the people who give you feedback? If the answers are no, the problem is architecture, not growth.

Where does this guide come from?

From the article “Play2match: costruire una community resiliente” (“building a resilient community”), chapter 95 of the CommunityLand newsletter, published on 30 March 2026 with Simone Tabellini's account.