The business case for good documentation to improve developer experience and productivity is solid, and there are several helpful guides describing how to operationalize an effective documentation strategy.
A simple approach that I’ve found works surprisingly well over time is to always respond with a link.
Whenever you get a question, reflect on whether the answer is relatively durable and could benefit more than just the inquirer. If the answer is yes to both questions, take a few minutes to write down your answer in a page instead of as a message, and reply with the link. The additional effort compared to simply replying with the answer directly is minimal, and even less so in these AI-assisted days.
The impact, however, is compounding. Over time you’ll notice that the same questions are frequently resurfaced, meaning you’ll have to write less and instead share links to documentation that’s already available.