How We Designed Our Developer Experience Survey

Creating the survey

Design criteria

  1. Get value from the first click. Users drop out of surveys for many reasons. By ordering the questions by importance and capturing every interaction using an analytics tool, we can turn an abandoned survey into one with some value.
  2. Ask the fewest possible questions. This criterion served as a forcing factor to only ask questions that added to our overall measure: developer satisfaction.
  3. Treat each question as critical. It’s tempting to grab your users’ attention and then try and stretch it out as far as possible. With thoughtful design and copywriting we can respect our users’ time; hopefully, they’ll give us their attention next time, too.
  4. Don’t be annoying. Enough said.

The questions:

  1. Sales: how big is your business?
  2. Behavior: what are you busy with right now?
  3. Product: pick the top 3 things you value in integration documentation.
  1. NPS style rating: How likely are you to recommend Braintree’s integration docs to other developers?
  2. Likert scale rating: How satisfied are you with our developer documentation so far?
The Braintree 2019 Developer Satisfaction survey

--

--

--

Design, data and delicious things.

Love podcasts or audiobooks? Learn on the go with our new app.

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Craig Wattrus

Craig Wattrus

Design, data and delicious things.

More from Medium

Product manager’s key stakeholders

Talk About the Growth Skills of Enterprise Product Manager from Three Aspects

Importance of Customer Feedbacks and it’s role to either induce a New player to emerge or help…

Product experience — small details matter