R4/R5 leadership playbook
Make the correct action easier than the wrong one.
Members should not need to decode five chats, three time zones and an unexplained map marker. Good leadership turns strategy into one clear next action.
Every event message needs
- What: event and objective
- When: UTC, primary local time and countdown
- Where: coordinates or marker
- Who: teams and callers
- What not to do: protected targets, reserved attempts and stop conditions
Divide ownership
| Role | Owns |
|---|---|
| Event lead | Plan, objective changes and final calls |
| Diplomacy lead | External agreements and incident resolution |
| Roster lead | Attendance, teams and substitutes |
| Education lead | Plain-language instructions and new-player questions |
| Language leads | Human translation when automatic translation is unclear |
| Buff coordinator | Fair rotation of limited construction, research or combat benefits |
Copyable announcement
EVENT: [name]
START: [UTC] / [local time] / [countdown]
MEET: [coordinates or marker]
TEAM 1: [job + caller]
TEAM 2: [job + caller]
SAVE: [attempts / stamina / teleports / speedups]
DO NOT: [protected targets or common mistake]
IF ABSENT: Tell [name] before [time].
After-action review
- What was the stated goal?
- Did members understand their jobs?
- Where did timing or translation fail?
- Which reports prove what worked?
- What one change will be tested next time?
Do not bury the instructionPut the required action in the first two lines. Lore, encouragement and explanation can follow. A member opening the message during work should still know where to go.
How much should leaders disclose?
Share enough for members to act and understand the goal. Keep sensitive negotiations and contingency details within the officer group until disclosure is useful. Secrecy without clear orders feels like chaos to everyone else.