|
Hey Reader, “How do you like my haircut?” There’s really only one way to respond to that question. "Looks good." (Ok, please ignore that I don't have much hair to cut). The question and the response are meaningless. Yet, we often find ourselves seeking this sort of feedback. A few years ago, a major company not known for working with devs relaunched its portal:
The top story on that portal? All about the portal itself. Something tells me developers won’t care about their “updated personalized hero area.” 🤦♂️ Maybe they’ll like what’s in it. Maybe. These sorts of announcements are hard, because they force you to think about what developers care about. And that’s usually not your product. When I relaunched these emails as the Developer Trust Memo, I tried to think about what it helps you accomplish. With these memos, developer marketers, product managers, and developer advocates reach more of the right developers in the right way. Each week, they learn new ideas to implement so their company builds trust with technical audiences. Trust is the foundation that enables all the other good things: signups, usage, and new customers. These valuable insights are based on years of developer engagement experience, analysis of hundreds of developer programs, and plenty of facepalm moments (some from my own actions). The good news is that if you’re reading this, you already get the Developer Trust Memo. You may have received many of the 200+ memos in the last five years. I’ve never wanted to call them newsletters, because they’re not just some collection of links. Going back to the archives, I put together a foundational overview of developer trust (PDF). It shares four lessons from my years of working with developer companies. Please share this with others you think would enjoy receiving the Memo. Even better, go put these ideas into action. Skip the haircut talk and go straight to what it represents: that you take these developers seriously and want to help them be successful.
|
