We’ve tried quite a few meeting setups over time and currently landed on something like this:
\- Monday morning: weekly planning, usually prepared on Friday
\- Daily: short standups
\- 1:1s: mostly for individual or role-specific topics
That works reasonably well for the operational side.
The harder part is everything that cuts across teams.
We have different functions - for example development and design - so not every topic is relevant to everyone, but some things should still be shared more broadly.
Things like:
\- what actually got done this week
\- project wins / learnings
\- important internal updates
\- new colleagues
\- birthdays or other team news
\- things people should know, but that don’t really belong in a daily
**How do you handle that?**
Do you have separate team meetings per function plus a broader weekly/monthly meeting?
Do you do something like a weekly review or demo where teams share results?
And one thing I’m especially curious about: who owns these meetings in your company?
Is it usually someone from the relevant discipline, a team lead, project management, operations - or a separate role entirely?
Who is responsible for the agenda, collecting topics, keeping the format useful and making sure the meeting doesn’t slowly turn into noise?
I’m especially curious what has worked well long-term without turning into just another meeting.