Need someone to lead product management at your software company? I create software for people that create software and I'm looking for my next opportunity. Check out my resume and get in touch.

Developer Experience Principle 5: Easy to Trust

Freshness Warning
This blog post is over 3 years old. It's possible that the information you read below isn't current and the links no longer work.

Easy to Trust

Trust is paramount in any relationship between a company and its customers. For developers building their products on top of your APIs, it’s even more so. Your ability to deliver directly affects their product. To feel comfortable with your product, it must be Easy to Trust.

You start building this trust in your marketing. Every communication with the developer needs to be trustworthy and honest, and it starts with how you talk about your product. Developers can be less tolerant of marketing over substance. If you say your product can do something, it needs to do it. Not sort of do it, not do it in the future, not do it if they buy this add-on from a partner. It’s fine to communicate futures and possibilities, but make sure it’s clear what’s available right now.

Everything you communicate needs to be honest and straightforward. You need to be open and transparent with developers. A status page for your API is helpful to developers. You can build trust by showing not just the current state of the API, but historical statistics too. Developers will trust your API more if they can judge for themselves how stable your product is.

Developers need to trust that you’ll do the right thing for their users too. They need to trust you’ll protect their users' data. Believe you won’t put things in your error messages that they can’t show to customers. Know that you understand that their users are your users too.

A great example of this is OAuth permissions screens. An API often has end-users authorize your developer’s applications through your login system. The developer’s application is handing over a part of their user experience to you. How you present the login and permissions can have a giant effect on the conversion rate for your developer. Getting this wrong could scare their users away. When asking for permissions, using confusing or overly-broad names could lead people to abandon signup. Or worse, could lead to people giving permissions that they didn’t realize they’d given up.

A developer is going to build part of their business on your product. They need to believe that you’re going to do the right thing for them and their customers.

More about the Six Principles of Developer Experience

Recently Written

Too Big To Fail (Apr 9)
When a company piles resources on a new product idea, it doesn't have room to fail. That keeps it from succeeding.
Go small (Apr 4)
The strengths of a large organization are the opposite of what makes innovation work. Starting something new requires that you start with a small team.
Start with a Belief (Apr 1)
You can't use data to build products unless you start with a hypothesis.
Mastery doesn’t come from perfect planning (Dec 21)
In a ceramics class, one group focused on a single perfect dish, while another made many with no quality focus. The result? A lesson in the value of practice over perfection.
The Dark Side of Input Metrics (Nov 27)
Using input metrics in the wrong way can cause unexpected behaviors, stifled creativity, and micromanagement.
Reframe How You Think About Users of your Internal Platform (Nov 13)
Changing from "Customers" to "Partners" will give you a better perspective on internal product development.
Measuring Feature success (Oct 17)
You're building features to solve problems. If you don't know what success looks like, how did you decide on that feature at all?
How I use OKRs (Oct 13)
A description of how I use OKRs to guide a team, written so I can send to future teams.


What I'm Reading


Adam Kalsey

+1 916 600 2497


Public Key

© 1999-2024 Adam Kalsey.