A faction draft usually goes wrong in one of two ways. Either the writer begins with aesthetics—uniforms, ranks, slogans, banners—and discovers later that the organization cannot actually function, or the writer builds a thirty-page bureaucracy that never creates a useful scene.

A better workflow is iterative. Research gives you questions, the first draft turns those questions into operational rules, review looks for failures and power imbalances, and revision converts the weak spots into story pressure.

The method below borrows research prompts from institutional economics and governance studies without pretending that real-world institutions can be copied directly into fantasy. Elinor Ostrom's work is useful because it directs attention to rules, monitoring, participation, enforcement, and conflict resolution. The World Bank's World Development Report 2017 is useful because it emphasizes function, coordination, commitment, cooperation, power asymmetries, and the fact that institutions operate through actors with unequal influence. Those are lenses, not a fantasy-government template.

Phase 1 — Research the recurring problem, not the costume

Start with a one-sentence operational question:

What recurring coordination problem would still exist if every named leader disappeared tomorrow?

Examples:

  • Who allocates scarce harbor berths?
  • Who certifies magical healers?
  • Who records land claims after a war?
  • Who decides which monster reports deserve an armed response?
  • Who resolves disputes between merchant houses?

Now research the type of problem, not a historical organization you intend to copy.

If your faction manages common resources, read about monitoring and rule compliance. If it arbitrates contracts, research how records and appeals work. If it trains specialists, look at professional organizations, apprenticeships, licensing, and failure handling.

Keep a source ledger with four fields:

Field Note
source book, museum, law, study, archive
useful question what did it make you ask?
context limit where and when did the source apply?
fictional transformation what are you changing?

This prevents research from becoming disguised copying.

Phase 2 — Write the minimum viable institution

Do not draft the constitution. Draft eight operating facts.

  1. recurring problem;
  2. scarce resource or permission;
  3. entry path;
  4. routine decision-maker;
  5. enforcement mechanism;
  6. appeal or dispute path;
  7. institutional memory;
  8. succession mechanism.

If you cannot answer one, mark it as an intentional unknown rather than hiding it under lore.

Then write one ordinary day.

Follow a minor member through a routine task: applying for a permit, requesting funds, reporting a violation, assigning a patrol, certifying a ritual, or entering a record. If the institution only works during wars, coups, and coronations, it is probably still a plot device rather than a system.

Phase 3 — Add people with different incentives

A rule does not act by itself. People interpret it.

Create at least four internal positions:

  • someone committed to the official mission;
  • someone focused on professional competence;
  • someone who benefits materially or socially from the current rules;
  • someone who wants reform without destroying the institution.

Then ask what each person fears losing.

This step prevents “the faction believes X” from turning thousands of members into one mind. It also creates conflicts that do not depend on secret villains.

The World Bank's governance work is a useful reminder here: formal institutional design and real outcomes can diverge when power, bargaining, exclusion, or incentives change how rules operate. In fiction, that means the written charter and the lived institution should not be identical.

Phase 4 — Stress-test one rule

Pick the rule most important to the current story and attack it with five cases:

normal case: the rule works as intended.
scarcity case: demand exceeds resources.
elite case: a powerful person wants an exception.
ambiguity case: facts do not fit the categories.
emergency case: the normal process is too slow.

Record who decides, who pays the cost, and what precedent remains.

If every answer is “the leader decides,” you have found a structural weakness. Maybe the leader really is that central; if so, the faction should also show the delays, information bottlenecks, and succession danger created by that design.

Phase 5 — Draft the first story-facing version

Now convert institutional logic into things characters can encounter.

Do not explain the entire system. Choose traces:

  • a fee on a receipt;
  • a badge that determines who can enter;
  • an old form nobody understands;
  • a clerk who knows an informal workaround;
  • two offices that claim overlapping jurisdiction;
  • a waiting period;
  • a ritual oath with legal consequences;
  • a local chapter interpreting a central rule differently.

The reader learns institutions best through friction.

A good draft lets a character predict something: if the protagonist breaks a guild rule, the reader should have enough information to anticipate at least the category of consequence even if the exact outcome remains uncertain.

Phase 6 — Review for power, memory, and resources

Use three review passes.

Power pass

Who can make an exception? Who cannot even get heard? Who benefits when the rules stay complicated? Can a nominally weak office block action because it controls records, certification, or access?

Memory pass

What survives staff turnover? Archives, ritual, debt ledgers, oral precedent, professional training, property, or a shared enemy can all carry institutional memory. Also decide what the faction systematically forgets.

Resource pass

Trace one scarce resource from entry to exit: money, food, licenses, magical fuel, ships, trained investigators, beds, votes, or sacred objects.

If resources appear whenever the plot needs them, the institution is weightless. If one office controls the bottleneck, you have discovered a political center.

Phase 7 — Revision should change consequences, not only lore text

Weak revision often adds explanations without changing scenes.

Instead, change one consequence.

If the guild has an appeal process, show a character choosing whether the delay is worth it. If local chapters interpret the charter differently, make route choice matter. If inspectors are punished more for missing a catastrophe than for delaying harmless people, let that incentive shape an encounter.

Revision is successful when the institution changes what characters can do, not when the encyclopedia becomes longer.

Phase 8 — Run a contradiction audit

Before freezing the faction, compare five pairs:

Claim Audit question
mission vs incentive do rewards push members away from the stated mission?
central rule vs local practice where does implementation differ?
authority vs capacity can the office actually do what the law says?
punishment vs monitoring how would violations be discovered?
succession vs continuity what survives a leader's death?

A contradiction is not always an error. It becomes useful when it is intentional and produces consequences.

Phase 9 — Keep a change log

For collaborative projects, record institutional changes like software changes.

Each change should include:

  • what changed;
  • why it changed;
  • which scenes or characters are affected;
  • whether old material becomes invalid;
  • whether the change is public knowledge inside the world.

This is especially important for long serial projects where one faction appears across novels, games, websites, or reference material.

A 60-minute version of the workflow

When time is short:

10 min: define recurring problem and controlled resource.
10 min: fill the eight operating facts.
10 min: create four internal incentive positions.
10 min: stress-test one important rule.
10 min: draft one ordinary scene.
10 min: audit power, memory, resources, and contradictions.

That is enough to produce something usable. Research can then deepen the parts the story actually needs.

What can change the workflow? A four-person secret cell needs less formal structure than an empire. A hive mind may truly have unified preferences. A deliberately surreal institution may not need transparent rules. The method is most useful when the audience should be able to infer how an organization behaves under pressure.

A useful revision rule: remove a rule before adding three more

When an institution feels thin, writers often add more offices, ranks, exceptions, and terminology. Try the opposite first. Remove one rule and ask what breaks.

If nothing changes, the rule was probably decorative. If several scenes become impossible, you have discovered that the rule actually carries structural weight. If one group suddenly becomes much more powerful, you have found a hidden dependency.

This subtraction test is especially useful after research. Research naturally produces more material than the story needs. The job of revision is not to preserve every interesting fact; it is to select the smallest set of institutional mechanisms that produce the desired behavior.

For each retained rule, write one sentence beginning with: “Because this rule exists, a character must…” If the sentence cannot be completed with an action, cost, delay, permission, or risk, the rule may belong in background notes rather than the active story.

Handoff test for a second writer

If another writer, designer, or game master must use the faction, give them only one page and ask them to answer three scenario questions: who handles a routine dispute, what happens when a powerful outsider asks for an exception, and what survives when the leader disappears.

If their answers match the intended logic without additional explanation, the institution is portable. If every answer requires you to explain unwritten assumptions, those assumptions belong in the shared document.

Sources

Related Reading