It’s true, I don’t have much hair to cut. So, I won’t be asking you about my recent haircut, but I do have something new to share.

If I had asked, there’s really only one way to respond to the haircut question.

“Looks good.”

It’s meaningless. Yet, we often find ourselves seeking this sort of feedback.

A few years ago, a major company not known for work with devs relaunched its portal:

The top story on that portal? All about the portal itself.

Something tells me that developers aren’t going to care about their “updated personalized hero area.” 🤦‍♂️

Maybe they’ll like what’s in it. Maybe.

That brings me to the something new I have to share: it’s called the ​Developer Trust Memo​.

It’s not the existence of the Trust Memo that you’ll appreciate. It’s what it will help you to 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 allows for all of 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.

I really do see these as personal messages to you (and yes, a few others receive the same thing). So I’m calling it what it is in order to help people like you build trust with more of the right developers.

As thanks for being here, I want to share ​4 lessons from the field​ (PDF), a new foundational overview of developer trust. 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.

P.S. For the first time, both of my books are ​available in print and Kindle on Amazon​.