This is my preferred method as well when leading a team. Standups as intended are too brief to discuss the important details. This is why they end up ballooni

This is my preferred method as well when leading a team. Standups as intended are too brief to discuss the important details. This is why they end up ballooning to 30+ minutes at most companies, because anything shorter is of little value. They also end up as a catch-all meeting for any topics that require the team's input; I dislike this because people are expected to provide input on the spot without really making any thoughtful considerations. If we want to have a discussion on a UI component, that should be done in a dedicated, prepared meeting, not at 8:30 in the morning when people are unprepared and said developer can take advantage of unpreparedness to obtain the consensus they want. When I provide up-stream status reports, I like to have the developer's notes in front of me for a quick refresher. Plus, they serve as a good reminder on topics that need followup.