As the business intelligence (BI) industry continues to grow and businesses begin to understand the need for an integrated information solution, the question they find themselves often asking is: what's next?
There is enough general literature on the topic to provide a basic idea of what to do. However, companies need to understand the methodology that underpins a BI solution to be able to correctly ascertain what solution is needed, how it will work and what it will look like.
It is this understanding that will allow a BI solution to be implemented at a practical level and ensure the identified business drivers are met. In this way, the company can have an idea of the roadmap its BI solution will follow - for it should not be a destination but rather a step in the organisation's information management journey. It is this roadmap that allows for the methodology and solution to adapt to changing business needs.
Formulating the roadmap
In the end, the solution shouldn't be about the product, but rather about the value added to business.
Nitesh Vallabh is a director at PBT Group
Firstly, the requirement gathering process needs to be specific for a BI solution - the questions that should be posed depend on the outcome and orientation that is driving the need for the solution. From here, look at how the solution will logically be broken down into iterative phases.
This allows for the identification of the detailed requirements of the business and the value that is being delivered accordingly. These iterative phases also act as a feedback mechanism, ensuring value is realised early on in the process and that identified business drivers are continuously met.
Nowadays, there are a number of technologies that are widely available on the market to meet various requirements, but it has become increasingly difficult to tell the difference between competitive products. It is thus essential to formulate specific selection criteria that will be used to assist in the decision process.
These criteria need to ensure the technology is able to handle the volume of data, the number of systems, the complexity of information models and the expectations of the business.
All of these criteria influence the decision-making process, along with additional factors such as cost and supplier relationships. Therefore, it is not only important to understand what is needed in a solution, ie selection criteria, but there are a number of supplementary key questions that should also be considered during the decision process.
Does the organisation have existing suppliers that will be able to provide the solution? Is the provider a specialist in the BI space - or does it offer many services? How long has the solution been in existence and does the vendor have a product/solution evolution roadmap?
Getting support
These questions need to be answered in the requirements documentation and the architecture guide - which lays out the requirements for each phase and the technical specifications that will guide the design of the solution before it is implemented. What's more, these questions and guidelines should assist in choosing the appropriate solution provider.
Remember that the solution provider should become a trusted advisor. The provider should be able to guide the company through the entire implementation process, to ensure the process is understood and can be linked back to the set objectives, because, in due course, the organisation will need to introspect the BI solution.
By selecting a provider that is product independent, companies ensure product issues dissolve and business value comes to the fore. In the end, the solution shouldn't be about the product, but rather about the value added to business.
For it is the business that will ultimately drive the look and feel of the BI solution. Therefore, it is essential to have at least one person in the business dedicated to treating information as a business asset.
By working closely with the provider and going through the necessary training, this dedicated information specialist will be able to understand what solution has been implemented and how it works.
So, when all is said and done, the key to 'what's next?' is to understand the requirements that are needed and thereby manage expectations. It is also important to be prepared for change.
Start small so that change is minimised and benefits and value-add can be quickly and easily seen. This will make the change process and organisational buy-in a simpler and easier process.
Finally, let the requirements of the business pave the BI roadmap and drive the solution, not the products. It is only then the company won't be asking 'what's next?', but rather 'how do we maximise the BI potential?'
* Nitesh Vallabh is a director at PBT Group.
Share