We're moving to a four-day work week at Beacon

Re:We're moving to a four-day work week at Beacon by rootusrootus on Tuesday June 07, 2022 @09:31AM (#31654016)

I'm starting to get more militant about zoom calls. Trying to avoid angering people explicitly, but still pushing back as best I can to protect to the team from incessant zoom calls to have conversations that would be faster on slack, and better documented in email. Zoom calls just invite conversation that has to repeated again because 80% of everyone on the call forgot some amount of detail.

[ Parent | on HN ]

Re:We're moving to a four-day work week at Beacon by SkyPuncher on Tuesday June 07, 2022 @01:11PM (#31657332)

> conversations that would be faster on slack

I'm still searching for the golden goose "conversation" that's actually faster on Slack. Sure, a quick back and forth or check in is actually faster.

I have yet to find a meaningful discussion that's actually faster on Slack. It seems like they always drag out as sparsely filled, 45 minute threads. Nearly everyone of these would have been better served by a 10 minute call.

[ Parent | on HN ]

Re:We're moving to a four-day work week at Beacon by bombcar on Tuesday June 07, 2022 @01:47PM (#31657799)

Faster can mean less clock time (Zoom will almost always win) or less “involved” time - each person reads the thread and responds when they have time, which uses less of their time but more clock time.

It can work either way, depends on the type of discussion. Often the best is to hash as much out in chat as you can and then meet to finalize.

[ Parent | on HN ]

Re:We're moving to a four-day work week at Beacon by SkyPuncher on Tuesday June 07, 2022 @01:58PM (#31657943)

The problem is it still requires mental load to switch in and out of that conversation.

You also create inequality on the team since threads rewards the fastest to reply. This is a lot easier to manage on a Zoom call.

[ Parent | on HN ]

Re:We're moving to a four-day work week at Beacon by theonething on Tuesday June 07, 2022 @02:24PM (#31658243)

> still requires mental load to switch in and out of that conversation

In my experience, sitting through a boring meeting while trying to appear engaged is way more mentally draining.

> You also create inequality on the team

Actually, I see the opposite, that video conferencing favors the most extroverted.

[ Parent | on HN ]

Re:We're moving to a four-day work week at Beacon by bombcar on Tuesday June 07, 2022 @02:40PM (#31658438)

All methods can create equality issues, which can be a reason for using a variety.

I’ve noticed that the way Teams “collapses” threads that often the last to reply is the only one read besides the opening post.

[ Parent | on HN ]

Re:We're moving to a four-day work week at Beacon by greedo on Tuesday June 07, 2022 @02:00PM (#31657963)

My company's retention policy deletes emails after 6 months, as well as Teams chat logs. So unless we create docs in Sharepoint (who has time to add another layer of documentation?), everything becomes ephemeral at some point. Like tears in rain...

[ Parent | on HN ]

Re:We're moving to a four-day work week at Beacon by lkxijlewlf on Tuesday June 07, 2022 @09:53AM (#31654314)

> ... and better documented in email.

This, so much. Let's just jump on a quick Teams meeting almost always can be taken care of in an email. And then it's documented and can be referenced and sent to all parties who may need to know that were not included in the "quick" Teams meeting.

[ Parent | on HN ]

Re:We're moving to a four-day work week at Beacon by rhino369 on Tuesday June 07, 2022 @10:05AM (#31654484)

Quick phone calls are often more efficient than emails. For status updates, downloads of information, sure email works. But if you want a back and forth exchange of ideas, talking is often much faster.

[ Parent | on HN ]

Re:We're moving to a four-day work week at Beacon by heretogetout on Tuesday June 07, 2022 @10:32AM (#31654915)

Talking is indeed faster but if you're not recording the result in some document to share with others not on the call there's risk that valuable information will be lost.

[ Parent | on HN ]

Re:We're moving to a four-day work week at Beacon by seti0Cha on Tuesday June 07, 2022 @11:34AM (#31655871)

I'd say talking is best at straightening out misunderstandings. In those cases there's not necessarily any extra information generated. It's kind of like attaching a debugger to your communication stream.

[ Parent | on HN ]

Re:We're moving to a four-day work week at Beacon by bonestamp2 on Tuesday June 07, 2022 @01:34PM (#31657632)

We create a teams chat that is separate from the meeting and document what we agree on in that chat, that way it is documented for everyone who forgets the details by tomorrow morning.

[ Parent | on HN ]

Re:We're moving to a four-day work week at Beacon by rhino369 on Tuesday June 07, 2022 @11:01AM (#31655371)

Good point

[ Parent | on HN ]

Re:We're moving to a four-day work week at Beacon by corrral on Tuesday June 07, 2022 @01:56PM (#31657921)

I hate—hate—when I'm trying to find something in Slack and right where I'm pretty sure it should be I see a marker indicating that a call took place there, often without any surrounding indication of WTF it was about. Fucking hate it.

[ Parent | on HN ]