4 ms·
In my experience meetings should only be: 1) 1 on 1 2) Presentation with questions at the end 3) Roundtable status update (so like 2, but each person taking
by DanielHB 2y ago
In my experience meetings should only be:
1) 1 on 1
2) Presentation with questions at the end
3) Roundtable status update (so like 2, but each person taking turns)
4) 4-person maximum whiteboard to decide on a very specific point agreed ahead of time
- natebc 2y agogreat list of criteria. I'd also add 5) End the moment there's nothing left to cover.
- saulpw 2y agoThose were 4 different types of meetings.
- robertlagrant 2y agoI guess the question is: how do you, say, design a new feature that needs input from more than 4 people?
- SpicyLemonZest 2y agoYou write a design, accept valued but nonbinding comments on it, and then deliver a presentation after which you’ll proceed with the project unless someone vetoes.
- DanielHB 2y agoExactly, also use some kind of design document tool that accepts comments (like Google Docs or Confluence) and try to get people to read and make notes _before_ any meetings.
- MajimasEyepatch 2y agoIt’s often useful to meet individually with each person before the presentation too, especially those people who are likely to throw up roadblocks. Ideally everyone is in agreement before the meeting, and the final decision is essentially a formality.
- Angostura 2y agoI’d like to see you try that when trying to improve a flow at, say, a hospital where that involves separate teams of nurses, lab workers, doctors pharmacists and admin staff.
- robertlagrant 2y agoBut how do you know what to design?
- SpicyLemonZest 2y agoYou intuit it from discussions you've had with users about what they want, and with other developers about what can feasibly be built. If there's some reproducible process to identify good product ideas, I've never seen it in action, and I suspect the software market would look quite a bit different if it existed.
- SoftTalker 2y agoStatus updates rarely require a meeting. If there is a group and they all need to give status updates to each other, a meeting (e.g. a standup) can be an efficient way to do that, but so can a shared document or group email, which have the benefit of being asynchronous. If a team of people need to give status updates to their manager, that should certainly not be a group meeting. Nothing worse than the "status meeting" where you spend 5 minutes giving your report and then 25 minutes waiting for the meeting to be over.