Taking risks is healthy. Not being afraid of them and understanding that uncertainty is tremendously present in many development contexts, such as software and hardware, is an important thing to have within your team. Things might not always go as you planned, and I’ll be straightforward with you here: most of the time, they won’t. Understanding the ‘why’ is more important than blaming others and yourself, as well as making you want to avoid future risks. I’m not talking about overcommitment, for example, but about accepting that we cannot refine precisely every single story, that we potentially have a set-based design model in place, and that some decisions can only be taken in a certain moment when developing the product. If your team is always delivering 100% of what has been planned, there is a big chance they have not taken risks at all.