Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Get to Know Your User for a Better API

November 02, 2017

Get to Know Your User for a Better API


November 02, 2017

Other Decks in Technology


  1. This Talk 1. What’s a good API? 2. How we

    can change the API process to make our APIs better | @ashmchang
  2. Creating an API looks something like... 1) Users request an

    API 2) You decide its worth engineering time to make an API (but not that much time) 3) Find the simplest way to expose the necessary endpoints 4) Write some docs 5) ! ! ! | @ashmchang
  3. Scaling your API → API users increase → Types of

    users on your API increases → They need more help Instead of an easy win, time is sucked into supporting partners on your API | @ashmchang
  4. Let’s take this for a spin → Start by getting

    to know our user → Expose endpoints in a way that makes sense for them → More time up front, less time writing docs & supporting users later | @ashmchang
  5. How to get to know your users 1) Talk to

    users 2) Make it usable 3) Make it stick | @ashmchang
  6. Why talk to users → Perspective. How you feel might

    not be how other people feel. → Refine the problem. A good solution comes from a clear understanding of what the problem is. → Insight. What workarounds have people created? How successful is your solution? Users are experts on the problem, not the solution | @ashmchang
  7. Interview Plan → Goal: What are you trying to learn

    about? → Target Audience: Define your target audience → Hypothesis on the Audience’s Goal: How & why the audience is using your API. → 5 questions: These should evaluate if your hypothesis is right or wrong. They are starter questions. | @ashmchang
  8. Tips → Record it, if possible (take good notes if

    not) → Make participants feel comfortable → Use active listening techniques to focus their thoughts without leading → Pay attention to body language → Let it be organic | @ashmchang
  9. Reaching People → Talk to inbound people → Send out

    emails → Use pop-up options in the service → Rewards → Set up a qualifying survey | @ashmchang
  10. Starter questions → How did you find our API? →

    What do you do at [their company]? → Who from your team spends the most time with our API? → Did you already use something that does the same thing? → Can you tell me about a specific time our API has helped your team? | @ashmchang
  11. Goals You want to understand: → motivations → workflow →

    expectations (what do they see as a competitor) → their decision making power | @ashmchang
  12. Make it stick → Make sure your persona/JTBD is referenced

    in every step of building your API → Try to see your API and docs from the user’s perspective → Bring actual users back in for every step of the process! | @ashmchang
  13. In Summary → Get to know your user before you

    start building your API → Release endpoints, and APIs, that make sense for the way they will use it → Write fewer docs! → Win developer ! and build a strong dev community | @ashmchang