Foreseen Software

Home / Methodology / Foreseen Software
spy glasses
Foresight

We’ve all seen advice by pundits not to build software features or capabilities that are “only foreseen.”  

One company decided to build software to assist with certain of its transactions. The software wasn’t needed at all when development began!  The entire project was essentially meant to build merely “foreseen” software.

The software still wasn’t critically needed when development was complete. The management team made a decision to forge ahead, adopting the software.  In less than one to two months’ time employees became trained up and completely accustomed to using the software.  It turns out that sales volume of the company grew in parallel with that effort…

After about four months –maybe it was fewer– the company stepped back for a periodic assessment and realized something very interesting.  In retrospect, hardly noticed by anyone, was that the software had become essential.  It was very evident that the transaction volume of the company had already grown beyond a point that would have overwhelmed employees working without the software.  The growth would have created problems at the least.

Customers were impressed with the quality with which these transactions were being handled — which was better than before the project was undertaken.  Employees were able to handle the company’s increased volume comfortably. The growth took place without missing a beat.

The benefits of this merely foreseen software?  Essentially seamless growth, improved transaction handling, and competitive advantage as well.   To be sure, it was rewarding to see these benefits unfold.

In our view, a bit of foresight — including foreseen software — can sometimes prove very beneficial.

Leave a Reply

Your email address will not be published. Required fields are marked *

%d bloggers like this: