Writing documentation is always a must for me when I’m developing a feature or new solutions. Spending time on documentation is usually beneficial in the long run. I used to write them in my company’s document systems such as ClickUp, Confluence, markdown in README files, etc.
Here’s a true story about the importance of documentation
We used Clickup to manage tickets, and every team had its own space to receive tasks. Newcomers from other teams often didn’t know where to open a demand ticket for my team. As a result, they frequently asked us, which could take roughly 5 to 10 minutes each time. To avoid wasting time explaining the ticket flow to newcomers, I created a detailed document with pictures on how to properly open tickets for us. After I rolled out my document, a project manager asked one of my colleagues how to create a ticket. I simply passed him the tutorial, and he left to read it. Finally, the ticket was opened correctly without us spending any time explaining it face-to-face, saving us 5 minutes each time. I felt a bit proud of my document since it saved my colleague time, and she was happy(I personally assumed she was happy) that I had written it.