What’s new and what’s being sold as new? Part I

May 14th, 2010 by Quaid Saifee

Sorting  wheat from chaff in BI?  What’s must, good to have or useless depends on your needs.

Well like everything 2.0, BI has its own 2.0 features and functions.  Some of that is old stuff in a new package.  Let’s go over the list of new features / functions / technology in BI.

-  Mobile BI: With the advent of smart phones and particularly iPhone, this is one technology feature which BI software leaders cannot afford to miss.  Remember just showing the same  reports/dashboards on the mobile screen is not Mobile BI.  Mobile BI is still in its infancy.  Here is a good summary on mobile BI progress over past few years.

-  Data Visualization: I wish we had the dashboards when I was working in the railroad industry years back.  I remember most of the dispatch staff would print tens of pages to look at few numbers, to highlight them and store them in a special folder.  Charts, graphs etc on a dashboards are not only making executives interested in getting the information they need but are also helping middle level manager and operational line worker.  Why look at 500 page report to find a number, which can be shown in a dashboard, finally management by exception is becoming the norm.  No BI stack is complete without dashboard and there are many niche dashboard vendors in the market now.

-  BI in the cloud: Like everything else BI can be on the cloud as well, but should you put it there and why?  Bob Mitchell has a good piece in Computerworld on this topic

-  Analytics: Business Analytics Vs Business Intelligence, most of the BI vendors have tried to blur the lines between the two. I have rarely seen a power user without the power of Microsoft Excel even when they have the latest and greatest BI tools at their disposal.   The fact remains that their analytics users in the companies who need to analyze data never analyzed before (not in the datamart) and ask the questions never asked before.  Rock Gnatovich wrote an article regarding this in CIO magazine.

-  Search: Search should of course be a natural part of any BI tool.  It is easier said than done.  Most of the enterprise BI tools have basic search functionality like searching for a report with specific title or even a field in the report.  Also there is also a whole new category defined by Gartner called “Information Access Technology”, where the products bring the structured and non-structured data together for analysis, there are specialist tools like Endeca which are leaders in this category.

-  In-memory BI: This is one of the hottest term in the BI field and for a good reason, who does not want faster response from their BI applications.  Nigel Pendse has written a great commentaryon this, very interesting and it puts things in context.

Coming up in part II

-          BI appliances:

-          Data Mining

-          Predictive analytics

-          Open Source  etc.

Quaid Saifee

Say YES to NOs

February 12th, 2010 by Quaid Saifee

All of us have seen quite a few articles written on best practices to accomplish Business Intelligence projects.  Couple of years back when we were involved in a BIG BI project for a Fortune 100 company, those articles did not help.

As we went over lessons learnt from that project, I realized that it is more important to emphasize DON’Ts rather than DO’s.

I am making the assumption that you are embarking on a decent size (5-8 resources, multi-hundred thousand dollar project, fixed cost project).  The key points should be applicable whether you are doing this project internally or hiring a consulting company to do it for you; doing this on fixed cost terms or on time and material basis.

- Don’t start without exact specs and timeline (clarify that fixed cost depends on these two factors), this does not mean that one cannot modify the scope or implement iterative development methodology, but broad specs should be well defined before the start of the project

- Don’t start with more than couple of business processes (Ralph Kimball)

- Don’t start without blessings from the business users and IT staff (adversarial relationship with anybody in either of these groups can result into a disaster)

- Don’t start without identifying key business sponsor and key IT decision maker (and daily/weekly time commitment from them)

- Don’t start without a functional requirement document in place

- Don’t start without a designated / dedicated project manager (qualification and quality of the project manager is key)

- Don’t compromise on the quality of the resources (delay the project if need be if the needed resources are not available)

- Don’t follow the big bang theory (show incremental progress, this should be part of project plan)

- Don’t staff fully right from the “get go”.  (Technical: PM, Data modeler, ETL architect, Sr. reporter; Business: Power users)

- Don’t say Yes to everything client (internal or external) wants, make sure to convey your opinion about the implication of changes on cost/timeline (in writing)

Got more Don’ts, let me know!

Quaid Saifee

Business Intelligence; Really?

January 22nd, 2010 by Scott Smith

As the first blog of hopefully many, I thought I would write about my chosen line of work – Business Intelligence, or more comfortably, BI. Given that you’re taking the time to read this, you likely already have your own ideas of what BI is all about: data warehouses, reports, dashboards; basically any set of processes and technology that provide timely business information to end users.

But what does BI really mean? Let’s see what my good friend www.dictionary.com says about BI:

Business Intelligence
- the process of gathering information about a business or industry matter; a broad range of applications and technologies for gathering, storing, analyzing, and providing access to data to help make business decisions; abbr. BI

Interestingly, I see the word “business” a couple times, but no mention of “intelligence” anywhere. Hmm…I wonder why? I think it’s because intelligence is in the eye of the beholder. Let’s go back to the online dictionary to see what they say about the word intelligence:

Intelligence
- the capacity for learning, reasoning, understanding, and similar forms of mental activity; aptitude in grasping truths, relationships, facts, meanings, etc.

So my read on that definition is that intelligence is about mental capacity, the ability to interpret facts, and aptitude. Nowhere in the definition does it say anything about what to do with intelligence, assuming you’re blessed with it in the first place. In other words, intelligence is merely the foundation for good decision-making.

And therein lies the rub: To quit the wordplay for a moment, this definition of intelligence is exactly why we, as BI practitioners, seem to struggle with some of the basics of justification for what we do and sell, like return-on-investment for BI, and its value compared to other IT investment options. Too often, the details of a BI investment are left to IT, focusing on providing BI capability back to the business – without the necessary partnership to ensure that BI actually produces net positive business results and real ROI.

Let’s take one last trip to the dictionary and perhaps look for a more appropriate moniker:

Wisdom
- the quality or state of being wise; knowledge of what is true or right coupled with just judgment as to action; sagacity, discernment, or insight.

Wisdom, using intelligence as a foundation, provides access to the truth, good decisions, and the experience to take appropriate actions when intelligence alone in not enough.

Business Wisdom: I like the sound of that. Want to buy some?

Truly Yours,

Scott