|
|
|
|
|
by coldcode
3466 days ago
|
|
At work it is routine for people to create long phone meetings, invite 50 people who all are expected to be online, talk for hour with no decision, plan another meeting for later to talk about it again. People only show up because if they don't they will be blamed for anything that goes wrong which will spawn more unpleasant meetings. The actual decision needed could be done in a couple of Slack messages between two programmers, but the end result is massive wastage of time where no one can get any work done. Because no work is accomplished, more meetings must be held to decide what to do to fix it. Of course as a programmer I am expected to get everything done within a small window of time which of course doesn't include all the meetings, so I have to be masterful of what time I have to avoid being called into meetings about why I didn't get things done on time. |
|
If they had done this for 15 separate projects, 14 times that meeting could actually have been a waste of time, but on the 15th project they saved all this time and they'd still come out net ahead due to the meetings.
What makes this even more pernicious is that there's such a huge discrepancy in possible time wasted, but depending on personal preference it might feel very different to the people involved. For "hacker" or builder types, any meeting at all might feel like a brutal waste of time even if it saves time in the long run, they'd personally rather waste a few days building the wrong thing than sit in a bunch of meetings. But manager types can take this to the other extreme, they feel productive in meetings and end up scheduling too many of them. As always finding a good middle ground is important.