New
#1
MVP Summit Travelogue Day 2: Serious Feedback -- Seriously!!
Today was the first real content day at the Microsoft MVP Summit here in Bellevue (and Redmond). Instead of hanging at the downtown Hyatt, this morning we boarded buses for various destinations on the Microsoft campus. My itinerary took me to building 83 (home of the Windows 10 marketing team) and 86 (home of the Surface design team). I can't say I feel too constrained by the NDA stuff today because much of what we heard was neither earth-shattering nor terribly exciting.
I did, however, come away with some interesting insights on Microsoft telemetry. It seems that those who turn telemetry off are hurting themselves more than anyone else. Microsoft uses telemetry in the aggregate and keeps track of problems, bugs, and issues by comparing user feedback from the feedback hub against the logs and traces that the hub sends back to Microsoft when feedback is reported. They prioritize the things that need fixing based on the items that appear most often in that log/telemetry data that goes along with user reports. The more feedback they get on some specific topic, the higher the priority for addressing that topic becomes.
What does this really tell us about turning telemetry off or not providing user feedback? It tells us that those who turn telemetry off lose the biggest chance they have to provide the very data that Microsoft needs to fix such problems or issues as they many encounter on their Windows 10 PCs. It also tells us that those who want to steer Windows in a different direction, or to see problems or issues fixed, should provide feedback to improve the odds that those things will be addressed or fixed.
I was sitting at the bar a few minutes ago, talking to a new MVP friend name Janne from Finland. We agreed that if you don't ask the right questions you can't possibly get the right answers, either. This suggests very strongly to me that providing MS with telemetry only helps to make things better for Windows in the long run -- and thus for us, who use Windows, too.
The best way to give feedback, according to those who run the program at MS is to do the following:
1. Give your feedback a clear and descriptive title
2. Provide as detailed an explanation of what you observed, what you tried, and what happened to prompt a feedback report
3. Stick to one issue per feedback report: if you multiple items or issues to report, great! Just file one report for each issue (this helps greatly with distribution, analysis, and handling of such reports)
4. Because feedback reports depend in large part on telemetry used to tied human descriptions of problems (which usually focus on symptoms, where the telemetry includes information about errors, failures, and events, which point more toward causes) it's best to leave telemetry turned on. This goes double or perhaps even triple for Insiders, who are essentially participating in the program for the primary purpose of providing telemetry for the express purpose of improving the next, upcoming production version of the operating system.
'Nuff said.
--Ed--
#MVPSummit, #MVPBuzz
Last edited by EdTittel; 07 Mar 2018 at 18:30. Reason: Day 2 not Day 3