Why has dbt Labs's documentation site seen a 30% decrease in daily active users since the latest release of dbt version 1.5?

Introduction

The recent 30% decrease in daily active users (DAU) on dbt Labs's documentation site following the release of dbt version 1.5 is a critical issue that demands immediate attention. This significant drop in user engagement could have far-reaching implications for product adoption, user satisfaction, and ultimately, the company's bottom line. To address this problem, I'll employ a systematic approach to identify, validate, and resolve the root cause while considering both short-term fixes and long-term strategic implications.

Step 1

Clarifying Questions (3 minutes)

• Looking at the timing, I'm thinking there might be a direct correlation between the new release and the drop in DAU. Has there been any significant change in the documentation structure or content with version 1.5?

Why it matters: This could reveal if the new documentation is less user-friendly or harder to navigate. Expected answer: Yes, there were substantial changes to the documentation structure. Impact on approach: If confirmed, we'd focus on documentation usability and information architecture.

• Considering user segments, I'm curious about the impact across different user types. Have we seen a uniform 30% decrease across all user segments, or is it more pronounced in certain groups?

Why it matters: This helps identify if the issue is universal or specific to certain user types. Expected answer: The decrease is more significant among new users. Impact on approach: If true, we'd prioritize onboarding and introductory documentation improvements.

• Thinking about external factors, has there been any change in our marketing or SEO strategies that might have affected traffic to the documentation site?

Why it matters: This could reveal if the issue is related to discoverability rather than content. Expected answer: No significant changes in marketing or SEO strategies. Impact on approach: If confirmed, we'd focus more on internal factors related to the documentation itself.

• Considering the possibility of technical issues, have we noticed any changes in site performance metrics like load time or error rates since the release of version 1.5?

Why it matters: Technical issues could be driving users away from the documentation site. Expected answer: Some increase in load times has been observed. Impact on approach: If true, we'd prioritize technical optimizations and performance improvements.