Microsoft Corp. wants more details on how its products are used so it can make its applications "almost entirely crash-free" and build features users want, the company said Monday.
With the launch of Office 2003 later this quarter, Microsoft will also introduce a Customer Experience Improvement Program for Office. Users will be asked to volunteer to share information on feature usage, software and hardware performance and the type and frequency of errors, said Eric LeVine, group program manager for Office.
The program builds on Microsoft's error reporting tool in Windows XP and Office XP, which asks users to send a report to Microsoft when an application crashes. The Customer Experience Improvement Program goes a step further. Much broader usage data is sent to Microsoft on an ongoing basis without alerting the user, LeVine said.
"With error reporting there are explicit events. The Customer Experience Improvement Program gives us an anonymous ongoing feed," LeVine said.
Users will be asked to join the program a few days after installing Office 2003. After a user opts in, the data gathering happens in the background and does not bog down the system, LeVine said.
The Customer Experience Improvement Program is not new. Microsoft already uses the program for its Money, Windows Media and MSN Explorer products, LeVine said.
The program helps Microsoft understand how its software is used and make decisions on new features and bug priorities, Microsoft said in a white paper on what it calls its Customer Connection and Satisfaction Tools, which are used in the Customer Experience Improvement Program. It may never be possible to create "perfect" software that performs without crashing under every circumstance, but the tools have led many product teams in Microsoft to believe they can make applications "almost entirely crash-free," according to the white paper.
Building stable software is one thing. Data on which features users care about in Office is worth more, LeVine said.
"The Customer Experience Improvement Program lets us measure the progress we're making as we fix crashes, but the more interesting thing is that it lets us understand the functionality people use, what they like and dislike. So as we design future software versions, we make sure that we design features that matter to customers," LeVine said.
"It is not about turning the world into a giant test lab. It is about us understanding how our software performs in the real world and how we can continuously improve it based on feedback," LeVine said.