Users looking through Microsoft's help forums are finding a new option. Instead of being offered a long list of steps to fix some technical issue, Microsoft is adding a single button that will just solve the issue.
Web sites launch all the time, but they also shut their doors. We highlight 15 that bit the dust this year.
Let the debate begin: Was the iPhone more important than iTunes? Was anything bigger than Google finding a great business model? CNET offers its list of the 10 most important stories of the '00s.
About Beyond Binary
During her years at CNET News, Ina Fried has changed beats several times, changed genders once, and covered both of the Pirates of Silicon Valley. These days, most of her attention is focused on Microsoft.
Beyond Binary is a look at how technology is changing our lives and the people behind all that life-changing stuff, with an extra emphasis on that which emanates from Redmond, Wash.
Add this feed to your online news reader
Beyond Binary topics
A while back when I ran a software business, I insisted that we do two things for our users
1: EVERY error message that the software could spit out was indexed into the help files so that if you were to search on the exact text of the error you would find something that told you what was going on and hopefully how to fix it. (try this with any error you get from Microsoft, you won't get any hits to this day)
2: The code was instrumented that when it hit an error, we got a series of codes. Then the software built a link to our web site that would look up the solution for that code. This did two things for us. First, our customers could find a quick solution to their problem, second we got to see how many people were having which problems so that we could prioritize our resources to fix the more common bugs first. This was also integrated with the call center so that when we encountered an error that was not cataloged, the user was asked to call, and the solution to their problem was then put back into the catalog so that others could take advantage of it.
I left that job in 2004 and we had implemented this in 2002-2003. I can tell you this, that implementing these two things cut our call center volume significantly and the satisfaction with the software went up considerably. Our customers were able to solve their own problems, we got a good priority for fixing stuff and our costs went down for support.
MS Update errors are pretty common, especially with .Net framework.
However what I find most are errors interacting with 3rd party apps, which I doubt MS can do much about.
I actually got here from a referring article at http://www.zmogo.com/gear/microsoft-wants-to-just-fix-host-of-windows-flaws/
It wasn't as supportive of MS as this one is :P
- by Phil_Blades February 11, 2009 2:53 AM PST
- I liked the concept when I read about it here last week. Last night one of our laptops had a strange problem - this morning (vista) volunteers a new solution for a problem - when I follow the link it has one of the "fix it" buttons. So I used it, an active-X downlad later it fixes the problem, offers a test option to check it is fixed (it is) and asks for feedback. Worked for me - so I still like the concept. Lets see some more.
- Like this Reply to this comment
-
Showing 3 of 3 pages (112 Comments)