As we try to build APIs that are valuable, usable, and feasible, are there lessons we can learn from Product Management and how we approach this? This session will be a fun look at some anecdotes and cautionary tales shared by Product Managers, and reflect how they can help our thinking when designing and building APIs.
The concept of "APIs as a Product" and the need for a Product Manager for APIs is a growing trend (in 2017 Thoughtworks added an entry tracking the idea to their Tech Radar) – so what exactly does this mean? And what can we learn from Product Management? From dog psychology experiments to lessons from Netflix, we will take a whistle-stop tour through the discipline to look at what we can learn that might help us build great APIs.
10. Don’t make me think
➔ Create Visual Hierarchies
➔ Use conventions
➔ Break up the page into clearly defined sections
➔ Make it clear and obvious what is “clickable”
11. ➔ The most important characteristics of good
design are discoverability
& understanding
➔ Stop thinking of it as “Human Error”
The design of everyday things
13. ➔ What happens if you make your customers
think?
➔ Cognitive load, decision fatigue and giving up
➔ Can we make users awesome instead?
Making Users Awesome
19. Lessons so far:
❏ Don’t make me think!
❏ Create a visual hierarchy
❏ Use conventions
❏ Make it clear what is “clickable”
❏ Simplicity
❏ Understanding & Discoverability
❏ Make users awesome
20.
21.
22.
23. A visual hierarchy, that can
be understood and navigated
Use of repeating conventions:
{ENTITY}/{IDs}
{ENTITY}/{IDs}/{CHILD_ENTITY}
40. You know those balls that they put on car
antennas so you can find them in the parking lot?
Those should be on every car!
Homer Simpson, Oh brother, where art thou
51. ● Goes against established web standards (HTTP methods, REST)
● Clashes with years of web technology (caching)
● Solves a problem & growing adoption
52. Conclusion
❏ We are all building products!
❏ Product thinking is for everyone!
❏ Keep it simple, make customers awesome
❏ Don’t do whatever is asked, try to understand the root problem
❏ Don’t keep doing things because of tradition
❏ But there is a premium for changing standards! (both for tech & customers)
55. Photo credits
Light bulb Photo by Sean Patrick Murphy on Unsplash
Turntable Photo by Adrian Korte on Unsplash
Drilling Photo by Matt Antonioli on Unsplash
Kathy Sierra Photo at MTP Conference 2014
mindtheproduct.com
Cake Photo by Brooke Lark on Unsplash
Donuts Photo by Patrick Fore on Unsplash
Kodak Photo by Adam Birkett on Unsplash
Questions Photo by Braydon Anderson on Unsplash
Skateboarding Photo by Kirk Morales on Unsplash
Listen to Photo by Mohammad Metri on Unsplash
Car Photo by Paweł Kozak on Unsplash
Skeleton Photo by Mathew Schwartz on Unsplash
Coding Photo by Markus Spiske on Unsplash
Developer Photo by Tim Gouw on Unsplash
Pencils on yellow Photo by Joanna Kosinska on Unsplash
Happy developers Photo by Mimi Thian on Unsplash
Lemons Photo by Nery Montenegro on Unsplash