Templates greatly simplify the process of knowledge exchange: it is easier for a specialist to fill in several fields than to invent something from scratch.

But it’s not a trivial task to develop a good template that everyone understands and takes into account the practices of the team, and if you just take someone else’s sample/checklist, you’ll face a constant misunderstanding of how to fill it out.

Let’s say you want to create a post-mortem template.

To get around the resistance and get a good result, get your colleagues involved in the template, collect your own post mortem examples, and get your colleagues together to look at them, and together identify good examples and articulate what’s good about them, and from the examples you get, you can make patterns that all the employees share.

The created templates, of course, are not much needed by experienced employees – but they will help beginners.

Similarly, code design agreements and other best practices can be developed.