(Communication tip)
Ask your team to apply the "Rule of Repair" from Unix Philosophy in communication, too.
"Repair what you can โ but when you must fail, fail noisily and as soon as possible."
As a manager, there is a thin line between being pushy and holding people accountable. It's your job to communicate your expectations clearly.
There's a difference between expecting 100% success from the team all the time versus expecting an update if there's a delay or change of plan for any reason.
Make it clear that you're NOT expecting 100% success from team all the time (unless you want to be unreasonable). Instead, you'd like the team to communicate any delays and roadblocks 100% of the time.
Ask the team to repair what they can, but if they fail, ask them to fail as noisily as possible. This way, you can have their back and plan the next steps accordingly.
As a manager, don't punish the messenger delivering the bad news. Otherwise, you'll find that people don't come to you with any failures.
@arpit_bhayani Great thought, empathy is key to success and also food for through for folks in software the effort put in asking the question like upfront research and experiments to back your question shows you put in effort before asking the question. I learned it the hard way.