Hacker News Reader

I really appreciate the second point and the mentioned ideas! That is great advise. I think having everybody write status updates in advance can be a great idea but how do you make sure that does not turn out to be more work than just sharing those updates verbally in the meeting?

View on HN

It's not that it's less work!

By one measure it's "more work" - if you think about the time that each person spends creating their content in advance, vs what they could spend wall clock time talking in the meeting - 30 min meeting can only have thirty minutes of talking - vs N x 10min pre-writing. It's just parallelizable outside of the tiny synchronous need as the mutex is passed, and a better use of everyone's time - you can write the status update any time before the meeting, whenever you have downtime.

Reply on news.ycombinator.com