Information Is Not Panacea. It Is the Model That Ultimately Matters!

Stands on its own, the famous quote of “Information is power!”, if it is not a lie, exhibits a grave inadequacy in representing the real face of various kinds of information consumption. 

 

What is information in the first place? The information is data within the proper and focused context across time and space. Data exists and demises everywhere and anywhere in accordance with individual preference and selective perception to a subject matter. For data to be considered an asset, it must be understood and useful to decision-making process.

 

Decision-making process, indeed, is guided by a selective model, be it explicit or implicit. Too often, a decision maker is not even aware of the existence of model being adopted and framed in the process. No any decision may be made without a guiding model, whereas information is merely supporting factors to justify the decision. It is a misconception that more information will drive batter decision. In fact, the selection and development of model within a particular context in decision-making is more crucial and relevant to a batter decision than information on its own. But then what is a model actually?

 

A model is a real world representation. I like to use the scenario of a map in my lecture class. A map is a model as it is a representation of the real geographical existence. However that, a map cannot contain each pieces of information on the land. A usable and practical map should only include those pieces of information that could serve the purpose of reading and interpreting map to accomplish certain purpose. Hence the map to direct a traveller to move from one destination to another is very much different from the map for installing public utilities despite the geographical area is exactly same.   

 

In software engineering, we have too often heard the word “model”. But I bet you, many of those software professionals are not able to explain articulately the rationale and logic behind such modelling constructs. In database and data warehousing analysis and design, we talked about data modelling; in business process analysis and design, we talked about process modelling; in performance improvement, we talked about optimization modelling; and in enterprise architecture, we talked about architectural modelling.

 

All these modelling constructs require extensive deliberation and organization using knowledge, experience and techniques accumulated from learning and working. If a software professional does not display passion to consistently enhance, enrich and embody his/her skills, neither can we expect him/her plays good roles of modeller, nor problem solver, nor opportunity creator.