Story arcs

The narrative arcs behind story-led videos. This sits under the Performance Playbook: the Playbook lists "story" as a container ("drop into a scene mid-moment") but never says what shape the story takes. This file is the how, the same way the confession-list skeleton covers lists and the Breakdown Framework covers thesis videos.

The rules that override any arc

Every story still obeys the house system. Where a beat template and a rule collide, the rule wins.

1. The Hook Engine writes the first line. The arcs below give the shape; they do not give the hook. Front-load the punch, then let the arc unfold from beat two.
2. Vulnerable about the journey, certain about the work (the one rule of the whole plan, see docs/foundation/job.md). Failed attempts and doubt belong to the situation or the journey, never to my craft.
3. Present tense wherever it's true. An unfinished story travels further than a tidy one. Leave the doubt in.
4. Specific markers, real numbers, one exact person. "Insert dream result" becomes a concrete before-and-after with texture, or it doesn't ship.
5. Client stories are authority content, not confession. Anonymise the detail, name roster brands only as credibility, and never let a rescue story read as "clients are usually a mess."

The six arcs

Each arc: the beats, where it fits, the trap to avoid, example reels that run the arc (other creators' - watch them for the shape, not the voice), and a beat-by-beat sketch poured from my own story bank. Sketches are teaching examples, not finished scripts: swap in the true specifics, and run the hook through the Hook Engine, before anything gets filmed.

1. The origin story (who I am, why I do this)

Beats: where it started → the event that knocked me off the path → what I realised → what I changed → the mission, stated plainly (who I help, from what to what).

Best for: the pinned who-am-I, the dyslexia thread, founding By Default. Pillar 02, inspire. Trap: the mission beat is where hype creeps in. One plain sentence, no crusade.

Examples: one · two. Mine to write: 01 Who Am I - Erlen already leans this way, worth mapping against the beats.

Sketch (beat by beat)

1. Where it started: I've spent 15 years building the systems behind creative teams. I built the first one to save myself.
2. The event: I'm dyslexic. At school, words were never a safe place, so I went where they couldn't catch me, behind the screen.
3. What I realised: my brain was never going to hold the detail. So the structure around me had to.
4. What I changed: I started building systems for everything I touched. Then the teams around me started borrowing them.
5. The mission, plainly: that's why my co-founder Syeda and I built By Default, two neurodivergent creatives helping creative teams turn chaos into systems.

2. The war story (the hero's journey, mine or a client's)

Beats: the problem → what it was costing them → what got tried and failed → the thing that actually worked → the result, concrete → why this is the work I now do.

Best for: prove. Anonymised client rescues, the every-other-week revenue slot. This arc is the script shape behind the "Tales from the Rescue" format in docs/foundation/formats.md. The strongest version opens on a real client problem, per the non-negotiables. Trap: the falling-action beat wants social proof; give it one real number or outcome, not a highlight reel.

Examples: one · two · three · four

Sketch (beat by beat)

1. The problem: a brand came to us three weeks before launch with a campaign nobody could actually take part in.
2. What it was costing: the budget was spent, the team was fried, and the launch date wasn't moving.
3. What failed: they'd already tried more meetings, a bigger deck, and a second round of creative. Same wall.
4. What worked: we stripped it back to one participation mechanic, one thing the audience could do in five seconds.
5. The result: it shipped on time and beat the brand's own engagement benchmark.
6. Why this is my work: every rescue I've done starts the same way. The creative was never the problem. There was no system underneath it.

3. The lesson (the shortest arc)

Beats: the setback, stated bluntly → what I tried → what finally moved it → what it taught me.

Best for: educate or inspire inside pillars 02 and 03. The lesson line doubles as the screenshotable line, so write it first and build backwards. Trap: three failed attempts is texture, five is a diary.

Examples: none banked yet. First candidate from my bank, sketched below.

Sketch (beat by beat)

1. The setback, bluntly: one typo, in permanent print, nearly ended my design career.
2. What I tried: I checked harder, stayed later, read every proof three times. For a dyslexic brain, more effort was never going to be the answer.
3. What moved it: I built a proofing system that didn't depend on me having a good day.
4. The lesson: a system is just a promise you don't have to remember. That one idea is most of what I've built since.

4. The pursuit (a goal in progress)

Beats: the goal and where it comes from → the moment I decided to go → where I am right now, doubt included → the invite (come with me, tell me where you're at).

Best for: the meta-journey: building this audience, learning the camera, building the studio in public. This is the purest "present tense, in motion" arc, and the invite half-closes the follow the way the Playbook's pre-sell move does. Trap: the source version sets a public deadline. Only commit to dates I'll actually hold.

Examples: one · two

Sketch (beat by beat)

1. The goal and where it comes from: I've spent 15 years behind the screen. This year I'm building a personal brand in front of it.
2. The moment I decided: the studio's work speaks for itself, but nobody hears it, because I've never been the one talking. That finally bothered me more than the camera does.
3. Where I am now, doubt in: I'm a handful of scripts in. I still delete half my takes. I'm doing it anyway.
4. The invite: if you're building something that scares you a bit, tell me what it is. I'll trade you mine.

5. The turnaround (challenge to victory)

Beats: the doubt or limiting belief → real effort, no results → the turning point → the method, named and broken down → the before and after, concrete.

Best for: dyslexia-to-systems, and any piece that teaches a named framework (designed participation, conversation design), because the method beat is a natural home for one. Educate plus prove. Trap: end on the better way, and aim the doubt at a belief or a situation, never at a named person who doubted me.

Examples: one · two

Sketch (beat by beat)

1. The doubt: my school reports all said the same thing. I'd struggle with anything built on words.
2. Effort, no results: so I worked twice as hard at reading and writing, and stayed the slowest person in the room.
3. The turning point: until I stopped trying to fix myself and started fixing the process instead.
4. The method, broken down: the same three moves every time. Get it out of my head. Give it a shape. Let the shape do the remembering.
5. The before and after: the kid who couldn't trust his own spelling now builds the systems behind teams of 50 making campaigns for Nike and McDonald's. Not because the brain changed. Because the process did.

6. The breakthrough (stuck, then seen)

Beats: doing the "right" things and still stuck → the realisation → the fix, in two or three steps → what changed.

Best for: educate, pillar 03. Conversation design pieces are naturally this shape ("prompting and prompting and still getting generic rubbish, until I realised it's the asking"). Trap: the realisation has to be mine, from real work. A borrowed insight goes in a breakdown with credit, not a breakthrough story.

Examples: one (realisation) · two (realisation) · three (result). Mine to write: 04 Conversation Design - Erlen is close to this shape already.

Sketch (beat by beat)

1. Stuck: I was prompting and prompting, and the AI kept handing me generic rubbish. New tools, new prompts, same rubbish.
2. The realisation: it was never the tool. It was the asking.
3. The fix, in steps: now I brief it like a colleague. What I want, the context it needs, and what good looks like. Three things, every time.
4. What changed: the output stopped being generic the day my asking stopped being generic. That skill has a name, conversation design, and it's the one I'd learn first.

Picking the arc

If the idea is a claim or an analysis rather than events in time, it isn't a story, it's another structure: a Breakdown, a Take, or an Explainer. See 02 Skills/Structures.md. Story is one of those structures; this file is its detail.

The check before filming

Run the finished story through the Playbook's diagnosis checklist and the first line through the Hook Engine's 4-point test, as always. Two extra checks for stories:

• Do the beats escalate? Each beat should raise the stakes or the vulnerability until the turn. If the beats could be reshuffled without anyone noticing, it's a list wearing a story costume.
• Is the turn earned? The realisation or fix has to be specific enough that only I could say it. "I worked harder" is not a turn.