April 4, 2013 Silicon Valley Product Management Association (SVPMA) Santa Clara, CA Panel Discussion. (includes additional content provided by speakers)
What is the API business model?
Its the same as the web biz model –
advertising, selling product, recomendations, satisfaction….
there is NO API biz model (and no santa claus).
If you understand your core biz model – you should wrap your APIs around it = key KPIs
– look for leading indicators, adoption, market share, reach
– Align APIs with that.
See on storify.com
It has long been asserted (famously, by Steve Jobs) that customers can’t tell you what your next product should be. Companies create and customers consume.
To be competitive, brands need to look outward and cultivate the communities of creative customers that are shaping the future of their products.
Developers have been using APIs and open source software for many years to increase the pace of innovation. Consumer product companies can mimic these more open systems. Just look at companies like Sifteo or Lapka that have created physical products connected to software that are designed to be remixed into new applications.
Bottom Line for extending engagement and product narrative:
People embrace what they influence, so more open and transparent brands will become the most loved and talked about as well.
Questions for discussion:
How can you enable customer influence and manage user creativity without losing control and focus on development cycles and roadmap…?
Is it possible to nurture creative customer communities in parallel with developer communities? Remember User Groups that had love/hate for the developers?
How do you enable creative consumers without canabalizing next versions?
What are the most effective tools for managing crowdsourced feedback and ideas that enable more than marketing content and engagement incentives?
See on www.fastcocreate.com
By Michelle Sun
I had the privilege to attend the first Startup Product Summit in SF on Feb 7, 2013. It was a great lineup of speakers and a full room of buzzing energy and great conversation. Without further adieu, I’d like to share some key learnings of each panel.
Please let me know if I omitted or made any errors in the references. Credit for the good stuff is entirely the speakers’ (link to twitter handles are included on each name).
“Turning Mediocre Products into Awesome Products” – Jonathan Smiley, Partner & Design Lead, ZURB
- Ideation and iteration can ”turn mediocre products into awesome products”.
- Discussed a full spectrum of research from market-driven (focus group, survey) to user-driven (remote teaching, usability teaching)
- Importance of sketching, a lot, aim for speed and volume, then critique
- Advice to the audience: ”do 10 more sketches ( more ideation is always better ), build 1 more prototype, get 1 more round of feedback, ask 5 more customers”
“Being a UX Team of One” – Vince Baskerville, Product, Lithium & Co-Founder, TripLingo
1. Internal politics is a common challenge as a UX team/professional. Learn to manage expectation of different internal stakeholders and keep everyone in the loop.
2. Don’t listen to what customers are saying. Users’ claims are often unreliable. See what they are doing. Understand the underlying issue.
“Validate Your MVP on Paper” – Poornima Vijayashanker, Founder & CEO, BizeeBee & Femgineer
– 2 Reasons MVP Fail
1. Fail to figure out how to provide a simple value proposition that differentiates your product from your competition
2. Fail to figure out who their early adopter are.
– Early adopters are people who aren’t using the competitor’s product. Don’t want to take time to switch over.
– Steps on usability testing
- Explain the problem. What you are testing. How they are helping. Get them excited about the idea.
- Set expectations. Make them comfortable.
- Communicate intention (what exactly are you testing and specific feedback you are looking for).
- Thank them for their time. Follow up regularly.
Poornima’s slides are available here.
“Everyone’s Customers Are Wrong” – Evan Hamilton, Head of Community, UserVoice
- Data doesn’t tell the whole story. Analytics are bandaids because we can’t watch our customers.
- People don’t tell the whole story. Identify who the users are, where the feedback are from. Are they: paying/freeloaders? Using product in the intended way? Using main features? Early adopters / ‘tech fanatics’ (who are not likely to stay on a product for the long haul)?
- Combine data and customer stories. Customer feedback / feature suggestion usually leads from a deeper issue. Find out what the actual problem is by understanding the underlying need.
- Don’t lose track of your creative mind by getting lost in data rat-hole. Don’t chase 1% when you can get 15%. Not just A/B, but try something crazy. Try big bold things along with incremental fine-tunes.
“Designing for Everyone: The Craft of Picking or Killing a Concept” –Miki Setlur, Product Designer, Evernote
- Everyone use product in many different ways. A useful strategy is to segment users into business, partners (e.g., app stores for Evernote’s case) and users.
- Figure out what each segment cares the most about: Business / Partners – acquisition, retention, engagement, revenue. Users – being faster, better, happier.
- Case study on how Evenote’s design process stroke balance between business goals (monetizing) while being sensitive to user experience and goals (finding things faster).
Other relevant points
How to access willingness to pay during pre-product interviews. Get the first dollar within the trial period. Provide clear value proposition from the get-go.
How to get good feedback. Be specific in what feedback are you looking for. Instead of asking in general ‘what do you think of the prototype’, ask whether they are confused on what stage, what was confusing.
Tips on prototyping. Put more emphasis on story telling than illustrating.
For remote testing, use keynote as prototyping tool, screencast the keynote.
On the tension between product vs. business goals in roadmapping a product. Early stage products make sense to focus on product. Once reached product market fit, it makes sense to lead with business goals such as, acquiring, converting, retention customers.
Also mentioned was a tool called Impact Mapping.
- Key Takeaways from Roadmapping and Execution Panel
- Key Takeaways from Marketing and Getting Traction Panel
About The Author
Michelle Sun is a product enthusiast and python developer. She worked at Bump Technologies as a Product Data Analyst and graduated from the inaugural class of Hackbright Academy. Prior to Hackbright, she founded a mobile loyalty startup. She began her career as an investment research analyst. When she is not busy coding away these days, she enjoys blogging, practicing vinyasa yoga and reading about behavioral psychology. Follow her on Twitter at @michellelsun and her blog.