Playbooks: how Jaha runs a meeting

A playbook has a name, a list of prompts (“What did you finish?”, “What’s blocking you?”), how long each person gets, and how many people need to be there for it to be worth running. Attach it to a meeting in the composer under “What Jaha does”, and the run starts as soon as the first person joins. If you pause a playbook, meetings that use it run without Jaha leading.

The plan is locked when the run starts. Editing the template on Tuesday doesn't change what Monday’s standup did, and support can always see the agenda exactly as it was.

In the chat-only moderator role, Jaha announces turns in the meeting chat. As scribe, it takes notes without announcing anything. As host or interviewer, it says the prompts out loud and cuts in when someone runs over. Those two roles need an organization admin to turn on spoken playbooks, and the composer marks them with a “speaks” badge so nobody is surprised in the call.

Jaha waits until enough people are there (plus a short buffer for latecomers), then gives each person their turn in order. A third of the way into a turn, if that person hasn't said anything, it invites them by name, once. Thirty seconds before a turn of a minute or more ends, it says so. Past the limit, it allows a little extra time, gives a nudge, and moves on.

Nobody who couldn't attend is quietly skipped. Jaha puts together their update from the notes they left, and says plainly when they left none. If too few people came, Jaha posts a digest instead of running turns in an empty room.

Every run keeps its outcome: who spoke, who stayed silent, who ran over, and how it ended (completed, digest only, stopped because the meeting ended first, or failed). The meeting page shows this on its Playbook card, and the dashboard counts each outcome separately, so a standup cut short on turn two is never reported as finished.