A blog comment asks what a weekly meeting costs, and Atlassian's agenda guide helps answer
A comment on an Atlassian agenda guide raises a good question: is your weekly meeting worth its price? The guide's checklist helps you test that.
The short version
- The item is a reader comment on Atlassian's guide to writing a team meeting agenda, not a news announcement.
- The guide gives 5 tips, including ranking topics by priority and leaving real time for questions.
- It says every agenda needs a goal, a facilitator, a time slot per topic and a date, time and place.
- It advises sending the agenda to everyone at least a day before the meeting.
- Cost test: attendees times hourly pay times meeting length shows what a meeting really costs.
Why it matters
Meetings are one of the few costs most workers control but rarely measure. A simple agenda and a rough cost figure can show whether a recurring meeting earns its slot. The story also reminds you that a comment on a trusted site has not been checked by that site.
A comment, not a news release
Today's item is a little unusual. It is a reader comment posted under an Atlassian blog guide on writing a team meeting agenda. The comment's title is built around what a weekly meeting actually costs a service firm.
From the title alone, we can't tell whether the comment is a thoughtful piece of advice or a plug for something. So we won't judge it. What we can do is read the guide it sits under, as published on atlassian.com, and use it to think about the question the title raises.
That question is a good one. Many people sit through a weekly meeting for years without asking what it costs or what it produces.
What the guide says an agenda is for
Atlassian describes a team meeting agenda as an organized, scheduled list of the topics and action items a team plans to cover. Its argument is that a good agenda is more than a list of topics with times next to them. It takes thought about who is in the room, what they already know, and whether the meeting is meant to solve a problem, brainstorm or reach a decision.
The guide's goal is that anyone skimming the agenda can tell why the meeting is happening, what role they play, and what they need to prepare beforehand. It also says the agenda should go out to everyone at least a day ahead, so people arrive ready and can point out anything missing.
The five tips, in plain terms
The guide offers five tips for building an agenda:
- Tailor it to the meeting. A weekly team meeting might have a slot for wins and shoutouts, while a workshop may not need one.
- Rank the items. Put the most important topic first. If time runs out, the lowest-priority items move to the next meeting.
- Consider an icebreaker. It can set a relaxed tone, but the guide warns that a complex one with 20 people could eat the whole meeting.
- Leave real room for questions. Sixty seconds at the end is not enough. It also suggests asking "What questions do you have?" instead of "Do you have any questions?", since the second is easy to answer with a head shake.
- End on a positive note. A few minutes of thanks, to individuals or the group, leaves people feeling their work was noticed.
The basics every agenda needs
Beyond the tips, the guide lists elements that belong on nearly every agenda. These are the date, time and location (including the time zone and the video link for remote teams), the objective, the facilitator and attendees, the agenda items themselves, and an estimated time for each topic.
It also recommends a short team check-in, so people can mention how they are doing before the business begins. For agenda items, it asks for brevity and no jargon, with a clear note of what the team should accomplish on each topic and what action follows.
Notice how many of these elements are about limits: a stated goal, a time per topic, a lowest-priority pile that can wait. Those limits are what make a meeting cheaper.
Putting a price on the meeting
The comment's title points at cost, and the idea is easy to try. Multiply the number of attendees by their hourly pay, then by the length of the meeting. The result is a rough price for that hour or half hour, and you can compare it with what the meeting produced.
Atlassian's guide admits that a good agenda takes work upfront. Its claim is that the effort is repaid by a more efficient meeting. If you use the cost figure, you can check that claim against your own calendar. A meeting with a clear goal, ranked topics and written follow-up actions is easier to defend than one that exists out of habit.
One caution: we have not seen the comment's own argument, so we can't say whether its numbers or conclusions hold up. The formula above is simple arithmetic you can run yourself.
Treat comment sections with care
This story sits next to a more obvious case. Another comment on a different Atlassian post, about Dropbox and Trello, is a come-on to sign up for free cryptocurrency, which looks like spam. Both show that a comment section on a respected site is not vetted by that site.
If a comment links somewhere or offers something, judge it on its own. The meeting-cost idea costs you nothing to try. A sign-up offer for free crypto should not be clicked.
What to watch
- Whether the comment itself offers useful analysis or turns out to be a plug for a product or service.
- Whether your own recurring meetings still have a clear goal once you write one down.
Try it
Pick one recurring meeting. Multiply attendees by their hourly pay by its length, then check whether it has a stated goal and a ranked list of topics.
Sources and links
First reported by atlassian.com. Written by the SI Agent News Desk from the reporting above.Written with AI from the source above. Every number is checked against the source. Spot a mistake? Corrections.
Liked it? Say why
Add a line for other readers.
No account needed. We never show your email. Comments with links, ads or abuse are held and not shown. Your comment shows after a quick check.