« Busy. Simple is in the eyes of the beholder. | Main | VOICE »
Friday
Apr022010

Used Cars and Legacy Software

OK, you can see where this is going right now.  Here's the whole debate over re-use, repair and getting something new in an easy to understand analogy.  The way to think about used cars or legacy software is not "how much is it worth after I fix it?" but "how much does it cost me to get what I want (or need)?".  It's a cashflow question, not a value question.  In both cases you're probably not selling anyway.  So what difference does it make how much it is "worth" to someone else?  You're never going to realize that worth in cash or otherwise.

On the other hand, the cost to replace the car or the software is something you'll have to realize.  You'll realize it as the money flies out of your pocket.  You'll realize it as the debt incurred to acquire the new stuff continues to erode the value of the new stuff.  I'm not advocating a "never borrow" strategy, just pointing out that many of us forget to include all that interest in our thinking.

If you think about refreshing the user interface or adding some new behaviors to an existing application kind of like aftermarket accessories or repair parts for that older car, you can put this idea into perspective.  For instance, my old Mercedes doesn't have cup-holders.  I think I'll add some rather than get a new car just for the cupholders.  A trivial example to be sure.  On the other hand, the hydraulic suspension needs repair and that can make you think twice.  Worth it?  Well, if it costs $500 and I think then I have a car "worth" $3000 that I have repaired for 1/6 of its value, you might not think so.

On the other hand, if I think I've spent only $500 to keep what was originally a $60,000 car on the road and serving me perfectly well, I might make a different decision.  The functionality and features are all there, they just need a little refreshing to keep being really useful and enjoyable.

A lot of my interaction design work is that kind of refreshing.  I'm taking a valuable, useful and proven software system and restoring its utility by re-concepting and redesigning the interaction idiom and user interface.

Often it is a very cost-effective and efficient solution for the enterprise.

PrintView Printer Friendly Version

EmailEmail Article to Friend

Reader Comments

There are no comments for this journal entry. To create a new comment, use the form below.

PostPost a New Comment

Enter your information below to add a new comment.

My response is on my own website »
Author Email (optional):
Author URL (optional):
Post:
 
Some HTML allowed: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <code> <em> <i> <strike> <strong>