At which point during product usage were docs consumed?
Was the consumption of docs followed by normal operation?
Did docs help in setting up or configuring a feature?
Is increased docs consumption followed by increased product usage?
Which parts of the documentation proved more useful?
Which gaps exist in the documentation that we could document?
Even though all the previous questions could be answered through user research, or less directly through web analytics or A/B testing, a more efficient, less opinionated approach could be to track the journey of the users through the product and the documentation itself, using techniques such as real user monitoring (RUM) and correlating the resulting data with back-end logs, traces, and metrics. Observability solutions already do this for complex journeys such as adding items to the shopping cart of e-commerce sites, for example, so why not tracking docs usage?"