people.team-meeting-weekly·version 1.0.0·draft
Run the weekly team meeting
The team meets from a prepared agenda, every decision becomes a task with an owner and a date, and the notes are findable afterwards.
When to use
The standing weekly slot for a team: what moved, what blocks, what is decided. Not for the owner's review of the whole company — use management.weekly-owner-review. Not for the sales pipeline specifically — use sales.pipeline-review-weekly. Not for one-off problem-solving: if a topic needs more than its timebox, book a separate session instead of stretching the meeting.
Before you start
- The slot, the attendees and the chair are fixed; the agent knows who to prepare for.
- Last week's notes exist and their tasks are readable — the meeting starts from them, not from memory.
- The team's goals are in the goals module with ids the agenda can link to.
The trail7 steps
Collect the inputsagent
Pull open tasks and anything past due, goal progress, blockers logged during the week, and the decisions from last week's notes.
Done when the draft agenda has a source for every item — a task id, a goal id or last week's note.
Draft and circulate the agendaagent
Fixed structure: wins and numbers (5 min) · goal progress (10 min) · blockers (15 min) · decisions needed (15 min) · carry-overs and confirmations (5 min). Name an owner per item. Send it to attendees at least a few hours before.
Done when the agenda is in the team's hands with the timeboxes visible.
⛔ An agenda item without a named owner is a wish, not an item — mark it "needs owner" and it goes last.
Chair the meetingowner
Work the agenda against the clock; the chair cuts discussion that belongs in a separate session. Every decision gets: what was decided, who owns it, by when.
Done when the notes contain each decision with an owner and a date, read back to the room before the meeting ends.
Turn decisions into tasksagent
For each decision, create the task in the tasks module (
bc tasks add), set the owner and due date the chair stated, and link it to the goal it serves.Done when every decision in the notes has a task id written next to it.
⛔ "We agreed" with no task is the most common failure of this playbook — no note is closed without a task id or an explicit "no action, decided X".
Update goal progressagent
Set each discussed goal's current status and the confidence note from the meeting.
Done when each goal touched in the meeting shows a status dated today.
Publish the notesagent
Write the notes: attendees, decisions with task ids, blockers raised and who unblocks them, next meeting date. Send the link to attendees and anyone absent.
Done when the notes are reachable by the whole team, including people who missed the meeting.
Flag the carry-oversagent
List tasks from last week still open. Anything carried over twice gets a visible flag and goes first on next week's agenda, or is explicitly re-decided or dropped by the owner.
Done when the carry-over list is in the notes and next week's draft agenda already contains it.
Checks — how we know it worked
- Every decision in the notes has a task id, an owner and a due date (read the tasks module, not the notes).
- No task created today is missing an owner or a date.
- Every agenda item traces to a source from S1.
- The notes link resolves for a person who was absent — ask one, or open them as a non-participant.
- Meeting length is within the timebox; if it ran over, the overrun is named in the notes.
If it goes wrong
| Symptom | Response |
|---|---|
| Meeting ran with no agenda | Record decisions from memory in S4 within the same day, confirm each with the named owner in writing, and fix S2 before the next run. |
| A decision has no owner | The chair names one within 24 h; until then the task sits unassigned and appears as a carry-over in S7. |
| The same item carries over three times | Put it first on the agenda as a decision item: do it, drop it, or split it — not discuss it again. |
| Key people absent | The agent publishes notes plus a "decisions you may veto by <date>" line; silence past that date is acceptance. |
| The meeting turns into a status read-out | The chair moves status to written updates before the meeting and keeps the slot for blockers and decisions only. |
What each step leaves behind
- S1the draft agenda has a source for every item — a task id, a goal id or last week's note.
- S2the agenda is in the team's hands with the timeboxes visible.
- S3the notes contain each decision with an owner and a date, read back to the room before the meeting ends.
- S4every decision in the notes has a task id written next to it.
- S5each goal touched in the meeting shows a status dated today.
- S6the notes are reachable by the whole team, including people who missed the meeting.
- S7the carry-over list is in the notes and next week's draft agenda already contains it.
Evidence to keep
The agenda as sent · the notes with attendees and decisions · task ids created in S4 with owners and dates · goal status changes from S5 · the carry-over list · the meeting start and end times.
How this playbook improves
After every 10 runs ask: what share of decisions got an owner and a date in the room? How many tasks were closed before the next meeting, and which items carry over repeatedly? Did the meeting hold its timebox? A new version changes the structure in S2 or the recording in S4 to fix the worst number, and says so in its change note.
Obligātās sīkdatnes tur sarunu kopā. Analītika ir izslēgta, līdz tu atļauj — tā neliek nevienu sīkdatni un neglabā ierīces identifikatoru.Necessary storage keeps your conversation together. Analytics is off until you allow it — it sets no cookie and stores no device identifier. Ko mēs glabājamWhat we store