Which Documents Should I Verify?
A few good questions to ask yourself on any document:
- Will someone from another department look at this document for information they need?
- Will this information be used by Sales or Marketing to create customer material?
- Will someone on my team waste time if they use this information and it's no longer accurate? Requirements docs, design docs, FAQs, wiki pages, and debugging instructions are good examples.
If you answer Yes to any of these questions, it's probably a good document to verify and keep up to date.
This isn't a comprehensive guide. Use your judgment about how valuable a document is.
For example:
An engineer can verify a tech plan, so other engineers from different teams can weigh in on the latest decisions, dependencies, or considerations.
A product manager can verify the release notes of a feature, so Sales and Support can use that information with prospective and current customers.
A designer can verify a design proposal, so engineers know it has the latest requirements and designs for a feature they're building.
Respond to verification requests
When someone requests verification on a document you own, or when a reminder to re-verify appears, those documents appear under Knowledge → Verification → Tasks.
From that list, you can verify or deprecate documents.