(no title)
tanvach | 1 month ago
Also conveniently, we also had the calendar data for internal meetings, internal VC software (not zoom) db that logs the participants when they join and leave meetings and employee function db.
I was serendipitously the lead DS for analyzing the effectiveness of the ‘starting 5 minutes past’. After joining and cleaning a lot of the data, the data showed:
1) at the start of the trial, meetings ended on time. Then after few weeks it slip to ending late, negating the usefulness. Other orgs did not see meetings running late. 2) ICs tend to stick around and over run meetings, while managers tend to leave meetings on time. 3) if I remember right, we had a survey data that showed pretty clearly that managers prefer the ‘starting 5 minutes past’ while ICs do not care or have negative sentiment.
The biggest predictor for people who prefer starting late is how crowded their schedules are. Managers tend to have very crowded schedules which means they want a break between meetings, while ICs prefer not having to waste time waiting.
In the end we reverted back to normal schedule. It was just easier for busy people to bounce early.
conductr|1 month ago
potato3732842|1 month ago
That makes 200% sense. A couple or more ICs tend to want to stick around to go off topic or drill down on some thing if they don't have a conflict. People who aren't expressly relevant to that or have a conflict drop at that time.
You're basically seeing the post-meeting hall conversation of the ICs in your data.
carlmr|1 month ago
phantom784|1 month ago
bjackman|1 month ago
I have had a few senior managers (at Google) who ask for all the meetings _they_ attend to start 5 minutes late.
This seems 100% reasonable to me. No need for it to be an org policy. Just a affordance for the people who spend 95% of their working hours in meetings.
I've also had several senior managers at Google who _don't_ do this, but are 5 minutes late for every meeting anyway. This alternative is pretty annoying!
JamesSwift|1 month ago
Even better is they only need to use that method when meetings actually run full time rather than every single meeting they are in
earino|1 month ago
What was really awful, however, was when your calendar was a random mishmash of starts at :00, :05, :30 and :35 :-)
tanvach|1 month ago
RedShift1|1 month ago
JustinAiken|1 month ago
theshrike79|1 month ago
Dunno if people here know this Paul guy, but he wrote about this: https://paulgraham.com/makersschedule.html =)
steve1977|1 month ago
onion2k|1 month ago
- Does it even need to be a meeting? Keeping meetings to things that need 'a discussion or decision', and keeping updates and announcements to chat or email works fairly well.
- Does the meeting give you any value, or do you bring value to it? If both are no they should decline it.
- Is there an agenda with expected outcomes? No agenda and no goal means it should be declined.
- Are you doing something that's a higher priority? Seeing one of my reports in a meeting when there's an active incident in progress gets me asking questions.
- Does the person running the meeting share notes afterwards? One thing I've noticed over the last couple of decades is that people are much happier to skip a meeting if they'll still hear about what happens afterwards. People don't skip them if being in the meeting is the only way to know about what was discussed or decided. I always encourage people to write some notes and share them if they've set up a meeting now.
dataflow|1 month ago
nephihaha|1 month ago
Covid is supposed to have started in October 2019, and no one locked down until nearly six months later.
barrucadu|1 month ago