Community Strategy Frameworks: SPACES, Orbit, Community Canvas, and the Community Lifecycle

Community professionals have developed a handful of frameworks that make strategy conversations faster and design decisions clearer. None of them is a rulebook, and most practitioners borrow from several. This guide explains the ones you will encounter most often and when each is useful.

What a community strategy has to answer

Before any framework, a community strategy must answer three questions:

1. Why does the organization want this? The business outcome. Retention, support cost, acquisition, insight, revenue, or mission.
2. Why would members want this? The member promise. What a member gets that they cannot get elsewhere.
3. How do the two reinforce each other? The flywheel. Members getting value should produce the organization’s outcome, and the organization’s investment should produce more member value.

If any of the three is vague, the community will struggle no matter which framework you use. The frameworks below are tools for sharpening each answer.

SPACES: naming the business value

SPACES, from CMX, the community professional network founded by David Spinks, lists the six categories of value a community can deliver to an organization:

• Support — members help each other, reducing service cost and improving answers.
• Product — members provide feedback, ideas, and testing that improve what the organization builds.
• Acquisition — members refer peers and generate content and advocacy that attract new customers or members.
• Contribution — members create value directly: content, answers, code, events, mentorship.
• Engagement — members stay longer and buy more because they are connected to each other.
• Success — members achieve the outcome the organization promises, with the community as the vehicle.

The point of SPACES is to pick one primary value. Communities that try to deliver all six at once deliver none well. An association’s community is usually Engagement (renewal) first. A customer community is usually Support first. A founder community is usually Success first.

The Orbit model: community as orbits, not a funnel

Marketing thinks in funnels: people enter at the top and are pushed toward a conversion. The Orbit model, developed by the team behind the Orbit community tool, argues that community does not work that way. Members move in and out of involvement, and the goal is gravity, not conversion.

The model places members in concentric orbits:

• Orbit 4 — Observers. Aware, occasionally reading.
• Orbit 3 — Users / Participants. Engaging periodically.
• Orbit 2 — Fans / Contributors. Contributing regularly.
• Orbit 1 — Ambassadors. Leading, recruiting, and representing the community.

Members are positioned using two measures: love (how connected and active they are) and reach (how much influence they carry). A member with high reach and low love is worth nurturing; a member with high love and low reach may be your next volunteer leader.

Orbit thinking is useful for two things: it reminds you that the outer orbits are legitimate (lurkers are members), and it gives you a vocabulary for moving members inward with specific invitations rather than generic pushes.

The Community Canvas: a design checklist

The Community Canvas, created by Fabian Pfortmüller, Nico Luchsinger, and Sascha Mombartz, is a one-page framework for designing a community. It organizes seventeen themes into three areas:

• Identity — purpose, member identity, values, success definition, brand.
• Experience — selection (how people join), transition (onboarding and leaving), shared experiences, rituals, content, rules, roles.
• Structure — organization, governance, financing, channels and platforms, data management.

The Canvas is most useful at the design stage, as a checklist to make sure nothing is left implicit. Most community failures trace back to a theme the founders never decided: there was no selection process, no definition of success, or no governance for when the founder steps back.

The Community Roundtable maturity model

The Community Maturity Model, from research firm The Community Roundtable, describes how organizations’ community capabilities mature across eight competencies (strategy, leadership, culture, community management, content and programming, policies and governance, tools, and metrics) through four stages:

1. Hierarchy — community is informal or absent; the organization broadcasts.
2. Emergent community — a community exists but is under-resourced and loosely connected to strategy.
3. Community — the community is resourced, managed, and measured.
4. Networked — community approaches are embedded across the organization.

Its practical use is diagnosis: it shows an organization which competency is holding the community back. Most communities stall at stage 2 because of leadership and metrics, not tools.

Dunbar’s number and the case for small groups

Anthropologist Robin Dunbar proposed that humans can maintain roughly 150 stable relationships, with tighter layers at about 5 (closest), 15 (close friends), and 50 (friends). The exact figures are debated, but the design implication is widely accepted: beyond a hundred or so members, a single undifferentiated space stops feeling like a community, because members can no longer know each other.

The answer is structure: chapters, cohorts, special-interest groups, or small facilitated groups inside the larger community. Founder networks have known this for decades; a 10,000-member organization is really a thousand groups of ten. See How to Run a Founder Peer Group.

The community lifecycle

Communities pass through recognizable stages, and the work changes at each one. Researchers Alicia Iriberri and Gondy Leroy summarized the literature in 2009 as inception, creation, growth, maturity, and death or renewal. Community strategist Richard Millington’s practical version has four stages:

Knowing the stage prevents two common mistakes: applying maturity-stage tactics (committees, elaborate programs) to an inception-stage community, and failing to add structure when a mature community starts to feel impersonal.

Using the frameworks together

A practical sequence:

1. Use SPACES to choose the primary business value.
2. Use the Community Canvas to design identity, experience, and structure.
3. Use Dunbar to decide the group structure.
4. Use the lifecycle to plan the work for the current stage.
5. Use Orbit to think about moving members inward.
6. Use the maturity model once a year to diagnose what is holding the community back.

No framework replaces judgment about your specific members. They are shared vocabulary, and shared vocabulary makes better conversations with leadership, members, and other community professionals.

Next: How to Choose a Community Platform.