3 ms·
> I think if your standup can be async, then it's ineffective, and you should get rid of it. I agree, with one caveat: If you tell engineers that standups can
by PragmaticPulp 7y ago
> I think if your standup can be async, then it's ineffective, and you should get rid of it.
I agree, with one caveat:
If you tell engineers that standups can go async or be cancelled if they're ineffective, they will find creative ways to make the standups ineffective.
Poorly run standups are bad. Standups where the engineers are half-engaged are bad. But having a well-run standup that synchronizes the team, spreads vital information, and keeps people accountable is truly valuable.
However, a good standup requires everyone to put in effort to keep it useful, fast, and on track. If everyone decides that standups are a waste of time, it becomes a self-fulfilling prophecy as the leads have to pull unprepared reports out of each individual, summarize things because people aren't listening to each other, start over because people are arriving late, and so on. If you tell people the standup can go away if it's bad, you've accidentally incentivized those people to make it bad enough to get it cancelled.
- nogabebop23 7y ago>> having a well-run standup that synchronizes the team and this is (I believe) the point of stand-ups. Doing this "async" seems at best weird/hard and at worst impossible. The original post is for a prduct selling async status reporting, which is realy not what stand-ups should be about. If you want to have a daily status report, by all means do it remotely or async or whatever works best. If you want to synchronize the team, well the most obvious and effective way is to actually bring them together in the same temporal space (remote or otherwise). You don't need to do this for problem unblocking or status updates, but don't tell me you're doing a distributed async status update as a method of team synchronization.
- PragmaticPulp 7y ago> The original post is for a prduct selling async status reporting, which is realy not what stand-ups should be about. Exactly. Once you've reduced standups to async individual reports, you lose the team communication benefits. In my experience: Once you lose the team communication benefits, people give it even less thought and energy, so the value continues to decline until the concept is abandoned altogether.
- karatestomp 7y ago> If you tell engineers that standups can go async or be cancelled if they're ineffective, they will find creative ways to make the standups ineffective. What the hell? Have you actually seen this happen? I can't imagine someone jettisoning something that makes their work-life easier and is an extremely low time commitment, just because you tell them they can. I can imagine them changing it to something else if that's more useful and cheaper, time-wise, or getting rid of it if it's of very low utility. Lots and lots of standups are the latter, from the IC's perspective. A lot of "talk to the manager who's the actual audience for the meeting, everyone else dozes off" standups. "Ten people and only two others are actually on my project, and we talk all the time anyway". That kind of thing. Plenty of that out there. I could see them wanting to get rid of those. I mean if people are putting so little effort into the standup that it makes them bad, and the standup is for them, supposedly, then maybe that's a sign it isn't valuable to them? > If you tell people the standup can go away if it's bad, you've accidentally incentivized those people to make it bad enough to get it cancelled. Again, this makes no sense unless from their perspective it already is bad and they just need to convince you it is, too.
- deleted 7y ago[deleted]
- PragmaticPulp 7y ago> What the hell? Have you actually seen this happen? Yes, this is from personal experience. > I can't imagine someone jettisoning something that makes their work-life easier and is an extremely low time commitment, just because you tell them they can. Look at it from a different angle: If you tell people you're thinking about replacing standups with something more efficient, you've tipped your hand that the current situation might be inefficient. Suddenly, people lose interest in participating in the status quo because even management doesn't believe it works, so the quality of preparation and engagement goes down. This creates a self-fulfilling prophecy where the standups become more and more useless over time. On a similar topic: I worked in a department that tried to adopt a version of Elon Musk's famous "If you're not adding value, walk out of a meeting" rule. The people who hated meetings made it a point to not add any value in meetings, so they could get up and leave as soon as possible. This forced everyone else to have followup 1:1s with the people who walked out so they could be essentially re-capture their required meeting participation. > Again, this makes no sense unless from their perspective it already is bad and they just need to convince you it is, too. Two different topics. People can still dislike standups even if they're helpful. A lot employees are drawn to work concepts that reduce their workload at the expense of their manager's. It's less efficient to make a manager play a game of telephone to spread information around than it is to get everyone together for a 15-minute standup, but if someone thinks they can reclaim those 15 minutes and force their manager to bring them any relevant info, it's a net win. In the real world, this becomes an inefficient and lossy system, but it sounds good if all you see is an extra 15 minutes saved in your day.