I think this is as much an issue with your leadership roles than it is with daily stand ups in general. I worked with teams where stand ups are requested & seen

I think this is as much an issue with your leadership roles than it is with daily stand ups in general. I worked with teams where stand ups are requested & seen as important by the team. Personally, I see the aim of stand up to inform the team of work in case it is relevant to them & ask for help if needed. How the leads of the team react determines how good a lead they are. Developers should have enough autonomy to feel they are working well & able to properly investigate, problem solve and design solutions, without affecting the overall efficiency of the team. One of the more difficult aspects of a team lead role is balancing all the different personalities and work preferences in that team. Consider that "toughing it out" might be a desired work practice for some people but for others it's the opposite, it's leaving them struggling for longer than they need/want to be. Stand ups offer a chance to identify those situations, as not every developer will ask for help when they need it. The post stand-up follow up should then considers the individual developer's wishes (e.g. you should be able to ask to tough it out for longer, probably as long as it's not a critical blocker for other work) and that seems to be one of the places your leadership is going wrong.