Communities need responsibilities.
They do not always need complicated hierarchies.
Roles solve jobs
Examples:
member;
mentor;
moderator;
event organizer;
editor;
administrator;
technical operator;
volunteer;
project lead.
A role should exist because work or authority needs to be defined.
Avoid title inflation
Creating dozens of ranks can make a small community harder to understand.
Ask:
What can this role do?
What responsibility does it carry?
How is it earned or assigned?
Who can remove it?
Authority should be visible where necessary
Members should know who can:
moderate;
change rules;
manage accounts;
handle private reports;
speak officially;
or make operational decisions.
Unclear authority creates unnecessary conflict.
Roles can evolve
A community may begin with one operator doing everything.
As participation grows, responsibilities can be distributed.
Build roles around actual work rather than imaginary future bureaucracy.
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?