My Photo

About Mike


Subscribe to Mike's Blog

Subscribe to Postings

To Receive a Daily Email of new Postings
Enter your email address:

Delivered by FeedBurner

Read My Posts via RSS feed
 


Join the Conversation
Subscribe to Comments

To Receive a Daily Email of Comments on Posts
Enter your email address:

Delivered by FeedBurner

Join the Conversation (Comments RSS Feed)
 AddThis Feed Button

Blog Search and Links

  • Add to Technorati Favorites


Creative Commons License 
This work is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 2.5 License.


Recognition


My photos on
www.flickr.com
This is a Flickr badge showing public photos and videos from Mike Schaffner. Make your own badge here.


Powered by TypePad
Member since 10/2006

Rankings

  • Blogarama - The Blog Directory
  • Technology Blogs - Blog Top Sites
View blog authority

« Eight Business Technology TrendsTo Watch | Main | Zappos: Integrating Systems and Business Processes »

April 07, 2008

When Robots Attack

Robbie_robot_jopemoro_3James Taylor over at the smart (enough) systems blog posted an interesting article last week.  It was one of those that if it wasn't so serious it would be funny.  His post iRobot - Elite CRM, stupid returns system details his experiences of buying 3 systems from iRobot and wanting to return 1 of them.   As crazy as it sounds the only way he could do this was to return all 3 and then re-purchase the 2 he wanted.  As Taylor points out this is a poor way of doing business in so many ways.

Taylor notes that iRobot received a 2008 destinationCRM award for their automated customer service system.  However after his experience with trying to return a product Taylor notes " am sure the automated system for which they received an award is wonderful - I have not had to use it yet - but clearly they could do with making their return system a little smarter."  It does make you question how much thought they really put into the design of their system or if they tried to get any customer input into the system.

This example points out the need for 2 essential elements in good application development - the end user perspective and adaptability.  End user perspective can be obtained in a number of ways.  It can be based on the developers knowledge of how the system is used, input from the sales team,or directly from the end-user themselves.  How you get this input all depends upon the particular situation.

So why is all this important?

Taylor's example points out those darn end-users will always want to use your system in ways or to do things that you as the developer never imagined.  If you don't get end-user input you'll constantly be surprised and deliver software the end-users find lacking.

The need for adaptability comes in because even when you get end-user input they will find new ways to use it or try to do things in a way even they hadn't thought of when you asked them.  This may sound like a "no-win" situation but it doesn't have to be that way.  If you consider the end-user perspective and deliver solutions that are adaptable enough to cover ever changing situations you'll be a hero to your end-users.

How do you consider the end-user perspective in your application development?

"robbie-robot" photo by jopemoro

If this topic was of interest, you might also like these:

Tell a Friend       View blog reactions       

TrackBack

TrackBack URL for this entry:
http://www.typepad.com/t/trackback/1102168/27833850

Listed below are links to weblogs that reference When Robots Attack:

Comments

Thanks for the link. One of the key problems when programmers consider adaptability is that of finding the hidden decisions - in my example, the decision about how much of a refund is due. If the implicit decisions are not called out and automated they cannot be evolved. Even if the business says the decision is always the same, this may not be the case in the future.
JT

James Taylor
Author of Smart (Enough) Systems

James,

Thanks for commenting. You're correct adjusting for the hidden decision is tough. Because of this you always have to think twice about hard-coding rules etc. and try to think of how it can be changed to match changing situations.

Mike

That is just totally crazy that all 3 had to be returned even though only one needed to go back. It just goes to show we have a lot to do before we can really rely on automated systems.

new zealand travel

Your right we have a lot to do. Two things that could have been easily done but weren't include consider the possiblitiy or returns when designing the system. Returns are not all that uncommon afterall. Secondly, the company could have empowered the customer service rep (CSR) to resolve the situation. It iRobot doesn't authorize its CSRs to think for themselves and therefore the only option was to "undo" the whole transaction. I think everyone would agree their solution was as you say totally crazy but for some reason they wouldn't give the CSR the latitude to figure out an equitable solution and live with it. Strange to say the least.

Mike

Post a comment

If you have a TypeKey or TypePad account, please Sign In





Recommended Books


This is the personal blog of Michael W. Schaffner. The opinions expressed in this blog are soley mine and those of commenters. You should not infer that these opinions are the opinion of or have been endorsed by any current or former employer.
Copyright 2006, 2007 Michael W. Schaffner       You may copy or quote sections of this blog if you provide an attribution consisting of a reference to the Michael Schaffner and ''Beyond Blinking Lights and Acronyms" along with a hyperlink (if a web reference) to the blog posting.     
Creative Commons License 
This work is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 2.5 License.