Requirements gathering. So many organizations don’t realize this is often where success in a Business Intelligence (BI) deployment lives or dies.
When it comes to BI, we have all heard that BI is more than just simple reporting. That’s become the BI vendor’s mantra.
However, the challenge we see all the time is how to realize the tremendous benefits of BI beyond reporting or even making existing reporting more valuable. Through our experience and working with our clients, we have developed a proven, repeatable process to help make the vast promises of BI a reality.
It all begins with the premise that BI is not a tool, but rather part of the business process that should be used to improve business processes. Unfortunately, traditional report requirements gathering procedures have focused on – wait for it! – reports. In essence, that process is flawed from the start.
If an organization simply wants reports that may or may not assist the business process or answer business questions, then the old, outmoded approach is fine.
What happens if you go down this road?
Well, tunnel-vision happens: if you ask users what type of reports they need, they will provide an answer based upon the limits of their experience and job domain. Answers will be derived from what they use now, problems they have experienced in getting data or information, and “individualized” not process-based needs. Their perception is based upon the knowledge or lack of knowledge of the true capabilities of BI.
That’s a myopic – and oft-committed – error when trying to establish a real BI practice.
Embedding Bi into the business process is really an exercise of peeling back the metaphorical onion. In looking at the diagram below, if we think of a business process such as AP invoice payment, each process is surrounded by six key questions/considerations. By securing answers to these questions, we can help ensure that the requirements gathered do not result in a siloed report and that the downstream and upstream impact of this information is understood and usable. As these questions are asked and answers interpreted, they ultimately influence and refine what is being asked for. This inevitably leads to improved business intelligence far beyond glorified reporting.
This is only the tip of this discussion. If you would like to see additional detail and a practical example laid out in real-world terms, register for our free whitepaper, MiPro’s Business Intelligence Manifesto: Six Requirements for an Effective BI Deployment. It provides much more information and expands upon the theoretical with plain English examples.
Also, if you would like further information on an enterprise BI strategy or BI applications in general, please email me. I’m a nice guy. If social media is more your thing, you can follow us on Twitter or become our fan on Facebook. Or, if old school RSS is your gig, you can subscribe here.
- Business Intelligence Apps: Build vs. Buy
- Business Intelligence: A Picture (or Flash Demo) Is Worth a Thousand Words
- Twitter vs. Enterprise Software
- Living Together: Oracle BI and PeopleSoft
- Back to basics: Why choose an enterprise Business Intelligence tool, anyway?
- Using BI to Survive the Recession, Part I
- Using BI to Survive the Recession, Part II
- Business Intelligence in the real world: Aligning metrics (Part I)
- Business Intelligence in the real world: Aligning metrics (Part II)
Related whitepapers (PDF):business intelligence, business process, enterprise operations, enterprise software, IT, management, reporting, software requirements Posted by