Earlier quoted context omitted.
But you can share your daily status asynchronously as well. This might not scale well to larger teams, but we simply write a short message in a dedicated channel each day. It contains a short status and a few bullet points to plan the next day. Slack makes this conventient because you can write a top level message and then use the reply feature to add more details.
As you said, async doesn’t go well with scale, and async comms is OK if statuses are all you’re gonna write there. But in meetings you get to have back-and-forth, and while you can also have that in async, you’re punishing everyone with having to back-read. Which they might not do altogether. Anyway, I’ve come to really dislike async comms. If something is being communicated to you over async, it’s something not impo…
Sync is even worse at scale. I had the pleasure of attending standups in a 20-person team. It was a nightmare where I said two sentences and then wasted the next two hours of my life listening to things I either know or are unrelevant to me.
>you’re punishing everyone with having to back-read
Great, because skipping three pages of unimportant conversation is faster than skipping 30 minutes of banter between two extrovert UI developers as a backend specialist.
>structural strategy to keep everyone accountable
Sounds exactly like something mid level managers say to themselves. Structural synergy? Keeping people accountable? I just want to work, damnit.