I’m currently working on a big project where I’m updating a beloved client’s documentation site. Docs are interesting because they’re both high value (imagine your churn rate & support load by not having them) and hard to measure, making resourcing for them hard for some people to emotionally justify.
Docs are also very easy to build once & leave to seed. If you write a doc about an integration, expect it to go out of date the moment your integration partner updates their product. Ditto your own product – you’re still building, right? And this all tracks as a distraction, especially in businesses that happen to be resource-constrained.
So in this paid lesson, we’ll talk about what we’re doing with docs, why periodic reassessments are necessary, and what you can do to get your docs back up to baseline.