You know that feeling of "we always complain about the same things, but it never gets any better?" Your question is at the heart of making it possible to escape

You know that feeling of "we always complain about the same things, but it never gets any better?" Your question is at the heart of making it possible to escape stagnation and actually evolve the way a team works together. Sharing knowledge isn't just a matter of tooling, but a matter of principle. Because we want the knowledge we share to not just float out there as a "lesson", we want people to use the lessons and act differently what we're actually talking about here is governance (i.e. law!). This might sound heavy. It's not. It's just a change in orientation from "I'm passively sharing this lesson we learned" to "this lesson we learned changes the way we act." There are 3 things to do to shift from "lessons learned" to working agreements: 1. Capture knowledge in the pattern "when this happens, our team will act this way" 2. Adopt a workflow for formally adopting a working agreement – could be a majority vote, consensus vote, etc. 3. Keep that knowledge someplace the team can browse, search, and update (e.g. Confluence, Notion, Google Drive, etc.) If you do this, something magical happens: you'll begin to evolve your knowledge over time. Have a working agreement that didn't quite cover a corner case? Update it! Have a working agreement that was too restrictive? Nuke it! It's no less shift in magnitude as when humanity switched from oral tradition to the written word. And guess what? The written word works much better when you're operating remotely. Our remote team has been operating this way for nearly 5 years at Parabol. It's a common pattern that at the end of every retrospective we have a new working agreement we'd like to adopt. We've even come up with a Slack-based async workflow for adopting them: https://www.parabol.co/blog/async-decision-making-slack https://www.parabol.co/blog/async-decision-making-slack