Build a real community

Protecting Community From Platform Dependency

Lesson 20 of 25

Platforms can provide extraordinary tools.

Dependency becomes dangerous when the community cannot function without one particular provider.

Identify dependencies

Ask:

Where are the members?

Where is the member contact information?

Where is the knowledge?

Where are the files?

Where are the event records?

Where are the rules?

Where is the official identity?

Where is the conversation?

If every answer is the same outside platform, the dependency is substantial.

Build independent anchors

Useful anchors include:

domain;

domain email;

website;

portable archives;

direct subscriptions;

member database where appropriate;

documented community identity.

Do not duplicate everything unnecessarily

Resilience does not mean operating five identical systems.

It means protecting the pieces whose loss would threaten continuity.

Platform protection is not platform rejection

Use the best tools available.

Understand what happens if one disappears.

That is the entire principle.

Put This Lesson to Work

Choose an existing or proposed community. Apply this lesson to its purpose, membership, communication, safety, or continuity. Write one action that would make participation clearer or more useful.

Worked example

For welcoming members, write a short introduction explaining who the group is for, a first useful action, the rules, and where a newcomer can ask for help.

Your finished result

A concrete community improvement and a way to check whether members find it useful.

Check your understanding

  • Can you explain the main idea without repeating a slogan?
  • What evidence or example supports your explanation?
  • Which decision will you make differently, and why?
Open the matching worksheet
WRUnity logo

Welcome to WRUnity

One free SpiderTaz Network account works across every network site.