For any system you build, keep in mind a few general truths: 1) The system isn’t just “the wiki” or “Notion”. The system is composed of both the tools you’re u

For any system you build, keep in mind a few general truths: 1) The system isn’t just “the wiki” or “Notion”. The system is composed of both the tools you’re using AND the habits/expectations of the humans who use them. So, this is not just a matter of buying a tool. Its a matter of choosing tools AND designing a process made of humans habits. 2) The system will get messy and unused unless there is regular attention & time allocated to tidying it. 3) If you want people to do something, recognise and incentivize it. If there is a person who habitually sends out concise notes after meetings, make sure that their performance review recognizes that contribution. 4) A habit has three parts: {:situation, :action, :reward} Example: Situation: At the end of a retrospective meeting, we have learned of a need for a runbook on how to handle a type of automated alert. Action: The team lead updates a runbook and tags a junior engineer to review it for missing context. Reward: The team lead feels satisfaction that they’ve set their team up for future success. They add a bullet point to the notes to use during their next annual review.