Team rituals are the operating system of engineering teams. The right cadence keeps the team aligned, surfaces problems early, and creates space for growth conversations. The wrong cadence wastes hours per engineer per week. The interview probes whether you understand the operational rhythm of a healthy team.
The core rituals
- Daily standup: short sync (15 min) on what is blocking
- Weekly planning / kickoff: what will we ship this week?
- Sprint review or demo: show what was shipped
- Retrospective: what is working, what is not, what to change
- Quarterly planning: set OKRs, scope priorities
- 1:1s: personal alignment
Standup
The most common ritual, often the worst-executed.
Bad standup: “I worked on X yesterday. I will work on X today. No blockers.” Round-robin status updates.
Good standup: blockers, dependencies, unexpected discoveries. The status update is async (in Slack / Linear) — the live meeting is for what cannot be conveyed in writing.
Format that works:
- Async written update by 9am
- 15-min sync to discuss blockers and surprises
- Skip if nothing is pressing
Planning
Sprint planning (1–2 weeks) or weekly kickoff. The team commits to specific outcomes.
Don’t commit to too much. The team’s effective capacity is 60–80% of nominal — meetings, support work, on-call, surprises eat the rest. Plan accordingly.
Demos
Biweekly or monthly. The team shows what shipped to stakeholders. Builds visibility, surfaces issues early, makes the work tangible.
Demos work best when:
- The team rotates who presents
- The audience includes adjacent teams (PM, design, support)
- Demos focus on impact, not feature list
Retrospectives
The most important ritual for continuous improvement. Common formats:
- What went well, what did not, what to change
- Start, stop, continue
- Sailboat (winds, anchors, rocks, island)
- 4Ls (liked, learned, lacked, longed-for)
The format matters less than the discipline. Run them. Document them. Implement at least 1–2 changes per retro.
Quarterly planning
Set OKRs at the start of each quarter. Mid-quarter review at week 6. End-of-quarter retro on what shipped vs what was planned.
Connect quarterly OKRs to annual outcomes. Connect weekly planning to quarterly OKRs. The team should always know how today’s work maps to the bigger picture.
Death by meetings
Total ritual time should be ≤10% of an engineer’s week. If your team is in 6+ hours of meetings per week of ritual:
- Audit which rituals produce real value
- Move what can be async to async
- Cut what is not working
Adjusting for team size
- 3–5 engineers: can sustain daily standup; weekly retro
- 6–10: daily standup splits into smaller groups; weekly retro
- 11+: sub-team standups; team-of-team weekly sync; biweekly retros
- 20+: ritual rhythm shifts to leads, with the EM running a leads sync
Adjusting for distributed teams
Time-zone-spread teams need:
- Async-first written rituals
- Live syncs only when both/all sides can attend reasonably
- Recordings of live syncs for those who cannot attend
- Avoid “decision-by-meeting” which excludes async participants
The ritual you stop running
Some rituals stop working. Signs:
- Attendance is falling or attention is low
- The same content shows up in async channels anyway
- The conversation is performative — people saying things they think the manager wants to hear
When a ritual stops working, kill it or change it. Don’t keep it out of habit.
Frequently Asked Questions
How do I run standup remotely?
Async written update + a 15-minute video sync. Or pure async if the team is functioning well. Avoid daily 30-minute video standups.
Should I attend my reports’ team meetings?
Sometimes — for context. Don’t hijack. Stay quiet unless asked.
How do I introduce a new ritual without team pushback?
Frame as an experiment (“let us try this for 4 weeks and reassess”). Get input on format. Adjust based on feedback.