A recent issue of Reseller News looked at the transition of some IT resellers from "moving boxes" to selling services - including Business Intelligence services.
But the article includes a cautionary comment from Stellar BI's Managing Director, Grant Broadbent (pictured).
"If you just drop the technology on the floor you might get some
passionate soul to use it and show their fellow business unit [members] how great
it is, but if that person leaves or if the business changes its focus,
then a lot of those projects just end up dying. There’s a lot in BI that
people don’t realise."
Paul Plester of Express Data adds that teaching users how to analyse and use data is a key part of a good Business Intelligence offering.
"That type of skill is going to be more in demand, it’s not a box move
any more, there’s value add around it."
“With BI, you’re not really selling software,” says Richard Johnson,
sales director of consulting firm Cortell.
"I mean
you are, of course. But you’ve got to understand [a customer's] data
and then you’ve got to build the underlying data structure that you then
report on and do your analysis.”
Showing posts with label business intelligence. Show all posts
Showing posts with label business intelligence. Show all posts
BI - More than just technology
Friday, April 16, 2010 Posted by Grant B
I was talking to the CFO of a medium/large Auckland-based organisation the other day about that organisation's experiences with Business Intelligence. He told me that the IS team had spent a fortune on purchasing one of the popular data visualisation packages which they proceeded to put on the shelf for a while, uninstalled. Why? Because the vendor offered a "never to be repeated price" at the end of its financial year.
As if this wasn't bad enough, along came a vendor selling a data extract tool who proposed to the IS department the installation of a quick prototype of a data warehouse to show how easy it was to build data warehouses. This resulted in the IS department buying the data extract tool and commissioning a project to deploy a data mart based on the prototype to the finance department, using the aforementioned state-of-the-art shelfware data visualisation tool to deliver a few neat dashboards and sexy cubes. The project took a little longer to do than the prototype suggested (note: they always do!) and the total cost came to several hundred thousand dollars but it was an ultra leading-edge architecture using the latest, greatest tools so it was going to delight the end user community.
Problem was, the end user community wasn't involved until near the go-live date. They had no input into any requirements analysis, they weren't involved in the selection of tools and their management had not been informed of this development until long after the purchasing decisions were made. In addition, several requirements brought on by recent changes in the industry were not incorporated into the solution by the IS people because they were too busy playing with cool technology to see what was happening at the industry coalface.
When it all boils down, we know from decades of experience that there are seven discreet requirements for a successful BI project. We refer to these as the Seven Essentials for BI Success:
As if this wasn't bad enough, along came a vendor selling a data extract tool who proposed to the IS department the installation of a quick prototype of a data warehouse to show how easy it was to build data warehouses. This resulted in the IS department buying the data extract tool and commissioning a project to deploy a data mart based on the prototype to the finance department, using the aforementioned state-of-the-art shelfware data visualisation tool to deliver a few neat dashboards and sexy cubes. The project took a little longer to do than the prototype suggested (note: they always do!) and the total cost came to several hundred thousand dollars but it was an ultra leading-edge architecture using the latest, greatest tools so it was going to delight the end user community.
Problem was, the end user community wasn't involved until near the go-live date. They had no input into any requirements analysis, they weren't involved in the selection of tools and their management had not been informed of this development until long after the purchasing decisions were made. In addition, several requirements brought on by recent changes in the industry were not incorporated into the solution by the IS people because they were too busy playing with cool technology to see what was happening at the industry coalface.
The result? The solution was ill-conceived, not fit for purpose, the insight being presented by the solution was not believed by those who make decisions with it and senior finance department management had no will to make it right because they had no involvement during its development and therefore no skin in the game. The finance guys just carried on with their manually produced Excel spreadsheets and the whizz-bang BI solution was shut down.
Needless to say, these guys are a little "BI Shy" now.
This story highlights a typical problem we see in the BI space - only a small fraction of the prerequisites of a successful BI project are addressed. In this case, the IS guys assumed that the latest BI technology was the sole requirement for a successful BI project. This is a very common misconception.
There is a whole lot more to BI than technology. Decisions need to be made not just with respect to technology, but more importantly with reference to business processes, data, and the people involved in a BI solution.
When it all boils down, we know from decades of experience that there are seven discreet requirements for a successful BI project. We refer to these as the Seven Essentials for BI Success:
- Governance;
- Engagement Model;
- Delivery Model
- Performance Insight;
- Information Architecture;
- Data Management;
- and of course,Technology.
Over the next few posts, Stellar's BI experts will discuss the seven essentials for BI success in some detail, so stay tuned!
Copyright ©2010, Stellar Consulting Group Limited. All rights reserved
BI - the Key to Competitiveness
Sunday, October 11, 2009 Posted by Stellar Team
A recent survey of more than 2500 CIOs worldwide shows that Business Intelligence and Analytics top the agenda when it comes to boosting corporate competitiveness.
The comprehensive study, conducted by IBM earlier this year, compares how fast-growth companies use technology compared with lower-growth companies.
83% of respondents indicated that Business Intelligence and Analytics were key to boosting corporate competitiveness - making BI the most popular initiative across the entire survey group.
Read the full article on Forbes.com
The comprehensive study, conducted by IBM earlier this year, compares how fast-growth companies use technology compared with lower-growth companies.
83% of respondents indicated that Business Intelligence and Analytics were key to boosting corporate competitiveness - making BI the most popular initiative across the entire survey group.
Read the full article on Forbes.com
BI Tool Shootouts - A Waste of Time?
Friday, September 18, 2009 Posted by Grant B
Having just put the phone down after talking to a customer about a product evaluation process, I thought I'd share a few thoughts on BI Product Evaluations or "Shootouts". Many companies in New Zealand have dedicated a fair swag of resource to this process over the years, so here are our considered thoughts.
There are two things about BI Tool Evaluations we feel should be highlighted:
1) They shouldn’t take too much time and their outcomes shouldn’t be a deal breaker for the project.
2) They must be heavily oriented toward the end user community, as they are the ones who will be actually using the tools, not the IT people.
It amazes us when IT shops spend several man years evaluating BI tools on behalf of and in isolation from their end user community. If the entire solution was going to be developed in this tool, and the solution was only allowed to use features that were provided by this one tool for ever more, then fair enough. In reality though, with an open BI architecture in place, there is more than one way to skin the proverbial cat. No end to end solution should ever be entirely developed within one product’s development realm.
Here’s Stellar’s editorial comment on tools evaluations: Don't waste too much time on tool evaluations. While the arcane mechanics of each tool are being dissected by technical people in white coats, the end user business community is demanding a solution to their problems "right now" before their window of business opportunity closes. So whatever you do, make sure these guys get involved early and buy into the tools chosen.
Tools evaluations should be done once the BI technical architecture is established and understood. We have seen several examples of tools being selected to perform roles that they are not really capable of doing. If they were evaluated against a mature BI architecture backdrop, where these roles are clearly documented, these mistakes would not have happened.
The BI Tool segment of the IT industry is churning out some great products. In its proper role, virtually any BI Tool today is rock solid and can provide 80 to 90 percent of the functionality required by the average kiwi company. There are some “horses for courses” situations to be sure, where one tool stands out above the others in a particular role, but as a general rule, they are all pretty good these days.
Give us a holler if you need help – remember, we are 100% product independent!
There are two things about BI Tool Evaluations we feel should be highlighted:
1) They shouldn’t take too much time and their outcomes shouldn’t be a deal breaker for the project.
2) They must be heavily oriented toward the end user community, as they are the ones who will be actually using the tools, not the IT people.
It amazes us when IT shops spend several man years evaluating BI tools on behalf of and in isolation from their end user community. If the entire solution was going to be developed in this tool, and the solution was only allowed to use features that were provided by this one tool for ever more, then fair enough. In reality though, with an open BI architecture in place, there is more than one way to skin the proverbial cat. No end to end solution should ever be entirely developed within one product’s development realm.
Here’s Stellar’s editorial comment on tools evaluations: Don't waste too much time on tool evaluations. While the arcane mechanics of each tool are being dissected by technical people in white coats, the end user business community is demanding a solution to their problems "right now" before their window of business opportunity closes. So whatever you do, make sure these guys get involved early and buy into the tools chosen.
Tools evaluations should be done once the BI technical architecture is established and understood. We have seen several examples of tools being selected to perform roles that they are not really capable of doing. If they were evaluated against a mature BI architecture backdrop, where these roles are clearly documented, these mistakes would not have happened.
The BI Tool segment of the IT industry is churning out some great products. In its proper role, virtually any BI Tool today is rock solid and can provide 80 to 90 percent of the functionality required by the average kiwi company. There are some “horses for courses” situations to be sure, where one tool stands out above the others in a particular role, but as a general rule, they are all pretty good these days.
Give us a holler if you need help – remember, we are 100% product independent!
Looking Past the Flash of Dashboards
Monday, September 14, 2009 Posted by Travis B
We've been receiving a lot of interest lately from customers wanting to construct "Executive Dashboards". I guess this stems from a growing need by upper level management to more effectively monitor core business performance in the wake of the global credit crisis. Whatever the case, the need for greater visibility and awareness of key performance metrics are driving renewed interest in executive dashboards.
Dashboards are certainly nothing new. You'll find a plethora of information about them on the Internet and in various textbooks, and you're probably well aware of the various whiz-bang applications available on the market for constructing fancy visualisations. Unfortunately, when it actually comes to designing something meaningful for executive management, the message can often get lost in the over exuberant use of dashboard gadgetry... resulting in an overpowering visual experience for users.
In response to the rising demand for executive dashboards from customers Stellar's resident dashboard specialist - Chris du Toit - has put together an excellent discussion paper to draw attention to fundamental design considerations for effective dashboard creation. If you're currently constructing an executive dashboard, or thinking about it, Looking Past the Flash of Dashboard Design will help to refocus your efforts on what is and isn't important, which of course will help you to fulfil your greater goal of providing an effective platform for delivering business insight to management.
