Blog posts of section strategies
We need to validate the results of our strategy reviews (#379 (closed)). During the OKR review discussion, we decided to try measuring public response to the strategies via a blog post. But rather than just measuring page views, let's add a survey to the bottom of the post which asks a simple question like "Would you recommend this strategy? Rate 1 to 5." Maybe a better question would be "If we execute on this strategy, how likely would you be to use GitLab for this category?" It's critical that we also have space for free-form reasons why they picked that number. This can help drive iterations of the strategy. If necessary, we could tweak the strategy and re-publish.
Sid suggested not measuring it like an NPS though, because the average is not the important part. If we get 100+ people rating it at
5, then we consider it a successful strategy. It doesn't matter how many people dislike it; it just needs to resonate with a sufficient number of people. We've never done a survey or blog post like this before, but it seems worth trying.
We'll start by testing the section strategies because they've had the most focus so far. We can consider posting about industry categories (Project Management, CD/RA, AST, and VSM) later.
The content will all be on our direction pages, so the blog post is just a copy of that content. I propose we copy the content rather than point to it because a) only a portion of the page is relevant and the pages are way too long/cluttered without condensing it a bit and b) this provides a snapshot in time post. We will, of course, link to the source documents so people know where to go for evergreen content.
- Should the blog post only include the 3-year strategy section, or the 1-year plan as well? Decoupling would help measure effectiveness better, and we can always point people to the direction page for the 1-year plan. => I believe both the 3-year strategy and 1-year plan are necessary to understand the direction, so let's do them together.