An event is not yet a story
An event is a sequence of occurrences. A story is a selected sequence in which choices, constraints, and consequences reveal something.
The Wickersham craft work offers a useful diagnostic. Write two sentences:
This happened: …
This is really a story about a person or group who: …
The first protects factual sequence. The second searches for meaning.
For example:
This happened: a company introduced a stricter approval process after repeated payroll mistakes.
This is really a story about a team that tried to eliminate human error and discovered that its informal exception handling had been carrying information the formal system could not yet see.
The second sentence is not automatically true. It is a reporting hypothesis. It tells you what to investigate.
Problem → Character → Collision
Your recent course gives a reusable narrative frame:
- Problem: What pressure exists before the scene begins?
- Character: Who is forced to act under that pressure?
- Collision: What happens when the character's model, habit, goal, or identity meets reality?
"Character" does not require a celebrity or a heroic protagonist. A supervisor, founder, engineer, customer, regulator, or institution can carry action if their choices have consequences.
The story is not the moral
Do not find the lesson before you find the action.
Suppose you decide in advance that a failure proves "systems matter more than people". Every detail will begin serving that conclusion. You will miss evidence that the system was sound, that incentives were misaligned, that training failed, or that one person did make an avoidable error.
Report first. Interpret later.
One action can contain complex ideas
A single governing action does not require a simplistic story. Complexity can live in any of these:
- mixed motives
- reasonable but conflicting goals
- incomplete information
- changing constraints
- a choice that solves one problem while creating another
- a conclusion that is true only under certain conditions
Unity means one central movement, not one-dimensional people.
Choose the carrier of the story
The science-writing notes add a useful question to ask before you choose a character: what is the smallest concrete unit through which the larger issue becomes visible?
The carrier might be one of these:
- a person whose choices expose the pressure
- a relationship in which competing needs collide
- a place where the larger system becomes physically visible
- an object or tool whose use reveals the process
- a single case that contains the mechanism in miniature
- a system itself, when no human protagonist can honestly carry the action
Do not default to a person merely because narrative advice says stories need characters. A place, institution, process, or recurring event carries some issue stories more honestly.
Move from micro to macro only after the micro can bear the weight
Large ideas often become legible at small scale. A street, one site, one employee's device, one lab bench, or one customer dispute can make a system concrete.
But the small case is not automatically representative. Use this sequence:
- Micro: show the actual case with enough specificity to understand it.
- Mechanism: explain what produced the outcome.
- Comparison: test whether the mechanism appears elsewhere.
- Macro: generalise only as far as the evidence permits.
This sequence protects against a common narrative error: treating one vivid case as proof of a general rule because it makes a good story.