Live data from Hacker News

How do we make remote meetings not suck? (2018)

chelseatroy.com

21–30 of 113 posts

Re: How do we make remote meetings not suck? (2018)

#21

stop having them and rely largely on email for communications that should in fact be email.

Okay, this may sound nuts but I think the only issue with your proposal is that it doesn’t address the reason that this doesn’t happen. Our colleagues do not or do not want to read business communications for the purpose of comprehension for the content of their own work or communication with their colleagues. I genuinely propose a three strike policy where professional employees are to be fired after three occasions…

> I’ve tried to right this “meeting should be an email” battle but the reality is shocking: nobody reads anything, for the most part, and when they do, they act like they didn’t.

Exactly. "This meeting could have been an E-mail" is only true if people read and respond to their E-mail. I usually will try E-mail first, but if I don't get a response or if the expected action is not taken--I sigh and break out the meeting invite.

Re: How do we make remote meetings not suck? (2018)

#22
> if the goal is instead to deliver info to the attendees, your meeting should be an email

If we just stuck to this rule I would have hours of more time to do actual work.

So many “meetings,” are listening to folks um-and-ah their way through their slides. They read the exact text they wrote. Slowly. It’s painful.

Just send an email.

If this happens in recurring meetings, make an email digest.

Re: How do we make remote meetings not suck? (2018)

#23

Earlier quoted context omitted.

Same. I searched a bit online but it doesn’t seem to be a well established term

[flagged]

Caucus is also one of two ways state branches of political parties can nominate a person to be a candidate for election (the other being a primary).

The author likely lives in a state where such a thing happens (both parties use primaries where I live, but the term is not unfamiliar at all).

https://th.usembassy.gov/primaries-caucuses-differences/

You might want to tone down the hyperbolic aggression. It isn't the author's fault for using a word in a fitting analogy just because you're not familiar with it.

Re: How do we make remote meetings not suck? (2018)

#24

stop having them and rely largely on email for communications that should in fact be email.

Okay, this may sound nuts but I think the only issue with your proposal is that it doesn’t address the reason that this doesn’t happen. Our colleagues do not or do not want to read business communications for the purpose of comprehension for the content of their own work or communication with their colleagues. I genuinely propose a three strike policy where professional employees are to be fired after three occasions…

> nobody reads anything, for the most part, and when they do, they act like they didn’t.

It's actually even more insidious than a lack of reading comprehension.

It's a lack of retention in memory. People read an email, it blends in with all the other email they read, it lacks salience, it's the metaphorical "in one ear, out the other". Text lacks immediacy so it doesn't get attention, retention, or action.

This is, needless to say, not a solvable problem within any given team, company, or industry.

Edit: The irony of writing this in a HN comment does not elude me.

Re: How do we make remote meetings not suck? (2018)

#25
I appreciate the attempt to bring structure to meetings. I agree structure is necessary, but I feel like the article is committing the same sin that it decries: "rewarding A but hoping for B"

If you blindly rebalance meetings based on "caucus score", you'll get less ideas from the loud people and more ideas from the quiet people ("A"). You won't necessarily get better ideas overall ("B").

IMO, the "floor" should be given primarily to people with a track record of clearly and concisely expressing novel and good ideas, no matter how loud or quiet those people are. Figuring out who those people are is hard and probably can't be nicely described in a blog post.

No one has a meaningful contribution for every topic, and most people don't have the self-awareness to know whether their contribution is meaningful or not. Any good meeting structure has to be able to handle that common situation in a safe and healthy way.

Re: How do we make remote meetings not suck? (2018)

#26
The main issue that this gets at is that meeting time is a valuable company resource and a contentious resource for employees and should be managed as such.

People shouldn’t feel free to chime in with half-baked ideas in meetings or call meetings willy-nilly any more than they would play horseshoes with equipment from the supply closet, use the company credit card for grocery shopping, or call in sick to play golf.

What appropriate policies look like probably do vary by company and team but the policy shouldn’t just be that anyone with access to the calendar software can call a meeting or that anyone in the meeting can speak at any time.

Re: How do we make remote meetings not suck? (2018)

#27

Earlier quoted context omitted.

Same. I searched a bit online but it doesn’t seem to be a well established term

[flagged]

This is the third article in a series, and the term is fairly clearly described in a previous article, linked at the top.

Missing that (and thus the question that started this thread) is okay. Your aggression is not.

Re: How do we make remote meetings not suck? (2018)

#28
post #6

This article keeps talking about "the caucus problem", but never actually defines it. I couldn't follow the post at all because every problem kept ending with "but this isn't the real problem, the caucus problem is".

For everyone else who felt similarly, the explanation is in the previous post (linked near the top of the intro). I also found this confusing because the whole intro felt like it was building up to define the concept and explain why it’s a (the) problem. I even googled the term, thinking it may be some term of art I’m just not familiar with. Then I looked back at the intro again, and inferred that it must be pointing back into the post series… just conveying that poorly.

Re: How do we make remote meetings not suck? (2018)

#29
Latency is the killer for me. Both with video calls and even just with cell phone calls. Old school phone calls could be spontaneous and collaborative almost as good as meeting in person, because latency was as close to zero as possible and you could properly hear both people talking at the same time. But the delays and lack of good audio mixing in cell and video-call tech mean it’s impossible to use in the same way. Given the fundamental differences, then, the better solution is to use video calls only for highly structured meetings and to use other tools like chat and email (gasp) for remote collaboration.

Re: How do we make remote meetings not suck? (2018)

#30
It seems to me that the problem isn’t that remote meetings suck but that meetings suck. My writing group meets remotely because (a) covid and (2) one of the members moved to Ohio from Chicago. We manage not to have the issues about people interrupting etc., likely because we (a) care about what we’re doing and (2) actually that caring about what we’re doing really covers it. We do have structure in that we’re workshopping 2–3 stories per session and we have a four-part agenda for each story (aboutness, likes, suggestions, questions). Everybody has done the necessary homework before the meeting (in this case read the stories and written up their notes), but the structure means that we avoid a common workshop trap of everybody just reading their notes to the group and since you know your notes will go to the writer, you don’t need to feel obligated to say everything you’ve written down.

Thinking about this, I can see pretty clearly how this could be translated into work meetings pretty easily and fits with a lot of the other commentary here.

But bottom line, either the meetings will suck or they won’t and what matters is not whether they’re in-person or remote but how they’re run.

Post reply on HN