When your product is an API, your immediate users and your end-users are distinct groups with different and sometimes conflicting needs. I want to talk about the product management strategy I employ to balance the needs of both developers and the product users, which in turn balances both technology mandates and business goals.
I will define my terms, explaining why I think it’s valuable to define two sets of user problems and create two parallel tracks on your roadmap. I’ll provide some practical examples, and then talk about how I manage the conflict when these two tracks occasionally compete with one another.
High impact blog posts and eBooks on API business models, and tech advice
Connect with market leading platform creators at our events
Join a helpful community of API practitioners
Can't make it to the event? Signup to the Nordic APIs newsletter for quality content. High
impact blog posts on API business models and tech advice.
Become a part of the world’s largest community of API practitioners and enthusiasts. Share your insights on the blog, speak at an event or exhibit at our conferences and create new business relationships with decision makers and top influencers responsible for API solutions.