Give Your Weekly Meeting a Reason to Happen
Give Your Weekly Meeting a Reason to Happen
A recurring invitation tells people when to show up. It should also tell them why their time together matters.
A full agenda is not the same as a useful meeting.
You can cover every item, finish on time, and still leave the room without answering the question that brought everyone together. Before improving the agenda, it is worth being clear about what the meeting is meant to accomplish.
That does not mean every conversation needs to produce a decision. A team may need to work through a problem, learn something together or hear concerns that deserve discussion. Those are valid reasons to meet. The important distinction is between choosing a purpose and continuing a routine simply because it is on the calendar.
For an employer, the aim is not to eliminate meetings. It is to make a thoughtful choice about when people need to be together and what deserves their attention.
An update is not always a discussion
Begin by looking at the items you normally cover. Some may simply tell people what happened. Others may require questions, judgment or agreement.
A completed order count, for example, might be suitable for a short written update in a place the team already uses. A disagreement about why orders are waiting may need a conversation with the people who understand the work.
Do not assume a written update will reach everyone just because you posted it. Check whether people have access, time to read it during their working day and a way to ask questions. If they do not, keeping a brief shared discussion may be the more sensible choice.
The question is not “Could this be an email?” It is “What is the clearest, most practical way for these people to understand this information and respond?”
If you change the format, explain what is changing and where the information will go. Removing a meeting without preserving its useful function leaves a different problem to solve.
The agenda should reveal the work
“Operations update” names a subject. It does not tell someone how to prepare.
A more useful item identifies what needs attention. Here is an illustrative contrast:
Broad agenda item: Review delayed orders.
Focused agenda item: Identify what is preventing the three delayed orders from moving and agree on the next action for each.
The second version gives the conversation a destination. People can arrive ready to explain the obstacle, supply missing information or make a decision within their authority.
Keep the supporting material proportionate. If a short summary will do, do not ask everyone to prepare a presentation. Share what participants need to understand the issue, and be clear about any preparation you expect.
It is also worth asking who needs to be involved. Someone may have information essential to the discussion even if they are not usually on the invitation. Others may only need the result afterwards. Review that thoughtfully rather than treating the existing attendance list as fixed.
A useful discussion has room to change your mind
A meeting with a clear purpose should not become a performance of agreement.
If you have already chosen a solution and are only explaining it, say so. If you are asking for input, leave room for that input to affect the answer. People need to understand which kind of conversation they are joining.
During a problem-solving discussion, ask about the part you may not see: “What would make this difficult in practice?” or “What are we missing from the people doing the work?”
Give people a moment to think. Do not treat the first answer as the only answer, or silence as proof that everyone agrees. If someone raises an issue that cannot be resolved in the room, acknowledge it and decide how it will be examined.
You do not have to settle every question immediately. A useful outcome may be recognizing that you lack a key piece of information and agreeing who will obtain it. What matters is distinguishing a real decision from a discussion that has merely run out of time.
The closing minute deserves attention
Before people leave, summarize the result in ordinary language.
For the delayed-order example, that might sound like: “We have an agreed next step for two orders. The third still needs a delivery confirmation. The coordinator will check that today and update the shared record before the afternoon review.”
This is invented wording, not a proposed commitment for your team. The useful features are the distinction between settled and open items, the next action and the agreed update point.
Ask whether that summary matches what people understood. Then put a short record where the affected team can find it. There is no need to reproduce the whole conversation when a clear decision and its next step will do.
After a few meetings in the revised format, ask participants what is helping and what still feels unnecessary. Keep what serves the work. Change what does not.
A weekly meeting earns its place through the conversation it makes possible. When people leave understanding something important, resolving a question or knowing what happens next, you can explain why you asked them to be there.
Further reading: Atlassian’s meeting-audit guide offers a way to review recurring meetings and decide which to revise or replace.
Planning your next hire? Explore Summit Careers’ employer services.





