Working in this domain for nearly half a decade, I have been trying to figure out some of the key challenges when it comes to designing a robust Business Intelligence solution, from text books to real business case studies as such there is no single thread you can pick up and say here it goes. The question becomes even more tough to answer when it requires a cross geographical team and cross platform integration
The answer to this question is actually subjective and depends on the domain you are working on be it retail, banking, supply chain etc etc., however there are bunch check list that you need to mark before you actually commit .
1) Scalable Data Integration
I would call this as one of the major challenge teams are facing, every integration design is ought to be outdated at some point of time, the question is what time do we set as threshold, for industry like e-commerce, banking online retail this will be a continued area of research because of cut-throat competition and business requirement changes with a blink of an eye, however if the design sustain a period of 3-4 years, I would probably call that an excellent design. One of the key thing to incorporate when we design a system is we try to capture all business scenario and integrate data at the most granular level, so that we take care of scalability into consideration. Another dimension to an element of scalability is how flexible is the design is, if a new business case needs to be developed rather than starting from square 1 its better to complement the current system with some additional work around, but yes this should not be made a habit else this might create a web of data which would be hard to maintain.
2) Long Term Solutions
Most of the time folks are trying to solve a business problem which is 2-3 years in their line of sight, technically a new business launched at least needs 5-6 years to come into break even, providing a solution for such a short term, might break down the whole structure and would incur extra cost. The key to this problem is, the participants need to be prudent enough so that they design solutions which have long lasting life.
3) Cross Geographical Team Integration
With the advent of internet, the world has become flat, to make business operations running 24x7 its always a good idea to make sure teams are coupled tightly among all geographies. Knowledge flow should be proper and the division of labor is well defined. Providing a good business solution is less of technology and more of understanding the business process, so if the knowledge flow is not correct, all the hard work done above are of no use.
4) Remove Social Barriers
Since we are working as global team, and encompass folks from different region it is a key requirement that we remove all the social barriers, the team should not be working with a local goal but should strive on a global scale, driving business is like connecting all the parts of the machine and making sure that each part is functional, with social barriers the drive may not be smooth.
5) Regular Audit
Above all, the most critical point that needs to be plugged in each stage is an element of audit, no design and solution will go perfect in single shot, however by auditing it we can make sure we are sticking to quality standard so the business users have a confidence in the solutions we provide to them.
The above checklist is certainly not perfect and its the outcome of my past experience, however if we take these things into consideration my guess is we would be able to make a good and robust Business Intelligence solution.
I would appreciate feedback and comments on this article, in case I have missed out any key aspect of this discussion.
Best
Siddharth
The answer to this question is actually subjective and depends on the domain you are working on be it retail, banking, supply chain etc etc., however there are bunch check list that you need to mark before you actually commit .
1) Scalable Data Integration
I would call this as one of the major challenge teams are facing, every integration design is ought to be outdated at some point of time, the question is what time do we set as threshold, for industry like e-commerce, banking online retail this will be a continued area of research because of cut-throat competition and business requirement changes with a blink of an eye, however if the design sustain a period of 3-4 years, I would probably call that an excellent design. One of the key thing to incorporate when we design a system is we try to capture all business scenario and integrate data at the most granular level, so that we take care of scalability into consideration. Another dimension to an element of scalability is how flexible is the design is, if a new business case needs to be developed rather than starting from square 1 its better to complement the current system with some additional work around, but yes this should not be made a habit else this might create a web of data which would be hard to maintain.
2) Long Term Solutions
Most of the time folks are trying to solve a business problem which is 2-3 years in their line of sight, technically a new business launched at least needs 5-6 years to come into break even, providing a solution for such a short term, might break down the whole structure and would incur extra cost. The key to this problem is, the participants need to be prudent enough so that they design solutions which have long lasting life.
3) Cross Geographical Team Integration
With the advent of internet, the world has become flat, to make business operations running 24x7 its always a good idea to make sure teams are coupled tightly among all geographies. Knowledge flow should be proper and the division of labor is well defined. Providing a good business solution is less of technology and more of understanding the business process, so if the knowledge flow is not correct, all the hard work done above are of no use.
4) Remove Social Barriers
Since we are working as global team, and encompass folks from different region it is a key requirement that we remove all the social barriers, the team should not be working with a local goal but should strive on a global scale, driving business is like connecting all the parts of the machine and making sure that each part is functional, with social barriers the drive may not be smooth.
5) Regular Audit
Above all, the most critical point that needs to be plugged in each stage is an element of audit, no design and solution will go perfect in single shot, however by auditing it we can make sure we are sticking to quality standard so the business users have a confidence in the solutions we provide to them.
The above checklist is certainly not perfect and its the outcome of my past experience, however if we take these things into consideration my guess is we would be able to make a good and robust Business Intelligence solution.
I would appreciate feedback and comments on this article, in case I have missed out any key aspect of this discussion.
Best
Siddharth