Many think they figured out Information Systems and that they have reasonable expectations on how to implement their requirements – it has to be done now, it has to be done with built-in functionalities, it has to be mapped here and there, you have to use systems for this purposes… and etc.
It is interesting to observe their conclusions and efforts on how to make thoughts operational.
Here is the small collection of banalities caused by such attitudes.
#1 Perpetual Defending from Bad Ideas
- “We will place all reports to DWH” – even simple reports from production systems that are already built-in”. This is one of the worst idea so far, because costs will be doubled. For recreation of reporting environment many tables and relations will have to be copied and understood.
- “New solutions will satisfy informational requests“. Data quality is one of the core data problem and cause of informational requests. Is new solution really targeting data quality processes? Information relation is second cause of informational request. Is the new solution targeting master data management processes?
I’m tired of explaining complex problems and solutions to same people over and over again. They come with judgment before the meeting and on meetings expect that others have to find out how to implement their wonderful creation, instead they have to explain why they think their artwork is so beneficial. Others have to defend from creators of IS ideas instead of other way round. So many times you have to explain them why is their idea wrong, and they came with such banal and simple solution…
for company for them.
They can not defend it because their knowledge is not on appropriate level, but their suggestion is another story.
#2 Wrapping Own Tasks into IS Solutions and Delivery to Others
- “We haven’t delivered data because DWH could not deliver to us required report” – Taking data from production systems is dirty job I presume. If data is not delivered through push the button wrapped package, then this data is not accessible… like it does not exist…
- “DWH has to do mapping job for specialised Business Intelligence solutions” - DWH has to map for others and to take care for possible wrong mapping of information flowing to their system… excellent delivery of own job (data and reporting maintenance) to others…
In certain cases, solutions are presented as accusations against others like ”IT did not prepare reports!” Accusations are actually delegation of own tasks. It is the delivery of their tasks to others, mostly to IT. If they don’t deliver guilt to others they will be accused for non functional information processes. Very often people within IT have to defend from such nasty accusations wrapped as solutions.
#3 Lack of General Vision
Without the knowledge about overall data and information flows, functionalities of production systems, capabilities of master data management, business intelligence and etc., there is no overall knowledge about Information Systems and how corporate knowledge is generated. In that case there is no strategic BI vision and there is no good and transparent solution suggestion of Information System architect.
I’m tired of shallow knowledge about Information Systems. Knowing a lot about processes but not in deep, how they are applied in production systems. Details make the difference, not high tech general presentations and concepts without implementable reality.
Who reads details about solutions? Several times? This are very rare persons…
Nothing works as general premise without details… details contain wealth.
#4 No investment
Without investment everything has to be perfect…
Reports still needs to be generated despite many changes. Information environment nowadays are under permanent dynamic – change. Changes are very often, almost constant, and they are mostly unstructured. Information Systems with administrators and developers are under great pressure to supply solid supplies of information. what is often forgotten that initial investment very huge and they are not one time expenditure. Each request for change can be significant. This fact is important for understanding that each new report that was not considered during deployment is big task for implementation.
This is often banality.