2 ms·
Developing a postmortem culture is important to share the lessons learnt from production. For eg. Documenting and sharing the lessons learnt from a SRE perspect
by weekay 7y ago
Developing a postmortem culture is important to share the lessons learnt from production. For eg. Documenting and sharing the lessons learnt from a SRE perspective , a google doc would suffice. Some pointers at https://landing.google.com/sre/sre-book/chapters/postmortem-culture/ https://landing.google.com/sre/sre-book/chapters/postmortem-...
Have seen Wiki being setup and fail and go stale very quickly.
Lots of knowledge and learnings are tribal knowledge.
Sharing tribal knowledge is effective in person or in a non wiki mode especially through brown bags or chapter meetings etc.,
Challenge is not everyone has the time or the energy / enthusiasm to be talking in front of a wide audience.
Never seen one solution working effectively. You need to figure out the best approach based on the team culture and how the organisation is setup. For eg., some teams are hesitant to share knowledge and learnings with other groups - Conways law comes into play. End of the day it is not up to the company to track lessons learnt. It is the job or becomes the job of the person supporting production to a large extent to maintain it for making it easier to do their job. That being said , that knowledge leaves when that person moves jobs & the cycle continues
- HenryBemis 7y agoSimilar to that; Post Implementation Reviews (PIRs), then we adapt the relevant documents (processes, procedures, policies, PM methodology, etc.). Usually on the projects the Sponsor is high enough that can approve/influence the changes in the aforemention documentation. On the side, we have a Wiki where every project has its own page (with user access in place because some semi-sensitive info can be found there).