The author outlines the process of improving internal documentation after a migration from Confluence to Notion in January 2025. Feedback from a developer productivity survey highlighted documentation as a significant issue, with outdated and duplicated content creating confusion. New team members were unsure about their authority to update documents, and the reliance on Notion AI for content access emphasized the need for accuracy over quantity. Limitations within Notion, such as the inability to verify non-wiki pages via API and the lack of archiving features, further complicated the situation. To tackle these issues, the author adopted several policies focused on optimizing documentation for Notion AI and minimizing duplication. They prioritized linking to existing resources in Git over creating new guides and encouraged all team members to participate in keeping documentation up to date. The implementation involved creating two distinct teamspaces for archiving and a weekly script to manage this process. A series of scripts were developed to prune expired pages, compact stale hierarchies, and identify broken links, leading to the archiving of around 1,500 outdated documents. After executing these steps, the author manually reviewed key pages, particularly those related to onboarding, to ensure they were well-organized and linked appropriately. This review process took about eight hours and required no additional time from others. The changes aimed to reduce duplication and improve the overall quality of documentation, making it easier for the team to maintain and access necessary information moving forward.