A LITTLE WORLDBUILDING. A LOT OF BELONGING.
TribalShaping
Field notes

Run a guild-name vote that produces a decision

Structure nominations, practical checks, preferences, and a final choice without an endless naming debate.

By Armindo · AI-assisted editorialUpdated October 23, 2026

A naming poll often mixes three questions: whether a candidate is usable, whether it suits the guild, and whether someone personally likes it. Separating those questions makes the conversation calmer and the result easier to explain. Set the process before revealing the favorites so nobody feels the rules were written around a preferred answer.

A scene from an imagined guild

Their first poll ended with three tied favourites and several people asking where their suggestion had gone. For the second attempt, Nia put the selection rules in the channel before collecting names. Every candidate needed a spoken form, a practical tag, and a sentence about the group it suggested. Members reviewed those details before choosing. The eventual winner was not everyone’s first choice, but nobody had to guess how it had reached the final ballot.

Create a brief everyone can see

Publish the intended audience, tone, supported languages, length restrictions, and any hard boundaries. Explain why each constraint exists. A short tag may be a platform requirement; a particular theme may be a cultural preference rather than a necessity. Invite candidates with a one-paragraph explanation and a proposed spoken form. Keeping the submission format consistent gives thoughtful suggestions the same space as immediately catchy ones. Limit the nomination window and say who will organize the shortlist, otherwise the group can remain in the enjoyable suggestion phase indefinitely.

Remove practical failures before preference voting

Check the relevant game restrictions, obvious naming collisions, uncomfortable meanings raised by members, and basic readability. A candidate that cannot be entered in the game does not become workable because it wins a popular vote. Explain removals in specific, respectful language and allow a corrected version when appropriate. If an objection concerns taste rather than a hard problem, leave that distinction visible. Members are more likely to accept a shortlist when they can understand how it was prepared, even if a personal favorite is missing.

Show each finalist in the same context

Give every name the same amount of explanation, the same plain typography, and the same sample recruitment sentence. A beautifully illustrated favorite has an unfair advantage over an undecorated alternative. Ask voters to consider their first choice and which other candidates they could comfortably use. You can collect ranked preferences or run a short final round; choose one method in advance and describe it simply. Avoid promising mathematical perfection. The purpose is a legitimate shared decision, not proving that one arrangement eliminates every possible disagreement.

Close the process and preserve the reasoning

Announce the result with the chosen spelling, tag, pronunciation, and a short explanation of why it fits the brief. Thank the contributors and explain any tie-breaking rule that was used. Give practical concerns one defined route for follow-up, while making clear that the preference stage has ended. Start using the name in an ordinary guild activity so it becomes part of shared life. Archive the brief and final options. If the group revisits naming years later, officers will have a record of the decision rather than a collection of screenshots and remembered grievances.

Shape your guild name

A little control over your space.

The naming engine runs on your device. Optional favorites and your language preference can be kept in this browser. No advertising or analytics scripts are active. This panel controls local site storage; it is not an advertising consent platform.