Wednesday, October 21, 2009

In Search of Simple Business Applications

My company is currently developing a very simple, easy to use software package which we hope will enable companies to communicate more easily internally. It will cost very little and be VERY user-friendly.

I mention this, not in the hope of selling it to you, but to highlight a problem. Our market research has identified that a number of major corporations and government agencies could really benefit from this little package, but probably won’t ever take it up. Their IT management say that they already have similar functionality built into their ERP and therefore don’t need it.


The Problem with ERPs

The problem comes from the fact that, while IT management might be theoretically correct, the majority of users within the organisation avoid much of their ERP’s functionality..... because it is too complex.

For me, the term ‘ERP’ always conjures up a picture of a large, amorphous, elephantine suite of applications functions which are very cleverly integrated but too complex – and expensive - to implement properly. And, once installed and the price paid, it then becomes too difficult to justify taking on anything else which might in any way compete with what the ERP offers. ERPs also tend to be expensive and slow to enhance, so meeting the changing needs of users becomes that much more difficult.

Consequently, many users are turned off by the complexity of the ERP. They only use the bare essentials of the ERP’s functionality – enough to meet the corporate requirements of the organisation, but avoiding using other parts of the system as much as possible.

The irony is that the concept behind an ERP is that it should be able to model all, or at least a major part of, the corporate operation. Different functions can be integrated within the ERP, so that data and data processing redundancy can be avoided. Yet I suspect that users miss out on a lot of the benefits because of the complexity problem.

The alternative to the ERP, the “Best of Breed” approach, often simply means selecting a number of different, smaller, ERPs, each servicing a smaller part of the organisation’s functions. And bringing these together can keep the IT group busy for many years, and ultimately results in a bigger, even nastier, overall ‘ERP’!


The Alternative

These days users have PCs with email, word processing, spreadsheeting and other stand-alone applications provided. These applications are designed to be easy to use, and they do not require the discipline which is called for with an ERP. It’s much easier to use these facilities in their daily work than using the comparatively pedantic processes offered by the ERP. So the staff, being human, will inevitable opt to use their PC applications rather than the ERP whenever possible.

My premise is that it’s time for large corporations to come to terms with the reality of smaller applications, following the model which is now popular with PC users. Of course it is necessary to retain large corporate systems to process the organisation’s mainstream production and accounting tasks, but we should draw the line there. Give users smaller, independent PC- and Server-based systems to carry out the other tasks within the company.

This may seem to some to be a rather luddite-style approach, going back to the simpler applications concepts which were popular in the pre-online data base days. In some ways this may be true, but the computing environment has changed so much of late that a rethink is surely appropriate and desirable.

One could object that simplifying the computing environment and having more stand-alone applications will almost certainly result in some data and processing redundancy. My response is that, in return, it will free up a lot of staff time which is currently spent in dealing with the complexities of the ERP. On balance, I believe, users will actually become more efficient.

So my call today is simple. It’s time to simplify our business applications, take advantage of the greater flexibility which technology now provides, and make it easier for users (ie staff) to do their work.

3 comments:

  1. Replacing functionality in ERP by a new stand-alone application for the only reason that people do not use the existing application since its too complicated (not too complex, read http://pauljansen.eu/complexity.htm) in use, seems a too simple solution: adjusting the user- friendliness of the existing solution would first come to mind. That would reap all the benefits you envision. Then also one would not have to find an additional solution for integrating the data in- and output of the separate application with the ERP system, which would, in fact, make the ERP system even more complicated.

    ReplyDelete
  2. I agree with Paul completely. Although it is a noble effort to create a software package that can do everything for everyone whilst being as simple as possible, there is one small problem. Every company is slightly different.

    Although the core business functionality requirements around the world are pretty much constant, it is the 10% or so of different or unique functionality that makes ERP systems grow in breadth, making them look larger than they need to be. ERP systems are designed to have that functionality in there just in case a customer needs it. Although they will whine a little about these extra bells and whistles that they don't need initially - as they grow and start needing this functionality it's a great benefit to have it there already rather than getting another 3rd party peice of software to plug a small gap.

    Using the analogy of Office applications being simple to use etc. may not be the best analogy either - I am sure that I only use 25% of the functionality in Word, but I don't complain too much, I just ignore it ;-)

    I'd love to see a link to your software prototypes though - and keep in mind that if people are saying that it can't be done, you are probably on the right track...

    ReplyDelete
  3. I believe that very few IT people actively pursue simplicity. The do not feel it is important to try an reduce the complexity.
    I am working on putting together a model that will use a rule engine to generate/manage an interaction with a user based on the knowledge the system has of the user, previous interactions and the current context/goals.
    My first aim is to tackle a simple conversation like one would have with an IVR system.
    I do believe the same model can be applied to GUI as well. The system could remove the training wheels as the user becomes more familiar with the system.
    Building the system changes from providing directed commands or processes into one where criteria and constraints are described in standard metadata models.

    ReplyDelete