online management

This essay originally appeared in the June 2001 issue of Imaginary Realities.

While finding new immortals for a MUD, MUSH, MOO or MURPE generally isn’t a problem, finding ones who will be a lasting and productive part of the team is. The first couple of weeks for a new staff member on a multiplayer game are the ones where the most mental adjustments are made, and the actions of other staff are often a crucial factor in whether or not those staff stick around. Armageddon MUD provides a good example of how this process can be made as painless as possible for both new and established staff members.

New immortals on Armageddon have undergone a fairly selective process to get there. When a gap is perceived, I post on our discussion board what the gaps are and who is being considered to fill them. In considering candidates, we look for the following:

• Imagination, creativity and writing talent
• Knowledge of the game and its world
• Ability to function as part of the team, including the ability to work with other people, to take input/criticism without feeling diminished or angry and a willingness to work within our guidelines and rules.
• A history of both integrity and trustworthiness
• Sufficient time and energy to dedicate for the game

At this point, I usually feel out the various candidates to see if there’s any of them who would not want to be on staff. Some people prefer to play, and do not wish to come on staff since the mystery of the game would be lost for them. If they’re interested and I haven’t seen past examples of their writing style, I might ask them to write up two or three possible small plotlines and send them to me as a sample. Other staff members post their impressions of the candidates or email in reactions to me, and in a week or so, we come to a consensus about which candidate(s) to approach.

Once that’s done, we set up the new immortal so they can start to read through our documentation, see what’s happening on the immortal discussion board, etc. Then they can log on and begin poking around, usually with another staff member walking them through the basic commands, questions, etc.

People come onto the Armageddon staff at the level of Storyteller. Storytellers run plots and clans, animate NPCs, build (etc). There’s a bewildering medley of options and expectations for a new immortal, so we assign a primary and secondary mentor, usually staff members who have been around for a while and who can answer questions. A lot of time they’re pointing people to the documenation.

We’ve got a lot of documentation, to the point where some new immortals have described it as daunting. But much of that documentation is devoted to helping the new imm: building and procedure guidelines, information about features in the world in the form of Who Is/What is pages and histories of the major clans and noble houses, tutorials for creating objects, NPCs, rooms, and documents. When a new immortal appears, I point them towards specific documents (the immortal discussion board, the guidelines for new staff members, the staff contract, and the mission statement) that I prefer that they read before logging on for the first time.

My feeling as far as new immortals go is that acclimating is much, much easier if they have some definite things they’re supposed to be doing. These should not be overly daunting. Running a clan, for example, requires a lot of organization and coming up to speed, so something smaller, such as helping with one aspect of a clan, or writing NPCs for it, may be a much better initial project.

Additional projects might include: asking them to come up with two or three mini plotlines to run, right off the bat; asking them to work with a plotline already in progress, which has already been planned and sketched out by someone who needs assistance running it; working with npcs in a particular area in order to get a feel for it; filling in gaps in the documentation. Generally, I try not to make these projects building an area, unless it’s a very small project that fits inside another one, like a couple of houses or an oasis.

Giving new staff feedback on what they’re doing is important, but during the initial stage this is not so crucial as is making sure they have resources and teachers who can help them get up to speed on things as painlessly and quickly as possible. Towards this end, make sure they know the rest of the team — I post on the immortal board to let people know who’s coming on board and what they’ll be working on. It’s good if the new staff member posts an introduction themself, with information like what they’re interested in working on, what their areas of expertise are, how they started playing the game, experience with past MUDs, and so on.

It’s also important that new staff know what’s expected of them, in terms of work and conduct. Documentation can help enormously here, but again, it’s having people that can explain things that is the most valuable resource.

In short:

• choose new staff carefully
• make sure new staff members have access to the information and resources they need
• work with them on coming up with clear, measurable tasks so they know what you’re expecting from them

One of the sad truths of the mud world is that there are never enough coders. Builders aplenty, brimming with fresh idealism and plans for entire zones, appear (and sometimes disappear) at the drop of a hat. But coders are the unicorns of the mudding world, seldom glimpsed and ardently pursued. We are lucky enough to have three dedicated coders on Armageddon MUD: Morgenes, Tenebrius and Tiernan, as well as a few other staff members willing and able to wade through the bugs file and tinker with things upon occasion. How, then, does an administrator keep these rare beasts happy? The following four steps may help.