Live data from Hacker News

Zoom Is Not the Problem – Our Meeting-Centric Workflow Is

blog.nuclino.com

11–20 of 53 posts

Re: Zoom Is Not the Problem – Our Meeting-Centric Workflow Is

#11

It’s a shame because Zoom has good fundamental tech.

Source? All I hear is about how buggy and insecure the platform is. Edit: source, https://www.buzzfeednews.com/article/pranavdixit/google-bans...

For better or worse, it's really easy to get both small and large (i.e., very large -- hundreds of people) video calls going, and it possibly has the best cross-platform support out of every option available right now.

Re: Zoom Is Not the Problem – Our Meeting-Centric Workflow Is

#12
The meeting I find the biggest time waster is the "what I did yesterday, what am I doing today" meetings. Nothing better than sitting on a 45 minutes call while 15 people try to justify their existence to the pm on the fly.

I find a slack channel called #status-updates works wonders. It persists, it's much faster to consume, it's searchable, and you don't have to read it if you don't need to.

Re: Zoom Is Not the Problem – Our Meeting-Centric Workflow Is

#14
Some workflows require synchronous communications. Meetings, in person or virtual, are great for these.

Other workflows work asynchronously. E-mail, IM and the like are great for these.

Post-War America erred on the side of meetings, forcing asynchronous flows into artificial bottlenecks. Silicon Valley seems to have over-corrected, replacing ten-minute meetings with full-day Slack threads.

Trying to force asynchronous flows into synchronous constructs introduces unnecessary delays, as the slowest process sets the pace. It also increases overhead, since resource C is occupied while A and B sync. Trying to force synchronous flows into asynchronous constructs introduces mistakes through mis-communications. It also increases overhead, since an additional layer of verifying everyone got critical information is introduced.

Re: Zoom Is Not the Problem – Our Meeting-Centric Workflow Is

#15

The meeting I find the biggest time waster is the "what I did yesterday, what am I doing today" meetings. Nothing better than sitting on a 45 minutes call while 15 people try to justify their existence to the pm on the fly. I find a slack channel called #status-updates works wonders. It persists, it's much faster to consume, it's searchable, and you don't have to read it if you don't need to.

Two problems immediately stand out here:

- 45 minutes: it should be 5-10 minutes, 15 on a bad day, and literally never 45.

- 15 people: this is probably just too many people in a single standup. Based on my experience, it's quite likely this can be split up into 2-3 teams that can have more autonomy, and meetings like standups will become far easier to run and far more efficient.

Re: Zoom Is Not the Problem – Our Meeting-Centric Workflow Is

#16

> Weekly status updates? Project kick-offs? Quarterly and monthly planning? Retrospectives? All are carried out asynchronously, in the form of structured write-ups in Nuclino. Another criticism of a controversial tech that is actually a pitch for a product. It's a Hacker News staple. Maybe I'm just getting too cynical.

You are not being too cynical. I think just yesterday there was a post about some person complaining about Google Analytics and it was a pitch for their product.

Re: Zoom Is Not the Problem – Our Meeting-Centric Workflow Is

#17

The meeting I find the biggest time waster is the "what I did yesterday, what am I doing today" meetings. Nothing better than sitting on a 45 minutes call while 15 people try to justify their existence to the pm on the fly. I find a slack channel called #status-updates works wonders. It persists, it's much faster to consume, it's searchable, and you don't have to read it if you don't need to.

We do daily status meetings and they are often productive. The thing is, if it's a daily meeting, it should last no more than 5-15 minutes. Also, sounds like you have too many people on the call.

Re: Zoom Is Not the Problem – Our Meeting-Centric Workflow Is

#18

> Weekly status updates? Project kick-offs? Quarterly and monthly planning? Retrospectives? All are carried out asynchronously, in the form of structured write-ups in Nuclino. Another criticism of a controversial tech that is actually a pitch for a product. It's a Hacker News staple. Maybe I'm just getting too cynical.

You are not being too cynical. I think just yesterday there was a post about some person complaining about Google Analytics and it was a pitch for their product.

Yep, that post was likely why just seeing the title of this one made me suspect it was a stealth-pitch.

Re: Zoom Is Not the Problem – Our Meeting-Centric Workflow Is

#19

The meeting I find the biggest time waster is the "what I did yesterday, what am I doing today" meetings. Nothing better than sitting on a 45 minutes call while 15 people try to justify their existence to the pm on the fly. I find a slack channel called #status-updates works wonders. It persists, it's much faster to consume, it's searchable, and you don't have to read it if you don't need to.

Yeah, it's pretty dumb considering that not only is everyone on Slack, but most workplaces already have some system for providing status updates, yet management insists that we repeat to them in person the same info they could easily grab from Jira/Trello/Pivotal/Github.

Re: Zoom Is Not the Problem – Our Meeting-Centric Workflow Is

#20

The meeting I find the biggest time waster is the "what I did yesterday, what am I doing today" meetings. Nothing better than sitting on a 45 minutes call while 15 people try to justify their existence to the pm on the fly. I find a slack channel called #status-updates works wonders. It persists, it's much faster to consume, it's searchable, and you don't have to read it if you don't need to.

"what I did yesterday" -- can't remember

"what am I doing today" -- not sure yet

Post reply on HN