Weekly team standup
Who uses it: Team lead running a 15-minute Monday sync
Date: Monday 09:00 | Attendees: full team (6)
Each person: What I did last week / What I'm doing this week / Blockers
Blockers raised: API rate limit blocking mobile team
Action: Backend lead — raise rate limit cap by Wednesday
Next standup: Monday 09:00
Why this works: Structuring standup notes around blockers rather than status updates means the notes are still useful on Friday — you can check whether blockers were resolved instead of re-reading what everyone was working on.
Client project kickoff
Who uses it: Account manager or consultant starting a new engagement
Client: Acme Corp | Date: Jan 14 | Attendees: 4 client, 3 agency
Project goal: Relaunch e-commerce site by Q2
Decisions: Agency leads UX, client approves all copy
Action: Client — provide brand assets by Jan 21
Action: Agency — deliver sitemap draft by Jan 28
Open: Client to confirm budget for paid media by Jan 18
Why this works: A kickoff note that captures decisions and open items in writing prevents the most common project failure mode: both sides leaving with different assumptions about who is responsible for what.
1-on-1 manager check-in
Who uses it: Manager having a monthly career conversation with a direct report
Date: Feb 3 | Manager: Alex | Report: Jordan
Jordan's wins this month: shipped auth redesign, mentored two new devs
Feedback from Alex: needs to communicate blockers earlier
Jordan's goal for next month: lead the API migration planning
Action: Alex — connect Jordan with senior architect by Feb 10
Action: Jordan — draft migration proposal by Feb 17
Why this works: Writing down the feedback and the goal in the same note creates a shared record both parties can reference — it prevents the common situation where manager and report remember the conversation differently.
Product sprint planning
Who uses it: Product manager and engineering lead planning a two-week sprint
Sprint 14 | Dates: Feb 17 – Feb 28 | Capacity: 32 story points
Committed stories: user notifications (8), search filters (5), bug fixes (6)
Decision: defer analytics dashboard to Sprint 15
Action: PM — write acceptance criteria for notifications by Feb 18
Action: Eng lead — break search filters into subtasks by Feb 18
Risk: design assets for notifications not finalized
Why this works: Including capacity and the reason for any deferral in the notes makes it easy to explain prioritization decisions later — 'we deferred analytics because capacity was 32 points, not 40' is a clear answer.
Sprint retrospective
Who uses it: Scrum master facilitating a 45-minute end-of-sprint retro
Sprint 13 | Team: Platform (5 people)
What went well: CI pipeline speed improved, PR reviews faster
What did not go well: unclear requirements led to two rework cycles
Action: PM — write definition of done before any story enters sprint
Action: Team — block one hour Friday for async code review
Check next retro: did definition-of-done process reduce rework?
Why this works: Retro notes only have value if the actions are checked at the next retro. Writing a 'check next retro' line for each action makes accountability automatic — the facilitator reads it aloud at the start of the next session.
Executive strategy review
Who uses it: CEO or COO running a quarterly business review with leadership
Q1 Review | Attendees: CEO, CFO, CPO, CTO, VP Sales
Decision: increase engineering headcount by 4 in Q2
Decision: pause expansion into APAC until Q3
Action: CFO — revise Q2 budget model by Jan 31
Action: VP Sales — present APAC readiness report in March QBR
Confidential: do not distribute outside leadership
Why this works: Executive meeting notes need to be brief and decision-focused. Long summaries of discussion are rarely read; a list of decisions and owners is reviewed before every subsequent leadership meeting.
