Shaping a Story — Stakes, Action, Change

P60.story-bank.02 · Audience: guest, it-ml, language-pro · Prerequisites: Mining Your Experience

Mining Your Experience Tell Me About Yourself — the Thread, Not the CV

LLM grading (this page):Real gradingOff — no LLM calls

Two people tell the same incident. The first: "So there was this project, and there were some issues with the timeline, and various stakeholders had different opinions, and eventually we sorted it out." The second: "Two weeks before the launch, our biggest client threatened to walk. I had one week and no authority over the team that could fix it. Here is what I did — and here is the retention clause we've used in every contract since." Same facts. The first is a report; the second is a story, and the difference is not talent — it is three moves that can be learned: establish the stakes, make your actions the spine, land on a change you can point to. This module teaches the three moves and then applies them where they are hardest and most valuable: failure stories and competing-priorities stories.

🗺️ So far you have built: the inventory — a systematic sweep of your own history distilled to an 8–12 story shortlist, each entry tagged with the competencies it can demonstrate. The entries are honest one-liners: real incidents, raw and untold.

In this module you will: the shaping craft: opening with stakes so the listener knows why to care, making YOUR decisions the spine of the middle, and landing on a stateable change rather than a trailing-off ending — plus the trimming discipline that keeps context from eating the story. Then the two tellings interviews lean on hardest: the failure story that stays honest, and the competing-priorities story where the decision is the drama. It closes on a two-rung ladder: shape one of your inventory entries into a full stakes/action/change story, then shape a failure story that owns the failure and lands on what changed.

Step 1 / 6 — Stakes — why should anyone care?

A story earns attention in its first sentence or not at all, and it earns it with stakes: what was at risk, for whom, and why it mattered then — before anyone knew how it would end. "I worked on the annual conference" has no stakes. "Three hundred attendees had paid, and ten days out our venue cancelled" does. Stakes do not need to be dramatic; they need to be concrete — a number, a deadline, a person who would be let down. The listener should finish your opening sentence needing to know what happened next.

ⓘ Concept: Open with what was at risk, sized honestly

stakes = what was at risk + for whom + by when · concrete beats dramatic, honest beats inflated

Why it matters — Stakes are what convert a listener from polite to curious, and they must come first because they are the lens for everything after: the same action reads as trivial or as decisive depending on what was riding on it. The commonest failure is not absent stakes but unstated ones — the teller knew perfectly well why it mattered and forgot the listener wasn't there. State them in one or two sentences, sized honestly: inflating a routine hiccup into a crisis destroys trust faster than modest stakes ever could, because your listener is often someone who can tell the difference. A small stake truthfully told — 'if I got this wrong, a new colleague's first week would be chaos' — is a perfectly good engine for a story.

🗣️ From a linguist's perspective: In medias res

Storytellers since Homer have known to start in the middle of things — the Iliad opens in the ninth year of the war, not with the shipbuilding. Your instinct will be to start where the project started; start instead where the tension starts, and let any truly necessary background arrive later, in half a sentence, once the listener already cares.

✅ Key takeaways

Open with stakes — what was at risk, for whom, by when — in one or two concrete, honestly-sized sentences. Start where the tension starts, not where the project started; the listener should need to know what happened next.
Make your decisions the spine of the middle: first person, active verbs, visible trade-offs. 'I chose X over Y because Z' carries more signal than a paragraph of outcome; 'we sorted it out' hides you from the one question that was about you.
Land on change, never fade out: one sentence of world-change (a number or a durable practice) plus one of you-change (what you have done differently since). Prepare the closing sentence in advance — endings are where improvisation fails.
Trim context ruthlessly: keep background only if the stakes or a decision breaks without it. Draft full, strike every non-load-bearing sentence, and let the listener ask about anything they miss — a story that provokes a question has succeeded.
Failure stories: a real failure with a named cost, the mechanism owned without blame, ending on the changed practice. You are judged on the ownership in the telling, never on the failure itself — and a low-stakes failure carries the full signal.
Competing-priorities stories: stakes are the collision of two legitimate demands, action is the choice and its criterion — including how you told the losing side — and change is both outcomes, with the cost of the slip stated honestly.
That completes the story-bank journey: module 01 swept your history into an 8–12 entry inventory, and this module gave every entry one reusable shape — paired with the answer-architecture track, you now hold both halves of the pillar, the question decoded and the material ready to meet it.

Next: P60 Answer Structure & Storytelling — step back to the pillar

With the inventory from module 01 and the shaping craft from this one, the story-bank track is complete: 8–12 entries, each one a telling away from answering most of what an interview can ask. The pillar's other track — answer-architecture — supplies the question-side of the same craft; the P60 pillar overview shows how the two meet.

Ask the mentor about this module

Ask a question about this content. The mentor explains and grounds its answer in what you are studying; asking is recorded as a learning signal, not a grade.

Images, PDF or text. Kept on this device only.

Keeping your files on this device

Keep a copy of the files I attach, in this browser

Off by default. The mentor always gets your file; this only decides whether your own copy stays here. Copies live in this browser only - they do not follow you to another device, and clearing site data removes them.

Ctrl/Cmd + Enter to send

🎓 Practice ladder

2 graded rungs · ~24 min

Now shape your own material. Both rungs are mentor-graded craft exercises on stories from your real history — and a low-stakes story is always an accepted choice. Rung 1 turns one inventory entry into a full stakes/action/change story; rung 2 shapes a failure story that owns the mechanism and lands on what changed.

Rung 1 — Shape one story (explorer)

Loading exercise…

Rung 2 — The honest failure story (practitioner)

Loading exercise…

Try it yourself

A scratch console for this page's ideas — ungraded, nothing you run here is recorded.

Scratch console

A scratch console with the scientific stack (pandas, numpy, scikit-learn). Runs on the server — no network, resource-limited and measured.

Output appears here.

My notes on this module

Loading your notes...

Where next?

Continue

Tell Me About Yourself — the Thread, Not the CV →

Career Narrative · P61

Go up a level