Is BI a Destination, a Journey Or a Journey That Begins With a Destination?

Nuance is a challenge for journalists. It's tough to offerFor a BI project a lifetime of two-and-a-half years
a nuanced view of dense topics - and technologyseems extraordinarily short, given the time and effort
topics are among the worst - without boring thethat needs to be devoted to delivering good BI.
reader to tears. In a recent story, I tried to bring out thePendse's survey may not differentiate between small,
(nuanced!) concept of companies starting small withtactical BI initiatives, failed larger ones and successful
business intelligence initiatives before applying BI moreenterprise BI implementations, in which case the
broadly across their business. Several of my sources,numbers may work out right, writes Thomas. Tactical
however, felt I was pitting one approach against theprojects are intended to have a short life and bad
other.projects tend to get killed quickly, so those categories
Analyst Nigel Pendse, author of the annual BI Survey,could exert downward pressure on the median.
feels it appears in the story as if he and InformationHe doesn't advocate "big" BI over "small" BI. Rather,
Builders Chief Marketing Officer Michael Corcoran"for me what counts is what works." He writes:
were "in violent disagreement" over whether BI shouldTactical BI initiatives can be very beneficial in their own
be widely deployed throughout an organization or justright, as well as being indispensible to the successful
to key users. As Pendse points out in an e-mail, he andconduct of larger BI projects. However, it is my firm
Corcoran "agree on most things." While Informationbelief that tactical BI works best when it is part of a
Builders applications are sometimes widely deployedstrategic framework.
throughout organizations, writes Pendse, end usersAgain, I'm not trying to create controversy where there
don't necessarily see them as BI and generally aren'tisn't any. Thomas obviously feels tactical BI projects
directly involved in implementing the apps. The twohave merit. I suspect Pendse will concede that
examples of Information Builders clients I cite in theenterprisewide BI projects can create tremendous
story illustrate this well, I think.value, even though they'll inevitably be more challenging
Information Builders' approach differs from otherand cost more to boot.
vendors that focus on workers who use BIOne area on which I know the men (and my other
applications in a more ad hoc manner and are "wellsources) agree is the importance of involving users in
aware that they're using a BI tool." As Pendse told meBI initiatives. They all mentioned it, though those
in an earlier interview, many of those vendors areremarks failed to make the final cut in the interest of
simply trying to sell more BI licenses.keeping the article reasonably concise. I'm now feeling
Another of my sources, independent BI consultantsome editorial remorse, since I think it's such an
Peter Thomas, takes issue with Pendse's suggestionimportant best practice, one that I've featured a
for undertaking small, tactical BI intiiatives rather thannumber of times, most recently in December. I like this
enterprisewide ones. Beginning with small projects isquote from John Colbert, vice president of research
the most logical approach, says Pendse, in light of theand analytics for BI advisory company BPM Partners:
fact that the median age of BI applications atDon't underestimate end users in the process, since
companies he surveys is less than two-and-a-halfthey will drive benefits. Users will keep doing
years. In a follow-up post on his BI blog, Thomasspreadsheets if they don't see enough benefit (from
zeroes in on that figure, thinking it seems inadequateBI). They should be pulling the project of your hands,
for a BI project. He writes:versus you throwing it over the wall to them.