Data-driven strategies are crucial to the success of any developer program. But before we discuss the methodologies for building them, we have to clear up a few misconceptions about what they are and what inputs they require.
First, a plan is not a strategy. A plan is a decision on how to get from point A to point B. You need more content to support developers in your ecosystem, so you come up with a few topics and assign writers to work on them. A strategy takes the bigger picture into consideration, understanding where points A and B come together and how they relate to all other points in the equation.
To develop a strategy, you leverage data, organize it into a framework, and use that framework to build a comprehensive approach to your content that supports your objectives. Initial data can take many forms depending on what’s available to you. In-depth metrics, advanced statistics, and complex modeling are often not required.
Collecting and Analyzing Data
The data you collect to inform a developer program isn’t just numbers. It gives you an informed picture of the broader landscape your program will exist in, as well as an early indication of the needs and preferences of the developers in your ecosystem. It includes both the numerical data pulled from your marketing tactics and the qualitative data collected from your stakeholders.
Here are a few examples of the types of data you can use: