b3126044e8
- Simplify flatten_vault API to return usize instead of MigrationResult struct - Add KEEP_FOLDERS: attachments/ and _themes/ alongside type/, config/, theme/ - Use HashSet for collision tracking in unique_filename - Update wikilinks from path-based [[folder/slug]] to title-based [[slug]] - Clean up empty directories after flattening - Flatten demo-vault-v2: move all notes from type-based subfolders to root - Update smoke tests for flat vault structure - Remove migrate_to_flat_vault from repair_vault (one-time migration only) Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
31 lines
2.6 KiB
Markdown
31 lines
2.6 KiB
Markdown
---
|
|
aliases: ["Weekly Team Sync"]
|
|
Is A: Procedure
|
|
Belongs to: "[[responsibility-team-management]]"
|
|
Cadence: Weekly
|
|
Owner: "[[person-luca-rossi]]"
|
|
---
|
|
# Weekly Team Sync
|
|
|
|
The Monday morning team sync is the operating rhythm of the business. In 30 minutes, [[person-matteo-cellini]], [[person-paco-furiani]], and [[person-sara-ricci]] align on the week's priorities, surface blockers before they become problems, and coordinate across workstreams. Without this weekly touchpoint, a small remote team drifts into silos where everyone is busy but not necessarily aligned. The sync is not for deep discussion — it is for coordination and clarity.
|
|
|
|
## Steps
|
|
|
|
- [ ] Before the meeting: review the team task board and note any items that are blocked, overdue, or newly urgent
|
|
- [ ] Open the sync by briefly recapping last week's key outcomes — what shipped, what slipped, and any wins worth celebrating
|
|
- [ ] Go around the team: each person shares their top 2-3 priorities for the week and any blockers they need help with
|
|
- [ ] Identify cross-team dependencies: does Sara need a draft from Luca? Does Paco need creative assets from Matteo? Surface these and set deadlines
|
|
- [ ] Address the top 1-2 blockers as a group — if resolution requires more than 5 minutes of discussion, schedule a separate follow-up
|
|
- [ ] Review [[measure-task-completion-rate]] trends briefly — are we maintaining velocity, or is the team taking on more than it can deliver?
|
|
- [ ] Confirm the week's key deadlines: newsletter publish date, podcast episode, sponsor deliverables, and any external commitments
|
|
- [ ] Close with any announcements or updates that affect the whole team
|
|
- [ ] Post a written summary of priorities and action items in the shared channel within 30 minutes of the meeting
|
|
|
|
## Notes
|
|
|
|
- Keep the sync to 30 minutes maximum. If it regularly runs over, the agenda is too broad or blockers are not being resolved between meetings. Tighten the format.
|
|
- This meeting is for coordination, not brainstorming. If a topic needs creative discussion (e.g., a new content strategy), schedule a separate session rather than derailing the sync.
|
|
- The written summary is non-negotiable. Without it, half the team will remember different priorities, and alignment degrades within 24 hours.
|
|
- If someone is blocked on something from the previous week, escalate it immediately — a blocker that persists for two weeks is a process failure, not a people failure.
|
|
- Rotate the note-taking responsibility weekly. This distributes the administrative load and ensures everyone is engaged in capturing decisions, not just listening passively.
|