BI maturity models

With most companies listing BI within their top agenda, and with the rising costs and confusion around proving the worth of BI and justifying its costs, it makes sense to try and understand the evolution of BI adoption and maturity in organizations. Knowing what is possible with BI and knowing the challenges and pitfalls allows organizations to plan their BI strategy and implementation.

There are quite a few schools of thought and available literature on the lifecycle of BI implementation and maturity in organizations, defining the models. Most are proprietary models provided by consultancies, which are primarily based on technical point of view or applies the knowledge management function to BI, following the Ladder of Business Intelligence (LOBI) model.

LOBI includes 6 levels of maturity moving up the knowledge management value chain from Facts > Data > Information > Knowledge > Understanding > Enabled Intuition.

There are several other models in the public domain e.g.

  • Business Information maturity model
  • AMR research’s BI/Performance management maturity model
  • Business Intelligence development model
  • Business Intelligence maturity hierarchy
  • Infrastructure optimization maturity model

I’ll not go into the details of the models above but discuss the three of the more popular and well documented models available.

1. The TDWI BI Maturity Model

The Data Warehousing Institute (TDWI) is a premier body in the field of BI and eponymous Data warehousing and proposes a six stage BI maturity model. The underlying assumption being that BI implementation in organizations typically evolves from a low-value cost centre operation to a high value strategic utility to provide competitive advantage.

Stage 1: Prenatal – Executive perception is that of a cost-center, which primarily churns out static reports for management operational reporting. It is also the stage which costs the most.

Stage 2: Infant – The BI function’s role is to inform executives, with several reports leading to “spreadmarts

A ‘Gulf‘ separates Stage 2 and Stage 3.

Stage 3: Child – The BI function’s role is perceived to empower workers, and this is the first evolution into an analytical system where OLAP and ad-hoc reports are used off data marts.

Stage 4: Teenager – The BI function has evolved into a performance monitoring system by now, using Dashboards and Scorecards, supported by data warehouses.

A ‘Chasm‘ separates Stage 4 and Stage 5.

Stage 5: Adult – This is where the ROI from the BI function shoots up, with predictive analytics answering what-if questions making the BI a strategic utility. The TDWI thinks that organizations’ BI architecture has evolved to have enterprise DW by now, with BI becoming a ‘Drive the Business’ function.

Stage 6: Sage – The BI function at this stage has the highest ROI and decreasing costs based off Analytic Services (SOA) with pervasive BI (e.g. embedded BI) making it ‘Drive the market’

2. The HP Business Intelligence Maturity Model

It has 5 stages based on the evolution of Business enablement, Information technology and program management.

Stage 1 – Operation (Running the business) – involves ad-hoc solutions focused at project activities alone

Stage 2 – Improvement (Measuring and monitoring the business)– involved localized solutions with project management

Stage 3 – Alignment – includes shared resources with program management and governance integrating performance management and BI programs

Stage 4 – Empowerment – includes enterprise operationalization with portfolio management focusing on organization innovation and people productivity through knowledge management

Stage 5 – Transformation (Change the business) – involves enterprise services tracked by service management creating strategic agility and differentiation

3. Gartner BI Maturity Model

Gartner, the IT research and advisory group’s BI maturity model is based on 3 key areas of assessment – people, processes and metrics. It has 5 maturity levels:

Level 1 – Unaware – Spreadsheet and information anarchy, one-off report requests

Level 2 – Tactical – Usage limited to few executives with data inconsistency and stovepipe systems

Level 3- Focused – Specific ser if users realize value, with focus on specific business need and BI competency centre (BICC) in place

Level 4 – Strategic – Business objectives drive the BI and performance management systems with well defined and enforced governance policies and standards

Level 5 – Pervasive – Use of BI is extended to suppliers and customers, information is trusted (holy grail of single version of truth) with analytics embedded in business processes

Barriers to BI adoption and maturity

The 3 models discussed above do a good job of explaining the continuum of maturity levels, which makes it difficult to identify explicit stages, however the common theme across these are:

  1. Each model has at least 5 stages of maturity – this is more than a simple 1-2-3. This indicates the path of BI evolution is longer and more complex than most think while jumping onto the BI bandwagon
  2. Each model starts with operational / one-off reporting and culminates in pervasive BI where BI is embedded in business processes and provides actionable insight for strategic advantage
  3. The models do not focus on technology alone and hinge on the involvement of people and process as well. Moving from one-off reporting to driving the enterprise involves big changes in organization culture and business processes and not just implementing the latest BI tool off the market.

The main barriers to BI adoption and demonstrating its worth as a strategic tool lies in its complexity. BI is a broad area encompassing both technical and non-technical aspects like people and process; therefore the models can only provide a prescriptive framework which needs to be adapted by each organization. It is important to understand that various departments of an organization can be at varying levels of maturity and not every organization follows the same trajectory of evolution or has to go through each stage.

It is however noteworthy that for organizations trying to move from basic levels (e.g. TDWI Level 2 –Infant stage) to higher levels (e.g. TDWI Level 5 – Adult stage) may find it very difficult to leapfrog levels. In fact regressing stages is also possible due to changes like mergers and acquisitions of organizations at different levels of maturity where differences across people, processes and technology may be difficult to reconcile or could be delayed. The TDWI model recognizes these difficulties as:

  • The Gulf – between level 2 (infant) and level 3(child) – mainly due to differences in executive perception, data quality issues and spreadmart anarchy
  • The Chasm – between level 4(teenager) and level 5(adult) – mainly due to differences in executive perception, spreadmarts, architectural inflexibility or lock-ins

It is important to take lessons from the BI maturity models and develop a BI strategy while planning to implement BI, rather than as a bolt-on which can provide instant ROI. The strategy needs to focus on quick wins at inception to build buy-ins and get executive sponsorship which is critical to the funding of the BI program and would help overcome organizational barriers in people and processes, and then should build on its success with incremental gains and asking the right questions. We’ll look at developing a BI strategy in a subsequent post.

About these ads

11 responses to “BI maturity models

  1. Pingback: Link Resource # 41 : Jan 06 – Jan 13 « Dactylonomy of Web Resource

  2. Pingback: Link Resource # 42 : Feb 01 – Feb 24 « Dactylonomy of Web Resource

  3. Pingback: Link Resource # 43 : Mar 01 – Mar 24 « Dactylonomy of Web Resource

  4. Pingback: Link Resource # 44 : Mar 24 – Mar 31 « Dactylonomy of Web Resource

  5. Doug Brockway

    The TWDI model is laughable:
    1. Starts out with very high costs and much lower value.
    2. It has no sense of time and thus no sense of payback period
    3. There is a major gulf prior to value exceeding cost
    4. The gulf and the steps are both based, in part, on executive “perception”
    Which won’t be good with all this spending for marginal value…
    5. Somehow, toward the end, costs go DOWN… IF the model was showing unit costs, likely, but total costs will go up with success as there is more use, with success
    6. At no place in the model can one see what “use cases” might be served, or as other wise stated what “questions can be asked [and answered]”
    Said another way, you can’t see in the model anything about the business impact. Who, but a cost-center person, would ever accept this?

    It also, as do many, uses a market share bell curve to explain a learning curve maturity. It is true that they are tightly linked but they’re used for different purposes for a reason….

    Like

    • Hello Doug
      To clarify your understanding – the model reflects the maturity curve which is not necessarily related to time. Different organizations remain stuck at various stages of maturity for various reasons and the time, consequently payback varies widely. It is not for TDWI to prescribe it as a best practice if you thought so, but rather to appreciate the challenges that jump on to the ever expanding hype around all things about BI and data.

      HTH
      Maloy

      Like

  6. I have also one for knowledge-based performance management. Although the focus is on PM, it contains many aspects of traditional business intelligence, too. Check out http://www.pm-index.com/ for more information.

    Like

  7. Great Post! Well said.

    Like

  8. Pingback: Business Intelligence Maturity Assessment | James Serra's Blog

  9. Pingback: Know about New and Emerging BI Trends

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s