Leadership FAQ
Leadership problems are rarely complicated because nobody has an idea. They are complicated because the same issues repeat, emotions get involved, and important decisions disappear in chat. These answers are designed to give leaders a practical starting point.
01 How should I structure an R4 team? +
Give every officer a real area of ownership without creating unnecessary hierarchy.
- Start with the work your alliance actually needs covered: war planning, recruiting, communication, member support, event coordination, diplomacy, and administration.
- Assign one primary owner for each recurring responsibility and at least one backup.
- Give R4s authority to make routine decisions inside their lane instead of requiring the R5 to approve everything.
- Review the structure periodically. A title should describe useful work, not simply reward seniority.
Promoting several R4s without defining ownership. Everyone has rank, but the R5 still performs every task.
Write down every recurring leadership duty, assign a primary and backup owner, and share the list with the full leadership team.
02 How do I remove an inactive member without creating drama? +
Protect alliance activity while treating the member respectfully.
- Use a clearly communicated activity standard so removal is based on an existing expectation rather than a surprise decision.
- Check for known real-life circumstances, vacations, or prior communication before acting.
- Contact the member privately when practical and explain the reason simply.
- Leave the door open for a future return when appropriate.
Turning the removal into a public judgment of the person or debating their value in alliance chat.
Use a neutral message: the roster standard was not met, the spot is needed, and they are welcome to contact leadership if circumstances change.
03 What is the best way to onboard new members? +
Make expectations and resources obvious before a new member has to ask.
- Give every recruit the same short welcome process.
- Explain alliance rules, event expectations, important times, communication channels, and who to contact for help.
- Point them toward the few guides or tools they need first rather than overwhelming them with everything.
- Have an R4 check in after a few days to catch confusion early.
Assuming a strong player already understands your alliance culture, state rules, or event procedures.
Create one reusable onboarding checklist and assign an R4 to own the first-week follow-up.
04 How should alliance expectations be set? +
Create standards members can actually understand and follow.
- Keep rules short enough that members can remember them.
- Separate true requirements from recommendations.
- Explain why important rules exist and what happens when they are repeatedly ignored.
- Announce meaningful changes before enforcement whenever possible.
Adding new rules reactively after every individual problem until nobody knows which expectations matter.
Maintain one current rules list and use the Incident Log to document additions, removals, and changes.
05 How do I run leadership chat effectively? +
Turn discussion into decisions and assignments instead of endless scrolling.
- State the issue clearly before opinions begin.
- Separate brainstorming from the final decision.
- When a decision is made, summarize it with the owner and next step.
- Move sensitive member issues out of broad chat when only a few leaders need to handle them.
Allowing five topics to run at once with no summary, owner, or conclusion.
End important discussions with three lines: Decision, Owner, Next Action.
06 How should repeated rule violations be handled? +
Be consistent without making every mistake a confrontation.
- Confirm the facts before assuming intent.
- Address the first issue privately when possible.
- Document repeated incidents so leadership is working from history rather than memory.
- Escalate consequences according to the seriousness and repetition of the behavior.
Treating similar violations differently depending on who committed them.
Use the Incident Log and agree on a simple escalation pattern before the next difficult case occurs.
07 How do you build a NAP that actually works? +
Create a cooperation agreement that protects the state instead of simply creating a list of protected tags.
- Define what membership represents before deciding which alliances belong.
- Set expectations for communication, participation, rule compliance, diplomacy, and state contribution.
- Make processes for disputes, city allocation, rule changes, and removal clear.
- Review whether the NAP is still serving the state as conditions change.
Treating NAP membership as permanent status regardless of behavior or contribution.
Write the membership standard first, then evaluate alliances against that standard consistently.
08 How should leadership prepare for migration? +
Know what the alliance needs before recruiting or releasing players.
- Identify roster gaps, time-zone needs, leadership needs, and competitive goals.
- Track prospective arrivals and likely departures before migration opens.
- Be transparent with recruits about alliance expectations and state culture.
- Coordinate with state leadership when movement affects NAP balance or alliance viability.
Recruiting only by Total Power and discovering later that activity, goals, or time zones do not fit.
Define three to five recruitment priorities before evaluating candidates.
09 How should leaders communicate during conflict? +
Solve the actual problem without making the conflict larger.
- Slow the conversation down enough to establish facts.
- Use one or two designated contacts instead of having an entire leadership team argue at once.
- Keep messages specific to the issue and avoid insults, motives, or unrelated history.
- Confirm the resolution in writing so both sides understand what happens next.
Responding publicly while angry and turning a solvable incident into an alliance-versus-alliance identity fight.
Move the discussion to the smallest useful leadership group, summarize the facts, and state the desired resolution.
10 How do I delegate instead of having one R5 do everything? +
Make leadership sustainable and develop officers who can operate without constant supervision.
- Delegate outcomes, not just tiny tasks.
- Give the responsible R4 the information and authority needed to finish the job.
- Accept that another leader may solve a problem differently than you would.
- Document recurring processes so responsibilities can move when leadership availability changes.
Delegating a task while requiring approval for every step, which leaves the R5 doing the mental work anyway.
Choose one recurring responsibility this week and transfer full ownership of it to an R4 with a clear success standard.