Kill the Spreadsheets!!!
Any new system implementation like an ERP or any other IT based system has to counter a long legacy. It all depends how they face each other. IMHO based on personal experiences with a Manufacturing Giant and now an EPC giant, the existing IT systems often hinders the implementation of new IT systems. I am not talking about compatibility and data transfer issues. I am just talking about stand alone individual systems that each one of us create and cling to them as if they have a potential to get Noble Prize nominations. I am talking about those several files and folders created through MS Office (or similar) applications.
MS Office beyond doubt has transformed the way we work. Hand written documents are on the verge of extinction. With features like spell check we don’t really need to flip a single page of any dictionary and the excellent storage and retrieval edge that e-documents have over the traditional ones, the extinction was bound to happen. But we often go an extent where we create our own systems on these platforms, systems that are secluded, which becomes our own intellectual property.
While we create our own way for looking at things, we do a great injustice to the organisation. We often do things that others have been doing, we create tacit knowledge base without sharing it, we depend more on human interventions and more importantly we create confusions with small errors in data entry.
The entire idea of Database automation was to have a single database and generate reports from the same date base. It also required some amount of discipline in terms of data forms and structures. More importantly, it was to serve as the resources centre for any data churning activity. As networking and computing infrastructure evolved to higher levels, a centralized database managements system was expected to weed out redundancies in roles as much as in people on such roles.
The individual spreadsheets came in the way. They blocked the way towards organisational effectiveness. Their creators loved them more than their jobs and had a hard time imagining life without those spreadsheets and e-documents. We somehow fail to understand that our spreadsheets and queries can take the shape a standard report by a small customization. It wont cost a fortune (infact may be a freebie) and more importantly would be from a centralized database. From all cross-linking and syntax writing, it might just require a click of a button. Most of these change management initiatives have failed to address such issues. New System Implementation to me, is more of a cultural issue rather than a technology or process related stuff.
The leadership in particular has a major role here. Most of these spreadsheets are created for answering queries and preparing reports for the top management. So in the most charitable words, they somehow drive the culture of standalone systems. They often ask what do we do? And the simple answer is stop driving those standalone sheets! Kill those spreadsheets. Instead try acting as a ‘Convert” and a champion for the new System. Don’t accept spreadsheets from the stand-alone systems. Apart from being a change agent, you must also be aware that the validity of such report is questionable and you will never have the time to check it yourself. By asking for a system generated report you reduce the risk and in turn help reach newer heights with exploiting the existing resources to their highest potential. So please kill all the spreadsheets. Please!
