After chatting with developers in your community and diving into how they learn, you'll have a pile of notes and data you can use to improve your marketing and DevRel efforts. What do you do with this data? Turn it into insights! One of the tools I use for this
In part 2 of the Uncovering your product's unique insight email series, I teased that having developer chats can help you design better developer experiences. How so? You can ask questions related to how people learn. By doing this, you can start to form a picture of how your developer
In the previous email, I shared how April Dunford says to lead with your unique insight when pitching your product. But how can you uncover insight if you don't really know what it is? Let me share a tip that's worked for us as we work through positioning our open
Ever asked what motivates your community to learn? It's not your product. The reason lives at a higher abstraction than that. Here are some examples: "I think about the future I want to live and then remind myself I can’t show up for others and not be there for
Listen to Kamran read this0:00/0:301× Saying you "have to" create more content because you want to cater to everyone is like saying you "have to" cater to every child's preferences on candy during Halloween. What does that do? It means you're paying for a lot more candy
Listen to Kamran read this0:00/1:211× A developer files a GitHub issue and "solutions it" in the issue. In the end they boldly claim: "Here's what you should do. That should work." Ah... a maintainer nightmare scenario. Close the browser tab. It may solve their problem. It's even
