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

Listening to (y)our users
from 1 to 100 Millions
Christopher MANEU
Azure Engineer & Advocate @ Microsoft R&D
@cmaneu

View Slide

@cmaneu

View Slide

@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 ?

View Slide

@cmaneu
Why

View Slide

@cmaneu
Only good reasons to listen to your customers
• Inform Product Management decisions
• Asses Product-Market fit at feature level
• Seize uncovered market opportunities

View Slide

@cmaneu
Continuous feedback is a pillar of DevOps
https://aka.ms/devops-definition

View Slide

@cmaneu
Our definition of done

View Slide

@cmaneu
Turn users into fans (or internal advocates)

View Slide

@cmaneu
But, what is continuous feedback?
• Code quality
• Monitoring and alerting
• Customer Feedback
• Internal feedback
• Commerce
• Customer Support
• Consulting teams / onboarding teams

View Slide

@cmaneu
User listening has it’s own challenges
- Being drown under the feedback
- Listening !/= Give control
- Are you building used/interesting features?

View Slide

@cmaneu
How

View Slide

@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

View Slide

@cmaneu
When to do it?
• Product planning
• Backlog priorization
• Feature design
• Pre-release
• Post-release

View Slide

@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

View Slide

@cmaneu
User community programs
Uservoice-like platforms for features
ideas and priorization
Discourse-like forums for
trends & co-building with
the community

View Slide

@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!

View Slide

@cmaneu
In-app Feedback

View Slide

@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

View Slide

@cmaneu
Tech & Business In-app feedback

View Slide

@cmaneu
Microfeedback

View Slide

@cmaneu
Microfeedback > Followup

View Slide

@cmaneu
Scaling Microfeedback
Any PM should be able to add a feedback piece in a service without days of
development.
inline
dislikeQuestion={followUpOnDislike}
likeQuestion={followUpOnLike}
likeIconTitle="Like"
dislikeIconTitle="Dislike"
sendFeedback={sendFeedbackCallback}
sendFollowUpIndex={sendFollowupIndexCallback}
thanksText="Thank you!"
tokens={{ followUpBackgroundColor: 'lightgrey' }}
/>
Microfeedback.jsx

View Slide

@cmaneu
What

View Slide

@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
• …

View Slide

@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

View Slide

@cmaneu
Surface feedback in development backlog

View Slide

@cmaneu

View Slide

@cmaneu
Surface feedback within the company

View Slide

View Slide

Porte de Versailles, Paris
13 et 14 Novembre 2019

View Slide

@cmaneu
Be relentless

View Slide

@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/

View Slide

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

View Slide

Thanks !
Christopher MANEU
Azure Engineer & Advocate @ Microsoft R&D
@cmaneu

View Slide

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

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

Christopher MANEU

More Decks by Christopher MANEU

Other Decks in Technology

Featured

Transcript