A weekly operations meeting template for startups

What should this meeting produce?

Founders often receive reports from separate teams without seeing conflicts between them. Sales is pushing orders, operations is overloaded and accounting is waiting for documents. An operations meeting must clarify those conflicts and choose how to coordinate, rather than ending once every department has presented its own update.

The template below suits a small group of accountable leads. The 45-minute duration is a design suggestion, not an effectiveness benchmark proven for every business. For a complex issue, schedule a separate deep-dive with the people directly involved.

Prepare one page before entering the room

Each lead updates previous commitments, metrics that have deviated, a notable risk and the decision where support is needed. For an issue, record facts, impact, options and a recommendation. Unconfirmed figures should be marked rather than presented as facts.

The facilitator selects items requiring the group’s participation. Information-only updates can go in a shared document. If data is insufficient for a decision, the meeting can agree on how to collect it and a deadline instead of forcing a decision based on guesswork.

A 45-minute agenda for your next meeting

The allocation below reserves most time for problems requiring action. Adjust it to the situation; do not achieve a tidy schedule by cutting confirmation of responsibilities.

A minutes template that keeps only what helps action

Each entry should answer: what was decided, on what facts, who is responsible and when it will be reviewed. If the decision changes an existing rule, update the place where the rule is stored; do not leave the information only in minutes that implementers may never see.

If debate remains, record what lacks evidence and who will verify it. Do not record consensus on an issue merely because the group was silent. The authorized decision-maker must confirm the choice and explain the trade-offs.

Hypothetical situation: sales increases orders while operations asks to stop taking customers

Rather than asking which team is at fault, collect data on service capacity, scope sold, timelines and money collected. The cause could be increased demand, commitments beyond the package or a step requiring rework. Those three causes require different responses.

The team considers options such as rescheduling delivery with customer consent, limiting the scope of new sales or adding resources whose costs have been assessed. The authorized owner chooses within their assigned scope. By the end, identify who informs customers and who tracks the effects on timelines, quality and cash.

Measure effectiveness through changes after the meeting

The following week, check whether actions were implemented and the problem diminished. A completed task that does not improve results is evidence for revising the solution. The number of checked-off tasks should not be the sole measure of a good meeting.

After a few weeks, review recurring issues. If the same exception keeps appearing, an SOP, authority matrix or measurement method may need revision. If meetings exist solely to request every minor decision, return to delegation rather than increasing meeting frequency.

From weekly meetings to a management system

The meeting connects management components: priorities need clarity, metrics need reliability, decisions need owners and implementers need resources. If a component is inadequate, use this article series to improve that specific part instead of trying to solve everything in the meeting room.

You can restart with the overview article, choose a template and test it with one team. If you need collaborators in operations, finance or team development, BHKD Connect is a place to explore suitable profiles.

Suggested actions