Welcome to MSDN Blogs Sign in | Join | Help

Customer expectations

Last October after presenting a keynote at the Conquest software testing conference I was invited to speak at an internal quality conference at SAP. At first it may seem a bit odd because Microsoft and SAP do compete within one market segment; however we also do collaborative work on other projects. Regardless of the company we work for, I do believe that most software engineers are intent on doing the best possible job they can to produce the best possible product they can that will ultimately provide a high value solution to the end user customer.

The common theme throughout the conference was the need to improve quality. In my keynote I suggested that customers demand higher quality because the end user customers of today are very different than the customers of yesterday. Today, software permeates virtually all aspects of our life. Today, software is found in children's toys, in our automobiles, and even in toothbrushes. A decade ago computer users were accustomed to periodic anomalies and  assumed it was the price of technology; however the end user customers today have much higher expectations of software and  presume it will simply work and provide an easy solution that offers some perceived value in their lives!

In my keynote address to the engineers at SAP I described how I would sometimes say "my Mom wouldn't understand how to do such and such" when describing ambiguous functionality, but in order to remain successful and competitive in today's market we need to consider designing and developing software for our children and future generations. Of course we want our existing customers (and my mom) to feel comfortable using our software, but it is readily apparent that our children want a very different experience and have higher expectations from software.

Published Wednesday, March 19, 2008 6:58 PM by I.M.Testy

Comments

# re: Customer expectations

"A decade ago computer users were accustomed to periodic anomalies and  assumed it was the price of technology"

I conditionally disagree with this; a decade ago users were accustomed to these anomalies because they didn't have much choice. I spent a good part of the 90's complaining about some application or other that was pretty lame, but the options were so limited that that's what you got. What were the options? Not many. I don't think technical savvy on the part of the customer made this change, but the slow maturity of the software industry and the increase in options means that the product developers must consider the real user needs.

"Regardless of the company we work for, I do believe that most software engineers are intent on doing the best possible job they can to produce the best possible product they can that will ultimately provide a high value solution to the end user customer."

While I believe that to be generally true, without developers and testers that actually understand the 'high value solution to the end user', quality must suffer. And as always, the urge towards cool technology often trumps the passion for a superior customer experience.

Finally, what isn't mentioned is that the end-customer has more ability to affect the company pocket-book. A decade ago, differing products had large deltas in end-user quality. Now, the measure by which a customer can make a decision has become more subtle because of the options available. As a product company, the 90's focused on features not quality, but now many of the features have baselined, so more fine-grained quality becomes the differentiator. This again is not predicated on the end-user's understanding or acceptance of certain technologies, but instead on the maturity of software apps and the growth of choices.

Wednesday, March 19, 2008 5:11 PM by trainer_erich

# re: Customer expectations

Hi Erich,

I am not quite sure what you mean by 'conditionally disagree,' but I don't think we disagree at all. I didn't say customers were satisfied I said (as you did) that customers were accustomed (familiar) with anomalies.

It seems that you limit your view of quality primarily from an end user experience, and I suspect you consider the primary end user to be the general public. On the other hand, I tend to look at quality both from an engineering standpoint and a customer value standpoint.

I agree that today's end user customer has more ability to impact the company pocket-book, but they do so indirectly. (Sorry to say, but the average end user customer doesn't really pay the bills, but for some companies it is their usage of technologies that company provides that may impact the company pocket-book. For example, some Internet-based companies don't sell software to end-user customers, but the end-user customer experience and the engineering quality is important to these companies because it is the high traffic flow by end-user customers that helps them attract advertising dollars, and in the end it is marketing dollars for advertisements that pay those bills).

In my opinion it is not the maturation of legacy software applications that is driving change, but it is the proliferation of computers in society providing low cost solutions to the mass market, and the rapid expansion of (relatively) new technologies and the way that we now utilize these new and emerging technologies (SOA for example) that have made the end-user customer more of a driving force in both end-user quality (value and experience) as well as engineering quality (functionality and reliability).

Wednesday, March 19, 2008 10:06 PM by I.M.Testy
Anonymous comments are disabled
 
Page view tracker