Chapter 4. The Designer as a Profession

A job title is needed for the duty of producing the deliverable. If a worldview is an asset, someone has to own the production and management of that asset, and that person's work overlaps with the writer's work without being identical to it. The guiding question of this chapter is: what is the difference between the writer and the designer? The reason to draw a boundary is not to build a hierarchy but to make collaboration possible. Where there is no boundary of duties, there is no boundary of responsibility, and work without responsibility never becomes a profession.

1. The Difference Between the Writer, the Planner, and the Designer

The three roles are most accurately distinguished by their deliverables. The writer's deliverable is the work: a completed story with a beginning and an end, the final product the reader consumes directly. The planner's deliverable is the product's requirements: a document defining what should be made and why, and to whom and how it will be sold. The designer's deliverable is the world — or more precisely, a referenceable system of documents that holds the world, an intermediate good that the writer and the planner consume. This difference between final good and intermediate good is what splits the three roles' standards of evaluation. A work is judged by the reader's response, a plan is judged by the product's performance, and a worldview document is judged by how little the creative works that referenced it went astray. The timing of judgment differs too. A work is judged the moment it is released, but a document's quality only surfaces after it has passed through several derivations. The customer differs as well. The writer's customer is the reader; the designer's customer is, first and foremost, fellow creators. When this distinction blurs, accidents follow. If the designer tries to face the reader directly, the document starts imitating a work and taking on narrative of its own; if the writer also carries responsibility for managing the world, creation gets crushed under administration. Either way, both roles' deliverables get worse together. One person can wear several hats. But which hat is being worn at any given moment must always be clear. It is not holding multiple roles that causes accidents, but holding them without noticing which one is in play. The smaller the organization, the more it helps to make declaring the role switch a habit.

2. Designing versus Editing: You Write the Story but Design the Worldview

The choice of verb also marks the boundary between duties. It is accurate to say a story is written, and a worldview is designed. To write points to a linear production that flows from beginning to end. To design points to a structural production that arranges elements and adjusts the relationships between them. But looking at the actual process of worldview work, even "design" undersells it, because half of it is editing. Settings are unearthed from existing works, scattered fragments are cross-checked against each other, conflicts are arbitrated, what to keep and what to discard is judged, and notation is unified. More time goes into putting what already exists in order than into creating something from nothing. This is especially true when inheriting the world of a long-running serialized work: the first year is spent almost entirely editing. This fact changes the standard for hiring and training. The common belief that the talent a worldview position most needs is inventive imagination is only half right. Imagination merely produces candidates; the ability to induct a candidate into the world is the ability to cross-check, judge, and record. A good designer's list of qualities therefore overlaps heavily with a good editor's: the reading comprehension to read someone else's writing accurately, the persistence to apply rules consistently, the restraint to place one's own taste behind the world's standard. The stronger a person's own desire to build their own world, the more likely they are to waver in this seat of managing someone else's. The image is closer to a librarian's meticulousness than a creator's flair. What to ask in a hiring interview, accordingly, is not "build us a world" but "arbitrate the conflict between these two settings." Only once this image is firmly established does the next comparison become accurate.

3. The Difference Between the TRPG Game Master and the TRPG Setting Book

The designer is often compared to a TRPG game master, and the comparison is half wrong. The master is the one who executes the live session. They respond in real time to the players' unplanned actions, rule on gaps in the rules on the spot, and answer for tonight's fun. The master's talents are quick wit, performance, and pacing. The designer's place is not the master but the setting book sitting on the master's desk. Whoever made the campaign setting is not present at the table. Instead, they supply, in advance and in document form, a world that will not collapse no matter which master runs it at which table. On-the-spot rulings belong to the master; filling in the material those rulings will be based on belongs to whoever made the setting. A good setting does not restrict the master's improvisation — it raises the quality of that improvisation. In practice, this distinction shows up as a question of authority. The authority to improvise on the spot and the authority to revise the world are different authorities. Just as a ruling a master makes in tonight's session does not automatically become the law of the world, an improvised setting a writer creates within one work does not automatically become canon. It must pass through the gate called registration. The gate is not censorship that filters out on-the-spot creativity; it is review that puts the addition against the whole of the world. In the other direction, the designer has to guard against the temptation to direct the table personally. Supplying the documents and guarding the gate is as far as the setting side's job goes. A designer who cannot resist the temptation to intervene at the table ends up as the bottleneck of every project. Building a structure that keeps running without them is this profession's paradoxical condition for success.

4. Naturally-Arising Worldviews and Deliberately-Designed Worldviews

There are broadly two paths by which a worldview comes into being. A naturally-arising worldview is one where the work comes first and the world is organized afterward. Settings accumulate as installments pile up, and at some point that accumulation is systematized after the fact. Most long-running comic series and long-lived franchises walked this path. A deliberately-designed worldview is one where the world is designed first and the work comes out afterward — projects under the MUOS regime, idol universes built before debut, belong here. Each path carries its own affliction. The affliction of the naturally-arising type is an accumulation of contradictions. In settings piled up for decades without a registration gate, paradoxes sit buried in strata, so the cleanup work becomes equal parts archaeology and surgery: which stratum to dig into and which contradiction to cut out is a judgment call every time. The affliction of the deliberately-designed type is an absence of verification. Filling a world with settings that have never met a reader piles up volume without ever learning what actually works as fun — a library full of stacks with no borrowing record. The remedy is for each to borrow the other's strength. For the naturally-arising type, the remedy is to erect a gate starting now, however late; for the deliberately-designed type, the remedy is to get quick market verification through a small work. The designer must first diagnose which path their own world is standing on. The path determines the first task. The naturally-arising type's first task is auditing and cataloguing; the deliberately-designed type's first task is shipping a minimum-verification product. Apply methodology before diagnosis, and the remedy gets applied backward.

5. Universe Designer: The Conditions for Existing as a Profession

For the job title of the person who takes on this work, I use the term Universe Designer. A title can simply be coined, but a profession has to meet conditions to exist as one. I hold there are three. The first is repeated demand. Work that happens once at one company is a project; only work that keeps arising across many organizations is a profession. Now that IP expansion has become the industry's basic strategy, the repeatability of this demand is being secured — the growing number of worldview-management job postings across both games and entertainment is the indicator. The second is a standardized deliverable. A profession proves itself through the shape of its output. Just as an architect has blueprints and an accountant has financial statements, the Universe Designer needs a system of worldview documents. Without a standard for the deliverable, there is no way to commission it, review it, or quote a price for it. Pay for a duty with no standard is set not by negotiation but by asking price, and trust does not grow in an asking-price market. The third is transmissibility. Work that depends solely on one person's genius is a talent, not a profession. The method has to be organized enough to teach and learn — which is the CT-ization mentioned earlier. Of the three, what is currently scarcest is the second and third. Demand has arisen, but standards and training have not kept pace, so the field keeps hiring people of unproven qualification and putting them to work on bare ground, over and over. The same vicious cycle repeats: success gets credited to individual talent, failure gets blamed on the uselessness of the role itself. This is also why this series keeps digging into standards and method.

6. Separation of Duties: What Splits Off from Scenario Planning

A profession is usually born by cell division from an existing duty. In the games industry, worldview work was for a long time an appendage of scenario planning. A scenario planner would write quest dialogue, then also write regional settings; write item descriptions, then also organize the timeline. There was not even a concept, at that stage, that managing the world was a separate job. When a project is small, this dual role is efficient. The problem appears when scale grows. When a live service runs for years, when a new title inherits the previous one's world, when an IP starts exporting beyond games, managing the world exceeds the scenario workload of a single title. What one person's side duty used to handle turns into infrastructure work receiving reference demand from multiple teams. At that point, the list of duties that split off becomes distinct: setting oversight at the IP level rather than the individual-work level, setting review for new content, supplying worldview material to derivative projects and outside partners, and building and revising the setting-document system. What they share is that all of them continue regardless of any single work's deadline. Assign deadline-bound work and deadline-free work to the same person, and the deadline-free work always gets pushed back. This is the structural reason world management chronically gets neglected in organizations. Separation is not a luxury; it is a step scale forces. It follows the same path by which accounting split off from general affairs and data analysis split off from marketing. An organization that misses the moment to separate ends up looking for a dedicated owner only after the world's debt has piled up beyond what anyone can handle.

7. The Beginner's Compulsion: The Pressure to Use Every Setting

A characteristic side effect appears in the early stage of separated collaboration: a compulsion around settings. A writer handed a thick worldview document easily feels pressure to reflect all of it. Knowing it was expensive to produce, not using it feels like waste, and failing to use it well feels like a lack of skill. The commissioning organization feels the same way — if a prepared setting never appears in the work, it feels as if the investment was never recovered. When both sides' compulsion meets, the worst possible result follows: a work where the story stops and setting introduction begins, a work where the dialogue recites an encyclopedia. Readers did not come to cram for an exam, so they leave. The fate of a work where showing off settings beats being fun is the same regardless of genre. This pressure comes from a misunderstanding about the nature of a worldview document. The document is not a contract that must be fulfilled; it is a storeroom to draw from. A storeroom's value is measured not by its rate of depletion but by whether the thing that was needed was there when it was needed. Start evaluating a storeroom by inventory turnover, and the floor starts pulling out things it doesn't need — and when the same thing happens with a worldview, that is exactly setting recitation. Recall the principle of the wastefully-minted coin: worldview work was, from the start, work that has waste as a required element. That most of what gets made never appears on screen is not failure — it is the normal state. Writing this normal state explicitly into contracts and evaluation criteria is the practical technique that eases the conflicts of the early stage. Replace utilization rate with accuracy of reference as the metric, and the compulsion eases on both sides at once.

8. The Inviolability of Imagination: The Worldview Must Never Obstruct the Writer's Imagination

Translated into the language of a principle, the compulsion problem becomes this: a worldview must never obstruct the writer's imagination. I call this the principle of the inviolability of imagination, and I treat it as the first constraint on design work. A worldview's reason for existing is to help stories be born. But in a world dense with rules and thick with prohibitions, the writer ends up in the position of first hunting for whichever story is still allowed to be written. The order of creation is inverted. The moment the cost of compliance exceeds the gain from creation, the writer works around the world or leaves it, and a worldview that is not referenced is no different from one that does not exist. A world's authority comes not from enforcement but from usefulness. The practical guideline is to reverse the direction of the imperative. A good worldview document is not a list of "do not"s but a list of "here is how things stand." Prohibition is imposed minimally, only at the points where the world's consistency would actually collapse. Everything else is supplied as a description of a state, so the writer can build anything at all on top of that state. "This city bans movement at night" reads like a prohibition, but to a writer it is a state description that hands over a new premise: a story about breaking curfew. Editorial review follows the same principle. The reviewer's question should not be "does this differ from the setting" but "should this change be registered." The first is the language of censorship; the second is the language of management. A writer's departure from the setting is not grounds for punishment but a candidate for updating the world. The principle of inviolability is, in the end, the principle that keeps the world the writer's tool rather than the writer's adversary.

9. The Boundary Between Versatility and Novelty

Keep to the principle of inviolability, and design naturally tilts toward versatility. This is where the tension set aside earlier returns. Versatility is a condition of marketability, not a condition of appeal. Build a world any writer who shows up can use, and it easily converges toward a bland world at the genre standard. A bland world is easy to reference but hard to love. What builds a fandom is always something unique to that particular world. A world faithful to standard is replaceable, and attachment does not form around what can be replaced. Chase novelty alone, on the other hand, and instead of becoming sharper, the world becomes harder to handle. The more original a setting, the higher its comprehension cost, and a world with high comprehension cost can only be handled by a small number of creators — which kills versatility. Worlds that no one can inherit after the original creator's death are the extreme case of this. Design is the search for the optimal point between these two values. The practical trick is to split into layers. Keep the world's foundation close to genre grammar to lower the cost of entry, and concentrate uniqueness into a small number of core settings to build distinctiveness. The goal is not a world that is strange all over, but a world where strangeness is placed exactly right. The reader walks in through a familiar door and is captured in an unfamiliar room. Which setting to seat in the place of uniqueness is the designer's most creative decision, and there is no answer key for this decision. This is why the job never ends at administration alone. Requiring both the discipline of management and the sense of creation within a single duty is this work's difficulty — and also its pleasure.

10. Experimental Collaboration: How to Work with Creators Outside Games

The last problem at the boundary lies outside the organization. In an era when an IP moves across games, webtoons, film, and stage, the designer ends up working with creators who do not know the grammar of the designer's own industry. This collaboration is still uncharted territory with no standard yet. Start with the typical failure. Handing over a thick setting bible whole and saying "reference it as needed" fails almost every time. When the medium differs, the kind and resolution of information needed differs, but the document is tuned to the needs of its original medium. The recipient can't find what they need, and the giver, having handed over everything, is baffled that it can't be used. A film team first needs visual references and character relationships; a stage team first needs symbols and an emotional axis; a game team first needs a system of rules and numbers. So the practical work of experimental collaboration is closer to translation. A per-medium briefing document — the same world curated and repackaged in the target medium's language — works far better than a wholesale handoff. Even if the volume shrinks to a tenth, a document organized in the other side's language gets referenced several times more. Another trick is unifying the point of contact for questions. When an outside creator's setting questions scatter across several people in charge, the answers drift apart from each other and derivative versions get born on the spot, because each respondent answers from a different memory. Route the point of contact to the designer, and feed every answer given back into the document, so that from the next questioner on, the document does the answering. Build a structure where the document grows with every round of collaboration, and each repetition of the experiment moves it closer to a standard. The list of questions from outside collaborators is, in itself, a free audit report showing exactly where the document falls short.