Inventing the Troubleshooter Team
By Nelson McKeeby
The Team Came Before the Organization
The first Troubleshooter team did not begin with a chart of departments, billets, and command relationships. I knew that Project Negentropy was sending capable specialists into the future, and I knew that several of them had to work together because no individual could carry enough knowledge to answer every problem the future might present. The characters therefore entered Campaign 80 as educated adults with different backgrounds and bodies of experience. Once play began, immediate problems forced the group to divide responsibility. Somebody dealt with an injury, somebody took charge of a technical failure, somebody kept track of supplies, and somebody coordinated a decision when several people needed to act at once. Repetition turned those decisions into habits, and the habits gradually became recognizable team jobs. The organizational language came afterward, when I began giving names to patterns that had already proved useful at the table.
One principle was already established: Project Negentropy was a civilian effort concerned with preserving human capability. Troubleshooters needed to defend themselves because the future was dangerous, but combat was only one of many situations they had to survive. A team also needed medicine, science, engineering, communication, navigation, logistics, investigation, and the ability to understand communities whose institutions and assumptions could be entirely unfamiliar. The Project therefore had reason to send people whose value might remain invisible during the first day after a Cylinder opened. A specialist could contribute little while camp was being established and later become the only person available who understood a problem well enough to solve it. That longer time horizon became central to the idea of the Troubleshooter team.
Profession and Team Responsibility
The distinction that clarified the design was the difference between a lifetime specialty and a team responsibility. A profession represented years of education followed by the judgment acquired through work in the field. The Project selected people partly because that depth of knowledge could not be created quickly. An archaeologist had learned far more than a collection of procedures for excavating a site; years of study had trained the person to interpret physical remains, compare evidence, recognize context, and distinguish a plausible explanation from a convenient one. The same principle applied to physicians, engineers, linguists, biologists, historians, and the many other specialists Project Negentropy might consider worth carrying into the future.
A team responsibility answered a different need. Before Cylinder entry, the Project could spend roughly a year giving a specialist concentrated preparation for work the team was likely to need immediately. An archaeologist could therefore receive medical training and become the person normally responsible for first treatment of injuries without ceasing to be an archaeologist. That year could teach procedures, provide supervised practice, and produce a dependable second competence. It could not reproduce the judgment accumulated through a professional lifetime, and it did not need to. The team received someone able to carry an immediate responsibility while the future also received the deeper body of knowledge that had made the person worth selecting.
This distinction also prevented the jobs from becoming exclusive character classes. A named responsibility identified the teammate with additional preparation and the expectation of taking charge when that kind of problem appeared. Other Troubleshooters still needed enough general field competence to assist, take over when somebody was injured, and continue functioning if the team became separated. Overlap made the group resilient, while different lifetime specialties gave the overlap texture. Two people could both know how to stabilize a casualty, repair ordinary equipment, or examine a scene, yet each would approach the problem through a different intellectual history. The job told the group who normally carried responsibility; the profession helped determine how that person thought.
Leadership developed in the same practical way. Campaign play repeatedly produced moments when somebody had to coordinate the group, and adults accustomed to professional decisions could accept temporary leadership when it was useful. The person directing one problem did not automatically control the next. Authority could move toward the teammate whose knowledge best fit the situation, while a more general team leader kept track of priorities, disagreements, time, and the consequences of committing people and equipment. This gave the team coordination without turning every problem into a military chain of command.
Campaign 80 and the Discovery of the Jobs
Campaign 80 was where these ideas became visible through play. I had not assigned a finished set of billets before the first adventure. The players discovered recurring needs because the same kinds of decisions returned. Equipment failed more than once. People were injured more than once. The group had to decide where it was going, what it could carry, who should speak for it, and what to do when information was incomplete. A player who repeatedly handled one of those problems became the person the others expected to handle it again. The expectation improved the efficiency of the group, and eventually it became useful to formalize the responsibility.
That sequence shaped the later organization of Project Negentropy. The department did not create the field problem; the field problem created a reason for the department. Once the same responsibility appeared across several teams, the Project could plausibly identify it in advance, train people for it, develop equipment and procedures to support it, and create an institution responsible for maintaining that preparation. The modern organization described in Master Control is therefore much more formal than anything I had when the first team entered play, but its structure still reflects problems discovered at the table. The bureaucracy grew outward from the working team.
The same process helped me understand why Troubleshooters needed broad capability. A team organized around a handful of narrow specialists would become fragile the moment the wrong person was absent. Campaign play constantly produced mixed problems: an injured person beside a damaged machine, a negotiation complicated by language, a route choice influenced by weather and supplies, or an investigation in which technical knowledge changed the meaning of the evidence. Troubleshooters worked better when each person had a center of responsibility, enough general training to support the others, and a lifetime specialty capable of becoming relevant in ways nobody had predicted before play began.
The Archaeologist and the Birth of Investigation
One Campaign 80 character made the whole principle clear. The character was an archaeologist, a specialization that could appear inefficient if the team were judged only by the first hours after emergence. Archaeology did not automatically establish a camp, repair a machine, or treat an injury. It existed in the team because Project Negentropy was supposed to preserve more than the skills required for immediate survival. Then the campaign produced a murder committed by a Clicker, and the archaeologist was confronted with a problem whose solution depended upon habits already learned in another field.
Archaeology had trained the character to examine physical remains, preserve context, compare traces, and reconstruct events from material evidence. Those habits could be extended toward the examination of a dead human body and the circumstances surrounding the death. The character began developing toward forensic anthropology because the campaign had created a reason to carry existing knowledge into a neighboring discipline. The new competence did not appear from nowhere, and the original specialization did not disappear. The character learned laterally because archaeology supplied an intellectual foundation from which the new work made sense.
The murder also changed the game itself. Investigation had always been present whenever players asked questions about something they did not understand, but the Clicker killing exposed it as a recurring form of work. Reconstructing an event required disciplined treatment of evidence, comparison among competing explanations, and a willingness to change an explanation when the physical record contradicted it. A single convenient roll could not provide the same experience. The players had to decide what to examine, what to preserve, what a clue could actually establish, and what remained uncertain. That process made investigation distinct enough that I could begin treating it as an organizational need rather than an incidental use of science.
The later Project could therefore train people specifically for investigative responsibility while still drawing heavily on their original disciplines. An archaeologist, physician, chemist, engineer, linguist, or historian might all become effective investigators, but they would notice different things and possess different limits. Formal investigation preserved the value of those differences. It gave the team a responsibility for turning uncertainty into a usable account of what had happened without reducing every investigator to the same generic detective.
From Repeated Needs to Project Departments
Once recurring team functions had names, departments became a logical next step. If many teams needed medical preparation, somebody had to decide what that preparation included, how it was taught, what equipment accompanied it, and what standards indicated that a trainee was ready. Engineering, investigation, communication, operations, and other repeated responsibilities created the same institutional questions. The modern Project departments grew from the need to support those functions consistently before a team entered a Cylinder. Their purpose was to prepare the person who would carry the responsibility in the field.
This order of development remains important because it keeps the organization subordinate to the people doing the work. A department can define training, procedures, records, and support, but it does not explain the whole value of a Troubleshooter. The person still arrives with an education and a professional history formed before the assignment. The Project then adds field preparation designed to make that person useful inside a small group whose members must depend upon one another. When the future presents an anticipated problem, the team job gives the group an immediate answer. When the future presents an unanticipated problem, the deeper specialty may provide the concepts needed to invent one.
The archaeological example also showed why perfect prediction was the wrong goal for the Project. Nobody needed to foresee a particular Clicker murder and then recruit an archaeologist because forensic anthropology would be required years later. The archaeologist was worth preserving because archaeology was itself a substantial part of human knowledge. When a new problem appeared, that stored expertise proved capable of extension. The Project's strongest preparation for an unknowable future was therefore a population of deeply educated people who could adapt what they knew, supported by enough common and team-specific training to survive long enough to do so.
What a Troubleshooter Team Carries
That is the principle that eventually defined the Troubleshooter for me. A character begins as a person whose education has already shaped the way the world is interpreted. Project training adds responsibilities, procedures, equipment, and habits of teamwork. Campaign experience adds another layer as the character discovers new applications for old knowledge, develops competence in neighboring fields, and responds to needs nobody could have listed before emergence. The result is a character who can be useful immediately without being exhausted by the job written beside the name on a personnel form.
The structure also works well in play because responsibility can move as the problem changes. During an injury, one character may become central. In an unfamiliar ruin, another person's specialty may suddenly govern the group's decisions. A technical failure, negotiation, unexplained death, weather emergency, or supply crisis can shift attention again. Players receive concrete reasons to act during ordinary team life while retaining the possibility that an apparently obscure part of a character's education will become decisive later. The campaign can therefore reveal what a character is good for instead of requiring every future use to be known during character creation.
Looking back, the Troubleshooter team was conceived as a small piece of civilization carried through the Cylinders. Immediate competence kept the team alive, while lifetime knowledge gave survival a larger purpose. The archaeologist who became a forensic scientist remains the clearest example because the character's value changed without becoming arbitrary: accumulated knowledge met an unexpected problem and produced a new application. The departments eventually organized the recurring responsibilities around that process, but the underlying idea had already appeared in play. Project Negentropy was sending people who could function together in the present and who carried enough human knowledge to make the future more capable than it had been before they arrived.