The only feedback I am seeing in this post is how standup should be used to report blocks. I encourage my team to message me when they have questions and not to wait until a sync meeting to report issues. We rarely discuss blockers because those are address in 1:1 or project focused meetings.
It's not async vs sync thing, it's that you're perverting stand-up from a tedious but low-stakes collaborative process (hey, what's everyone working on, who can help me with this quick problem...) to a grueling and ruthless micromanagement process that gives you false metrics to judge your employees by. It's a sign that you don't really care about your people or your team or their morale and just want to find easy numbers to evaluate people by, the engineering equivalent of "you're fired because you clocked in three minutes late four times this year". It's totally irrelevant to the job at hand...
Yeesh, it scares me that there are people like you who actually think this is a good management style. It's not even a management style, it's just petty sadism. Please seriously consider another career, this is not good for anyone on your team. Sorry to be so harsh, but god damn, this is one of the most braindead, heartbreaking, soulsucking posts I've ever seen on HN. Your team deserves a better manager than you.
Why would blockers wait for 1:1s and project meetings? Hopefully those are happening less frequently and should be addressed sooner.
But the in another of your replies you said you want people to contact you directly when there is a blocker rather than wait until the following standup? Those statements seem contradictory.
It sounds like you prefer to micromanage rather than really being Agile and allowing developer autonomy. This approach just frustrates good developers who want to learn enough about the business and the team that they can go directly to the source rather than having a micromanager as a go between too continually slow down the team.
