[operatingthetan]

The process isn't to wait until the next standup. Asking for blockers is the manager's way of ensuring no-one is keeping a blocker from them. A functional team would have devs who float blockers when the arise and most of the time they would answer the question with "no blockers."

[jwagenet]

This is in contention with the usual developer gripe about being interrupted from focus. Sometimes the blocker is your teammate who doesn’t like interruptions. Or a junior has been told to or assumes they need to “figure it out” and wastes a bunch of time instead of asking.

[bluGill]

> a junior has been told to or assumes they need to “figure it out” and wastes a bunch of time instead of asking.

Often you don't even know. More than once I've discovered someone working on a complex problem - they were making progress so didn't realize that someone else already had a solution and so they could save days of effort by asking the right person the right question.

[jwagenet]

Right. My point is there's a cohort of people here who are like "dont bother me, I only check email/slack in the morning, need extended focus time". At least some of those people are the ones who might know a thing or too, but they breed a culture of discouraging even bringing an issue up.