Example data. Fieldnote is a fictional company used to fill all 61 boards, so the examples tell one consistent story.
Scale-up Fieldnote, the fortnightly 45-minute sync Karim runs with Élise, Nadia, Julien and Tom, same format every time.
What the team took away
Route planning gets asked every sync; writing 'out this quarter' in the decisions column is what finally stopped the question coming back.
How to run it
Preparation
PM plus the 3 to 5 stakeholders who can block or unblock the product. Not their delegates.
Send the agenda 24 hours before, same four headings every time: Agenda, Decisions, Actions, Blockers. Pre-fill the open actions from last time.
Keep the board as one running page. Each session is a new dated block below the previous one, never a new file.
Agenda
10 min
Actions from last time Read each open action with its owner. Done, not done, or dropped. No explanations longer than one sentence.
10 min
Product update PM gives three facts: what shipped, what the numbers say, what changed in the plan. Facts, not a demo.
25 min
Decisions needed Two decisions maximum, prepared in advance with options. Each gets a decision or an owner and a date. Write it in the Decisions block while people watch.
10 min
Blockers Each stakeholder names one thing they need or one thing they can offer. Match them on the spot when possible.
5 min
Close Read the Actions block aloud. Confirm the next date. Post the block to the channel before leaving the room.
Pitfalls
Do not turn it into a status meeting. If nobody made a decision in 3 sessions, cancel the ritual and redesign it.
Do not bring more than two decisions. Stakeholders tire after the second and decide badly on the third.
Do not send the notes the next day. Notes posted after the meeting get read; notes posted the next day get filed.
Afterwards
The running page is the memory of the product's decisions. When a decision gets reopened, link the block where it was made. When the same blocker appears 3 times, run a stakeholder map to check who is missing from the room.