Startup meeting and reporting routines

A dependable operating cadence uses a few routines, each with a distinct purpose: a written status update, a live operating review for exceptions, and a separate investor update that explains progress at the appropriate level.

Give each routine a job

A weekly written update can report what changed, what is planned and what needs attention. Share it asynchronously. A live meeting should then handle decisions that require discussion, such as a blocked launch or an unexpected cash constraint. If there is no decision, trade-off or coordination need, the meeting can be cancelled or shortened.

For an operating review, keep a stable set of measures tied to current goals. Show the period, source and owner of each number.

Discuss changes that require action rather than reading every row aloud. A small team may need only a short check-in; a complex launch may require more frequent check-ins for a time. Frequency should follow the work, not habit.

Keep audiences distinct

An investor update explains business progress, material risks, decisions needing investor input and the next period's priorities. It is not a copy of the internal task board. Internal reporting can contain rough working notes and named owners; an external update needs checked figures, context and clear disclosure of uncertainty. Do not smooth away a missed milestone by changing the definition of success after the fact.

Choose an update format that fits the work

Share an update as a written message or a video message. Asynchronous updates are communication without real-time interaction or an immediate response, so teams can receive information without gathering at the same time.

More than 1,000 Atlassians freed up 5,000 hours for focus work over two weeks after replacing in-person meetings with asynchronous Loom video updates. In the same experiment, direct reports receiving video updates showed a greater increase in reported manager connection than those receiving written Slack updates: 38% compared with 9%.

Assess a reporting routine by more than attendance: it should improve clarity on progress and goals, surface roadblocks early, recognise contributions and protect time for work that requires live discussion.

Impact of Asynchronous Updates in Australian Teams

Make recurring records useful between meetings

A recurring meeting record should bring together the meeting’s purpose, goals, attendees and process with its agenda, notes, decisions and action items. It should also provide a way to carry open actions across recurring meetings, making the record a reference point between discussions rather than a note of a single conversation.

For Australian businesses, a Sprintlaw guide says clear agendas and well-kept minutes can help show how and why important decisions were made, support directors’ duties and reduce the risk of later disputes. This is a governance consideration for important business decisions, distinct from the lighter reporting routines used to keep day-to-day startup work visible.

Record decisions and remove stale meetings

End each live discussion with a short record: decision or unresolved question, reason, owner, due date and people who need to know. A decision without an owner or communication path tends to return as the same discussion next week.

Review recurring invitations regularly. Ask what decision the meeting enabled recently, who needed to attend and whether an asynchronous update would serve the same purpose. Cancel routines whose purpose has disappeared, and reinstate them only when a specific need returns.