A scorecard can organize a naming discussion, but numbers do not make taste objective. Use a few clear dimensions to expose tradeoffs and disagreements. The goal is to understand why one candidate works better for this guild, not to give a creative decision the appearance of scientific certainty.
A scene from an imagined guild
Their spreadsheet preferred one candidate. Around the voice channel, nobody wanted to introduce themselves with it. The scorecard had given extra weight to dramatic imagery because that column was easy to discuss; it had barely considered ordinary speech. They changed the weights and repeated the listening exercise. The numbers did not choose for them, but they revealed why their first result felt wrong. The final discussion was shorter because the disagreement finally had a name.
Choose dimensions you can explain
Start with community fit, ease of saying and typing, recognizable identity, and practical usability. Give each dimension a plain question. For community fit, ask whether the name supports the promise in your recruitment brief. For usability, ask whether it fits the destination fields and has a workable tag. Avoid scoring several versions of the same preference, such as coolness, impact, and impressiveness, because that quietly gives one taste extra weight. Keep the framework small enough that members can apply it without needing a workshop on the scoring system itself.
Write evidence beside the rating
If someone gives a low speech score, ask what happened in the listening test. If a candidate scores highly for meaning, ask which member behavior supports that reading. A short note is more valuable than an unexplained number. Use a simple scale with described endpoints and score independently before discussing the results. This reduces the temptation to echo the first confident speaker. Treat missing evidence honestly: an untested platform constraint is not a passing result, and unfamiliarity with a coined word is not automatically a permanent usability failure.
Look at disagreement before the average
Two names can receive the same average for very different reasons. One may be acceptable to everyone; another may be loved by half the roster and strongly disliked by the rest. Read the pattern and ask whether the disagreement concerns the name or an unresolved question about guild culture. You may need a sharper brief, a practical test, or a revised candidate rather than another round of arithmetic. If you weight dimensions, explain the reason before seeing the totals. Changing weights after the favorite loses makes the process harder to trust.
Let the final decision include a sentence
Choose the finalist with an explanation of the tradeoff you are accepting. You might prefer a slightly longer name because its image genuinely fits the community, while adopting a compact tag for crowded interfaces. Or you might choose the simpler phrase because international members can use it comfortably. Record what would have to change to reconsider the choice. Then close the discussion and use the name. A good scorecard leaves a clear account of judgment, not an invitation to keep adjusting decimals until every member sees their favorite at the top.
