Week 05 · 22 March 2027 · Tutorial

Anecdote Roleplay

Paired question-and-answer, rotating, with an observer scoring whether the story answered the question that was actually asked.

roleplayThis week's lecture →

Term of the week

the load-bearing anecdote — The one story you have told well enough that it holds up under four different questions without buckling. You need three, not twelve. Preparing is not dishonest; improvising badly is not more authentic.

Three stories, rehearsed until they bore you, is the whole ambition of the week.

What you bring

Rough text for three experiences. Each needs four things written down before you arrive: the situation, the decision you made, what followed, and what you would change. Where one of the four is blank, bring it blank — the blank is the teaching, and filling it in the room with something plausible is precisely the habit being interrupted.

Bring Dossier §5 as well, your Receipt Ledger. An anecdote with nothing behind it is a line item on your plausibility budget, and week 8 is somebody timing how fast they can find it.

The rotation

You work in threes and rotate every eight minutes. One of you asks from a deck of the four question shapes a behavioural interview actually uses. One of you answers, once, without restarting. The third observes and scores exactly one thing: did the story answer the question that was asked, or did it answer an adjacent question the speaker preferred.

That is a narrower brief than it sounds, and it is where the discomfort lives. A well-told story about the wrong thing reads as evasion from the other side of the table. The observer writes the verdict on the sheet rather than saying it, because written critique is what Assessment 3 is assembled from and talk leaves no receipt.

The two failure modes your convenor will interrupt for

  • No decision in it. Things happened and you were present. Nobody can score presence.
  • Someone else’s outcome. The team shipped, the campaign landed, the submission passed. Say what you did, then say what the team did, in that order and in the active voice.

By stream

  • Technical Practice — a failure or debugging story, scored on whether your reasoning under uncertainty is visible. How you narrowed it matters more than what the bug turned out to be.
  • Creative and Communications Practice — a piece that did not work, and what the revision cost in hours, scope or goodwill. The cost is the part people remember.
  • Commercial and Public Practice — a decision made on insufficient information, and who it affected. Name the group; “stakeholders” is reqspeak and a panel hears it as a dodge.

Leaving with

Dossier §6: three anecdotes, each mapped to the four questions it answers without buckling. Mapped, not merely written — the mapping is what makes any of them load-bearing. The lecture gives you the structure; this room tells you which of your three collapses under a follow-up.

Next week your work goes on a wall. Spend the days between on the artefact, not on the stories.

This week, by stream

Your stream's version

Stream 01 of 03

Technical Practice

A failure or debugging story showing reasoning under uncertainty.

Stream 02 of 03

Creative and Communications Practice

A piece that did not work, and what the revision cost.

Stream 03 of 03

Commercial and Public Practice

A decision made with insufficient information, and who it affected.

Who's running this one

Teaching team