A Startup Leadership Cadence Template That Creates Follow-Through

The template in one view

Three forums, each with a different job. The discipline is in the inputs and outputs rather than the agenda: if a forum has no required input beforehand and produces no record afterwards, it will decay into status reporting within a month.

Weekly: run the operating review

Reserve a short weekly forum for commitments, risks, dependencies, and decisions. Start with what changed since last week, then spend the majority of time on the issues that require leadership judgement.

Every outcome needs an owner and a timing commitment. Without both, you have an observation rather than an action.

The most common failure is spending forty minutes on status that could have been read in four. Circulating written status beforehand is not an administrative nicety; it is what makes the forum worth holding.

Monthly: reset priorities and trade-offs

Monthly planning is where leadership checks whether the work still matches the business reality. Review capacity, customer signals, critical initiatives, and any trade-offs that teams cannot make independently.

This prevents the common startup pattern where every priority remains urgent because nobody has formally removed anything.

Insist that the session subtracts as well as adds. A monthly planning forum that only ever grows the list is not planning, it is accumulation, and the team will learn to ignore the priority order within a quarter.

Quarterly: test the operating system

A quarterly reset looks beyond the work itself. Are responsibilities still clear? Is the cadence producing decisions? Are the same risks reappearing because the company has not changed the underlying system?

The result should be a small number of operating improvements, not a large process programme.

A useful prompt: list the three issues that have been escalated more than once this quarter. Recurring escalation is almost always evidence of an unresolved ownership or decision-rights problem, not a people problem.

What to leave out

Status that can be read beforehand does not belong in the room. Neither do decisions that sit squarely with a named functional owner: pulling them into the leadership forum teaches the organisation that ownership is provisional.

Long-range strategy also sits poorly alongside weekly execution. It tends to either consume the session or get squeezed into the last ten minutes. Give it its own time.

Anything that is genuinely a one-to-one conversation should be one. Leadership forums are expensive; the cost of a weak agenda is multiplied by everyone in the room.

Making it stick

Cadences fail quietly. The meeting keeps happening, but the decisions stop being recorded, the owners stop being named, and within two quarters it is a standing update that nobody wants to cancel.

Two mechanisms prevent most of this. First, a visible decision record that is reviewed at the start of the following session, so unmet commitments surface without anyone having to raise them. Second, a named owner for the cadence itself, responsible for the agenda, the record, and the discipline.

The second is where fractional operating support often earns its place early. Someone has to hold the standard while it becomes habit, and that is difficult for a founder who is also the most frequent source of exceptions.

Adapting it to your stage

Under about twenty people, the monthly reset can often fold into the weekly forum once a month, and the quarterly session can be a half day rather than a full one.

Above about fifty, the weekly forum usually needs to become leadership-only, with functional reviews happening one level down. If everyone who wants to attend is attending, decisions slow rather than improve.

The structure holds across stages. What changes is who is in the room and how much of the detail is handled before it reaches them.

What to check in your business

• Weekly meetings have a written decision and action record.
• Written status is circulated before the weekly forum, not presented in it.
• Monthly planning removes or defers work as well as adding it.
• Quarterly reviews address operating design, not only targets.
• Each recurring forum has a stated purpose and a named owner.
• Unmet commitments surface automatically at the start of the next session.