Author Beta
Denne side er maskinoversat og kan indeholde fejl. Rapportér en oversættelsesfejl · Vis på engelsk

Systems and dependencies

Science fiction worldbuilding through systems: map what an invented service depends on, how it fails or delays, and what that does to ordinary people.

IntermediateAbout 45 minutes, plus writingGratisUpdated

By the end: Show how an invented system depends on people, resources and other systems.
Systems and dependenciesShow how an invented system depends on people, resources and other systems.SystemOne inventedserviceInputsPeople, resources,other systemsFailureDelays andbreakdownsConsequenceFelt byordinary people

The idea

Worldbuilding can begin with a dependency chain rather than an encyclopedia. What does a service need to operate? What happens if it is unavailable, delayed, costly or reserved for another use? Include ordinary maintenance and organization without turning every scene into a technical lecture.

A dependency map is a narrative instrument, not engineering validation. When a real scientific or safety claim matters, use domain sources or expert review appropriate to that claim. Avoid operational instructions for hazardous systems in a writing exercise.

Et gennemarbejdet eksempel

The story’s personal-message service depends on an allocation schedule, an audio recorder and an incoming path that remains available after the outgoing slot ends. The last distinction prevents a later reply from contradicting the rule.

Every system needs inputs

An invented service, a relay network, a food printer, a transit pod, depends on people, materials, power and other systems. Science fiction worldbuilding gets convincing when you know those dependencies, because every dependency is a way for things to go wrong.

Map one service: three inputs, two ways it fails or delays, and one consequence that isn’t technical, a missed funeral, a lost job, an argument.

Failures make scenes

Working systems are invisible. A system in your story becomes visible when it delays, fails or is withheld. Those moments are where characters have to choose, improvise or blame someone.

Practise it

Map one fictional service with three inputs, two failure/delay conditions and a nontechnical consequence.

For your own project: World-system map and its narrative constraints.

Common pitfalls

  • Systems that never fail.
  • Technology with no people behind it.
  • Only technical consequences.

Think it through

What must be established if a character receives a reply after their outgoing access ends?

Compare with a suggested answer

That outgoing and incoming access need not share that restriction, or another previously established delivery route. Do not silently change a complete blackout into an outgoing-only limit.

Other answers can be just as good if you can point to evidence in the text.

Your turn

Work here or on paper. What you type stays in this browser until you save it to your Desk.

Fills the boxes with the worked example, so you can see how it saves. Change anything.

What you type here stays in this browser until you save it to your Desk. It’s kept on this device if you leave and come back.

What this saves to your book
  • Your practice, project work and next step, together in Ideas
  • The system as a world entry, with inputs and failures

Saved into your own Desk, encrypted in your browser first. Nothing here is graded; it’s yours to build on.

You’ll need a free account to save. Your answers wait here while you sign up.

Take it with you: Free for everyone. Made in your browser from what you typed above.

AI assistance optional, off

Off unless you switch it on. Ask about the lesson, get a hint, or have your exercise reviewed against this lesson’s checklist. It never writes the exercise for you. Questions and hints send only your question (we add the lesson). A review sends only the answers you copy into the box. Nothing from your Writing Desk or your books is ever sent, and every request shows you exactly what will leave, and to which AI service, before you send it. Don’t include anything private or confidential. Feedback is advice and may be wrong; it never changes your progress, and every lesson can be finished without AI.

Sign in to use AI assistance.

Check your work

These are prompts, not rules. Done when: Your work saved to your Desk, or marked done if you did it elsewhere. Self-reviewed, not graded. Counts toward your certificate of completion.

If you get stuck

If the system seems perfect, ask who would be blamed if it stopped tomorrow. That person is your scene.

Everything you save here is searchable in your Writing Desk and ready to move into a chapter.

Related: Keep a research ledger · Unequal access · All of Science Fiction Writing

Sources and further reading

  1. Writing what you know: 2.1 Building a believable world, The Open University, OpenLearn. Checked Nov 19, 2026. Why believable worlds are built from habitual, everyday detail.
  2. Start writing fiction (free course), The Open University, OpenLearn. Checked Nov 19, 2026. A free university introduction to fiction writing, including genre.

This lesson and its examples are original to Author Academy. Sources are cited for ideas and further reading; nothing is copied from them, and no institution endorses this course. Version 1.