Up to twenty people, the founder and Slack hold the company together. Above twenty, that breaks. Context goes missing, decisions get re-litigated, focus dissolves. The fix isn't more tools, it's an operating rhythm.
An operating rhythm is a predictable cadence of short meetings and decision points where the company aligns itself. When it works, the founder doesn't have to be in every thread.
Why now
In a small team, rhythm replaces what physical proximity used to provide, you saw each other's screens, overheard calls, knew what was happening. Distributed work, AI tools and growth all accelerate the team but also fracture context. Without rhythm, that context gets reconstructed five times a week on ad-hoc calls.
Weekly rhythm (60–90 minutes a week)
Monday 30-minute kickoff: every member shares three priorities for the week, one blocker and where they need help. No status history, only what will happen in the next five days. Friday 15-minute close: what's done, what slips into next week (and why), one lesson for the company.
Monthly rhythm (90 minutes a month)
Three fixed blocks: 30 minutes on numbers (revenue, pipeline, key operational metrics), 30 minutes on quarterly goals (green/yellow/red, what to do about red), 30 minutes on one strategic decision. Nothing more. If the agenda overflows, that's a signal the weekly rhythm is missing and operations are taking space they shouldn't.
Quarterly rhythm (half a day)
Three questions: three priorities for next quarter, what we stop doing, one experiment we try. This is the only place direction changes, no OKR or strategic re-prioritisation outside the quarterly window. Calm inside the quarter is the biggest gift you can give the team.
Roles in the rhythm
Every meeting has an agenda owner (not necessarily the founder), a note-taker and a timekeeper. Roles rotate monthly. Without an owner, the meeting drifts; without notes, decisions get re-opened; without a timekeeper, 30 minutes become 75.
Rules that keep the rhythm alive
Same time, same format, every week. No slide decks, link to a live document. Written notes within 24 hours (decision, owner, deadline). One owner per item. If someone can't attend, they send an async update. Without these rules, the rhythm dies inside a month and the team falls back into reactive mode.
Common mistakes
Adding meetings instead of removing them (rhythm should replace ad-hoc communication, not stack on top of it). Mixing operations and strategy in the same slot. Leaving notes in people's heads. Five owners on one action. Letting the first skipped session go uncommented, that's when rhythm quietly dies.
What to measure
Number of ad-hoc meetings per week, share of decisions closed in the weekly close, lead time from task creation to completion, count of re-opened topics. After three months we typically see a third fewer ad-hoc meetings, faster decisions, and a team that knows what's expected.
How rhythm survives growth
As the team scales from ten to thirty people, the format stays, the structure changes. Sub-team rhythms take over the weekly cadence, plus one short leadership weekly. The quarterly rhythm stays single, company-wide, it's the only place direction syncs. Without it, sub-teams start building their own version of the truth.
How to start next Monday
Send an invite for a Monday 30-min kickoff and a Friday 15-min close, create a live doc with three sections (priorities, blockers, lesson), agree on one rule: anyone who can't attend posts an update in the doc. Three weeks is enough for the team to feel the shift.
If you'd like help putting it in place and wiring it into Asana and Slack, take a look at our stepface PRO service, or just email us at hello@stepface.com. For ready-made meeting templates and dashboards, see the Weekly Review Kit.