[justanotherguy0]

Psychological safety is so critical.

I'm almost certain you have, at some point in your career, correctly implemented a feature, only for an operations or product counterpart to blame you for some piece of out of scope functionality not being there.

How did that make you feel? Did you alter your behavior to be less helpful in the future? Did you start recording meetings so that you had a source of truth on explicit scope?

If team members think or feel that they "need to cover their ass," that hurts the company's mission, and wastes resources. Worse, it can lead to managers pushing for excessive due diligence, which saps the motivation of ICs.

Blame is ultimately a waste of energy. Every team member is going to make mistakes if they are taking sufficient risks. You can fire people who have a negative contribution level or chronically underperform without leaning on blame.