A weekly review that ends with owners

A weekly review can become a tour of every document the team has touched. One person searches chat, another opens a spreadsheet, and the same questions appear again. A smaller agenda helps. The review should end with a few decisions that people can act on, rather than a complete account of everything that happened.

Prepare the work before the meeting

Ask owners to update their requests before the review begins. A status should explain what needs attention now. If a task is waiting, name the dependency. If it is moving, record the next step. If it is finished, describe what changed and whether a customer needs a reply. This preparation makes the meeting easier to follow.

Bring one shared view into the discussion. Keep new feedback, open questions, and work in progress visible in separate groups. The team can then decide what to discuss without opening each original conversation. Links should remain available when a detail matters.

Use three questions

• What changed since the last review?

• Which decision is holding work up?

• Who owns the next step, and when will it be checked?

An owner is the person who makes the next step happen, even when several people help with it.

End by reading the decisions back. Give each action one owner and a sensible review date. Avoid assigning work to “the team” without naming who will follow up. A short written summary is enough when it links to the requests and states the decisions clearly.

The weekly review in Felmio is fictional and uses sample activity. Treat its layout as a starting point. Adjust the cadence and agenda to the size of your team, and remove fields that nobody uses when making a real decision.