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

ON PEUT ÉCOUTER UNE FOIS UN UTILISATEUR, MAIS P...

ON PEUT ÉCOUTER UNE FOIS UN UTILISATEUR, MAIS PEUT-ON ÉCOUTER 10 MILLIONS D'UTILISATEURS UNE FOIS ?

Nous savons tous que la conception centrée utilisateur est fondamentale pour le succès d'un produit. Parmi l'ensemble des choses à faire pour y arriver, collecter du feedback de vos utilisateurs est l'un des points les plus importants pour prendre les bonnes décisions produits et techniques. Mais comment le faire ?
A la fin de cette session, vous aurez quelques techniques pour collecter ce feedback, mais aussi l'intégrer dans votre workflow de développements. Ces techniques proviennent de mes expériences à différentes échelles : de la startup qui tient dans une voiture aux équipes Azure en passant par Deezer.

Christopher MANEU

October 29, 2019

Transcript

42 slides
  1. Listening to (y)our users from 1 to 100 Millions Christopher

    MANEU Azure Engineer & Advocate @ Microsoft R&D @cmaneu
  2. @cmaneu Listening to (y)our users Why listening to our customers?

    How to do it? What ‘s needed to get this back into development process ?
  3. @cmaneu Only good reasons to listen to your customers •

    Inform Product Management decisions • Asses Product-Market fit at feature level • Seize uncovered market opportunities
  4. @cmaneu But, what is continuous feedback? • Code quality •

    Monitoring and alerting • Customer Feedback • Internal feedback • Commerce • Customer Support • Consulting teams / onboarding teams
  5. @cmaneu User listening has it’s own challenges - Being drown

    under the feedback - Listening !/= Give control - Are you building used/interesting features?
  6. @cmaneu Culture of Feedback • It’s not a criticism, its

    not only feedback • Being a good listener is hard • Split substance and emotional load This culture of feedback should be supported by management
  7. @cmaneu When to do it? • Product planning • Backlog

    priorization • Feature design • Pre-release • Post-release
  8. @cmaneu Ways to collect feedback • User sessions • User

    community program • App review • In-Product Feedback • Microfeedback • Top Program Users • Customer support • User advocacy teams (CSM, Advocates) • Customer Champs
  9. @cmaneu User community programs Uservoice-like platforms for features ideas and

    priorization Discourse-like forums for trends & co-building with the community
  10. @cmaneu Learning from App Reviews Focused on 1-star reviews Look

    for specific feedback areas : • Performance • Login • Feature X • Lack of features Weekly review of the ratings. Compilation done by one, reviewed by the whole team. Do not review comments on Friday!
  11. @cmaneu In-app Feedback { "feedback.v": "1", "feedback.ts": "1451399541", "feedback.type": "Provide

    a suggestion", "feedback.title": "Support the developers", "feedback.body": "Hey,\r\nThis is a great Windows 10 app. I love it !\r\nKudos to the devs ", "app.version": "3.0.8.0", "app.lang": "us", "dev.p": "windowsuniversal", "dev.family": "Windows.Mobile", "dev.arch": "Arm", "dev.brand": "NOKIA", "dev.model": "RM-937_eu_france_219", "dev.display": "432x768", "dev.osver": "10.0.10586.29", "dz.family": "Mobile", "dz.ua": "Deezer/3.0.8.0 (WindowsUniversal; 10.0.10586.29; Mobile; us; RM-937_eu_france_219)", "user.hasal": "True", "user.id": “XXXXXXXXXX", "user.country": "FR", "user.dal": "True", "user.ot": "None" } feedback.json
  12. @cmaneu Scaling Microfeedback Any PM should be able to add

    a feedback piece in a service without days of development. <MicroFeedback inline dislikeQuestion={followUpOnDislike} likeQuestion={followUpOnLike} likeIconTitle="Like" dislikeIconTitle="Dislike" sendFeedback={sendFeedbackCallback} sendFollowUpIndex={sendFollowupIndexCallback} thanksText="Thank you!" tokens={{ followUpBackgroundColor: 'lightgrey' }} /> Microfeedback.jsx
  13. @cmaneu Triaging the feedback • Internal • Insiders • Production

    • Commercial ticket • Actionnable feedback • Bug Ratio • By Product / Feature • By Area • Accessibility • Client • Docs • Download & Install • Performance • Privacy • Security • I18n / l12n • …
  14. @cmaneu Make the feedback actionanble • What success look like?

    • What metric can you put in place • Gather the necessary context • Tie back to your objectives
  15. @cmaneu Bibliography • https://hbr.org/2011/08/henry-ford-never-said-the-fast • https://medium.com/@antweiss/understanding-feedback- loops-in-devops-e93b92b74bd1 • http://itrevolution.com/the-three-ways-principles- underpinning-devops/

    • https://learning.oreilly.com/library/view/the-phoenix- project/9781457191350/ • https://www.hbrfrance.fr/magazine/2015/01/5928-sachez-tirer- des-lecons-des-critiques/
  16. Image credits Photo by Gia Oris on Unsplash Photo by

    Emily Morter on Unsplash Attribution-ShareAlike 2.0 Generic (CC BY-SA 2.0) Kristina D.C. Hoeppner https://www.flickr.com/photos/4nit sirk/3975502406/in/photostream/ Photo by Arnaud Jaegers on Unsplash Photo by Annie Spratt on Unsplash

More Decks by Christopher MANEU

Other Decks in Technology