Mentoring & Coaching
Meeting Cadence Pack
Strategic agendas that keep your team aligned. Consistent rhythm beats chaos every time.
Why Cadence Matters
🎯 The pattern: Predictable meetings build trust. Your team stops wondering "what's this for?" and starts trusting the rhythm. 1:1s = support. Staff = alignment. Stakeholder sync = predictability. Retros = learning.
1. One-on-One (Weekly, 30 mins)
30-minute sync focused on individual growth and blockers
0:00-0:03 | Opening (3 min)
How are you doing this week? (Work, home, energy level. Real question.)
0:03-0:12 | Blockers & Support (9 min)
What's slowing you down? Blocked by someone else? Need help? Decision needed?
📋 Example:
"I'm waiting on the backend team for the API contract. I've asked 3x and haven't heard back. Can you help unblock?"
0:12-0:18 | Wins & Feedback (6 min)
What went well? What could go better? Share one thing they did great. Ask for feedback on you.
📋 Example:
You: "I loved how you handled that production incident. Clear communication, calm under pressure."Them: "I wish we had more clarity on prioritization. Which bugs matter most?"
0:18-0:28 | Growth Conversation (10 min)
What's the skill or career goal this week? Pick ONE focus area (public speaking, system design, team leadership).
📋 Example:
"Your goal was to lead a design review. You did it. What would you do differently next time?"
0:28-0:30 | Wrap (2 min)
Owner & due date: "I'll follow up with the API team by Thursday." (Write it down.)
2. Staff Meeting (Weekly, 45–60 mins)
Your team synchronized on delivery, risks, and decisions
0:00-0:05 | Wins & Recognition (5 min)
Shout out someone or a project. Don't skip this. It sets the tone.
📋 Example:
"Sarah shipped the search optimization work. Response time dropped 40%. That's shipping."
0:05-0:20 | Delivery Status (15 min)
Where are we on roadmap items? What's stuck? Use a traffic light: 🟢 On track, 🟡 At risk, 🔴 Blocked.
📋 Status Board:
🟢 Payments Service
Launching next sprint
🟡 Mobile App Redesign
Waiting on design assets (Friday ETA)
🔴 API Upgrade
Blocked on Infra team. Action: Follow up by EOW.
0:20-0:30 | Incidents & Quality (10 min)
Fires from this week? Post-mortems? Trends? (If none: "All green, keep it that way.")
📋 Example:
"We had 2 incidents this week. Both auth-related. We're doing a focused retro Thursday. Everyone attend."
0:30-0:40 | Decisions (10 min)
What needs a call? Tech debt? Hiring? Re-prioritization? Bring the decision, not the debate.
📋 Example:
Decision: "We're pausing the caching layer work to focus on the mobile app launch."Why: "Mobile = revenue. Caching = tech debt. We'll come back to it."
0:40-0:50 | Learning & Growth (10 min)
Share a tip, paper, or learning. Rotate who leads. Keeps people sharp.
📋 Example:
"I read a thing about observability best practices. Here's what changed my thinking..."
0:50-0:60 | Wrap (10 min)
Owners + due dates. "Who is taking what? When?"
3. Stakeholder Sync (Bi-weekly, 30 mins)
Roadmap, risk, and delivery confidence with execs/PMs
0:00-0:08 | Roadmap Update (8 min)
What shipped? What's coming? Be specific. Dates matter.
📋 Example:
Shipped: "v2.1 (Payments). Live on web + iOS."Next: "Android rollout (2 weeks). Then mobile redesign (4 weeks)."
0:08-0:18 | Delivery Confidence (10 min)
Each major item gets a confidence rating. 🟢 High (90%+), 🟡 Medium (60-89%), 🔴 Low (<60%).
📋 Example:
Payments v2.1
🟢 95% (ready to ship)
Mobile Redesign
🟡 70% (design delays)
Analytics Integration
🔴 40% (2 blockers, needs decision)
0:18-0:28 | Risks & Dependencies (10 min)
What could go wrong? What do you need from us?
📋 Example:
Risk: "Mobile redesign depends on design team. They're at capacity."Ask: "Can we get 1 dedicated designer for 6 weeks?"
0:28-0:30 | Close (2 min)
Owner + due date: "I'll send the updated roadmap by EOD Thursday."
4. Retro (Bi-weekly, 45 mins)
Team learns. Team improves. Repeat.
0:00-0:05 | Setup (5 min)
Whiteboard or Miro: Three columns: 👍 What went well, 👎 What didn't, 💡 Ideas.
0:05-0:25 | Brainstorm (20 min)
Everyone adds sticky notes. Silent for 10 min (thinking time). Read & clarify for 10 min.
📋 Example Output:
👍 Went Well: "Quick incident response", "Good code review feedback"👎 Didn't Work: "Unclear priorities changed mid-sprint", "Too many meetings"
💡 Ideas: "Lock priorities on Monday", "Cancel one recurring meeting"
0:25-0:40 | Pick 3 Actions (15 min)
Vote on the top 3 things to fix. Don't pick 10. Pick 3. Assign owner. Set date.
📋 Example:
1. Lock sprint scope Monday morning (Owner: PM)2. Cancel Tuesday standup (Owner: Me)
3. Code review SLA: 24 hours max (Owner: Tech lead)
0:40-0:45 | Close (5 min)
Check in next retro: "Did we do these 3 things? What changed?"
Master Cadence Table
Copy this to Google Sheets. Share with your team. Own it.
| Meeting | Frequency | Duration | Owner | Attendees | Output |
|---|---|---|---|---|---|
| 1:1s | Weekly | 30m | You (manager) | 1 person | Notes + action items in shared doc |
| Staff | Weekly | 60m | You | Whole team | Decisions, status, owners, due dates |
| Stakeholder | Bi-weekly | 30m | You + PM | Leadership + PM + EM | Roadmap status, confidence ratings, asks |
| Retro | Bi-weekly | 45m | Rotating | Whole team | 3 improvements + owners + dates |
Pro Tips for Making This Stick
- Calendar is gospel: Book these recurring, same time, same day. No exceptions.
- Show up on time: You set the culture. Late = "this isn't important."
- Notes in one place: Same channel/doc every week. Team knows where to find them.
- Owners + due dates: Not "we should fix it." Say "Sarah will fix it by Friday."
- No emergencies in cadence: If something's on fire, pull the cord. But 1:1s and staff are sacred.
- First 2 weeks = awkward: People will overrun time. Gently rein it in. It smooths out.
- Skip if you have nothing: Retro is empty? Skip it. Stakeholder sync green light? 15 min is fine. Respect people's time.
⚡ The magic: Consistency beats perfection. Your team will trust the rhythm more than any one conversation. They'll know: "Monday is staff, Thursday is 1:1, that's where things get decided."
← Back to Blog