Vadīt iknedēļas komandas sanāksmi

Kad izmantot

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.

Pirms sāc

• 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.

Ceļš7 soļi

1. S1

   Collect the inputsaģents

   Pull open tasks and anything past due, goal progress, blockers logged during the week, and the decisions from last week's notes.

   Izdarīts, kad the draft agenda has a source for every item — a task id, a goal id or last week's note.

2. S2

   Draft and circulate the agendaaģents

   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.

   Izdarīts, kad 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.

3. S3

   Chair the meetingīpašnieks

   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.

   Izdarīts, kad the notes contain each decision with an owner and a date, read back to the room before the meeting ends.

4. S4

   Turn decisions into tasksaģents

   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.

   Izdarīts, kad 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".

5. S5

   Update goal progressaģents

   Set each discussed goal's current status and the confidence note from the meeting.

   Izdarīts, kad each goal touched in the meeting shows a status dated today.

6. S6

   Publish the notesaģents

   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.

   Izdarīts, kad the notes are reachable by the whole team, including people who missed the meeting.

7. S7

   Flag the carry-oversaģents

   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.

   Izdarīts, kad the carry-over list is in the notes and next week's draft agenda already contains it.

Pārbaudes — kā zinām, ka izdevās

• 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.

Ja noiet greizi

Ko atstāj katrs solis

1. S1the draft agenda has a source for every item — a task id, a goal id or last week's note.
2. S2the agenda is in the team's hands with the timeboxes visible.
3. S3the notes contain each decision with an owner and a date, read back to the room before the meeting ends.
4. S4every decision in the notes has a task id written next to it.
5. S5each goal touched in the meeting shows a status dated today.
6. S6the notes are reachable by the whole team, including people who missed the meeting.
7. S7the carry-over list is in the notes and next week's draft agenda already contains it.

Ko saglabāt

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.

Kā šī procedūra uzlabojas

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.