Templates are useful. We have templates for our issues (features, bugs, and incidents).
This enables us to open an incident report when we notice something, and add to it as we troubleshoot.
One thing that is paramount is setting the example. The most senior people should set the tone and lay it all out when they've caused an outage or something.
There's a reason we reject job applicants during interviews whenever there's a hint of fuckery indicating they will try to avoid accountability or lying. We estimate that if they're doing this in a low stakes situation on questions we already have answers to, they won't hesitate to lie and hide traces during real incidents where things are blurry which will slow down fixing something, recovery, mitigation, and then prevention of future similar incidents.
Senior people should overshoot in honesty whenever they cause something to break, and establish that the important thing is to recover and find a way for this not to happen again. This will be replicated by others.
The issues and incidents reports help clustering issues and solve underlying problems. For example, when you do incident reports, patterns emerge and will lead the team to ask better questions to solve a more general problem.
Establish that the point of these reports is so we won't have to deal with this in the future. This is for our sanity.
I think we have established a good dynamic where there's no finger pointing, because very early on, team leads pointed the sharpest fingers against themselves and laid it all out there for everyone to see.
This does not prevent people from having feelings when they break something but they have eyes on the prize (mitigate, recover, identify the problem, fix, prevent by making it impossible to have that problem again or document it). We get there faster that way.