Seilevel
Seilevel Home
Back to Blog Home - Requirements Defined

Tuesday, July 29, 2008

Mattress Software Requirements

My wife and I recently set up one of our spare bedrooms using a bed frame that had been handed down in my family. We didn't have a full size mattress to put in it, so I ended up shopping for a mattress last weekend. Mattress shopping was easy. Mattress buying - much more complicated, and an example of software gone wrong.

After having selected a mattress, we began the checkout process. The sales rep looks at me sheepishly and says "We got new software last month. You'd think that I wouldn't have to click the mouse a couple hundred times to sell you a mattress!"

Sure enough, the sales process was rough. It needed my personal information in 2 places. We couldn't check on delivery dates until we'd finalized more of the sale. The sales person was visibly frustrated just trying to navigate the software.

This is obviously a classic example of software being built without feedback from the users. Now granted, there are probably lots of features in the software that the business owners wanted - prompts to suggestive sell upgraded warrantees, financing offers, etc. What was missing was the critical usability review from the people who would have to use the software every day, all day.

Labels:

Requirements Defined Newsletter Bookmark and Share

5 Comments:

Anonymous Anonymous said...

Interesting post Marc. Of course, it should be noted that there may be times when the goals of a designer override the goals of the end user. In your example, the business may want to delay the checking of delivery availability until very late in the process to ensure that the customer is totally hooked in. If you spend 5 minutes helping the sales rep fill out a form you may be less likely to back out over a 2 day delivery wait then you would be if you heard that before you had jumped through all of the hoops.

7/29/2008 2:44 PM  
Blogger Roger L. Cauvin said...

Sounds like what was really missing was a nonfunctional requirement constraining the number of user gestures it takes to process a purchase.

7/29/2008 3:22 PM  
Blogger Craig Brown said...

Marc,

This raises an interesting question;

Who's requirements do you prioritise? The customer (aka sponsor) or the user?

7/30/2008 5:31 AM  
Anonymous Anonymous said...

Sadly, the unmanangable check-out procedures could come from a poorly designed software, or from lack of proper training on the new software. I have witnessed a business owner/manager purchase software because the management tools were fabulous---great advice on how to improve the business. Then the same owners/managers of the business didn't bother to invest a few dollars more to make sure that their employees knew how to use it, and that their customers contine to receive excellent customer service. Sadly, the business will probably never know that the problem exists, and customers who get fed up with the process will begin to shop elsewhere.

10/09/2008 2:33 PM  
Anonymous queen mattress said...

Hi Marc,

You have a thought provocing idea. Only the end users of a system can make the most useful remarks on the software. Thanks,

- T.Vincent

10/06/2009 12:40 PM  

Post a Comment

<< Home