BI Leadership Article

It isn’t often you come across a good article that brings together developing a Business Intelligence vision and the behaviours BI leaders need to demonstrate to make this vision a reality.  Well worth a read if you are a BI leader or are just trying to understand them…8)

Creating Shared Responsibility for Success in Your Business Intelligence Team

I’m glad to see we are already doing some of this in my current organization, but there are a number of areas discussed in this article that can be improved.  The fun never ends!

P.S. Apologies for the lack of updates to this blog, good weather calls!

The BI Experience: One Size Doesn’t Fit All

The enemy of BI adoption is treating all your users the same.  Each role and person in your organization will use your BI platform differently, so you must deliver a solution that fits each individuals needs.  You should consider aspects such as tool complexity, usage of visualizations, navigation and accessibility.

Executive Users will be best served with high level dashboards, mobile access, and real time alerts.  The typical executive (an effective one anyways) doesn’t spend a great deal of time behind their computer.  When they do, they are likely short on time and are looking for the bottom line on their organization’s performance.  Dashboards are great for displaying all the relevant information on a single screen, allowing your user to have a one stop shop for when they are at their computer.  With most of an executive’s time comprising of meetings and talking with folks, having mobile access from their handheld device (BlackBerry, iPhone, etc.) will provide them with metrics where and when they need them.  Couple this with real-time alerts via email, and your Executive users will be able to leverage your BI platform according to their needs.

In contrast, front line users (Customer Service Representatives, Sales Representatives, etc.) need intelligence that is bundled in with their business processes.  To drive maximum effectiveness you want to inject Business Intelligence into the operational systems these people use every day.  This can take forms such as surfacing a Customer Lifetime Value score to assist with save strategies when a customer is calling to disconnect, or providing real time alerts into your Customer Relationship Management system when a critical order deadline has passed.  You certainly don’t want these roles that are the face to the customer wasting time flipping between their operational screens and the BI portal!

The way you provide a tailored user experience to your BI clients is critical to drive adoption towards the goal of pervasive BI.  Spend extra time and attention to this aspect when you are planning any major BI deployment and you will reap the benefits.

Related Posts:

• Icing the BI Cake with User Experience
• It Just Has to Work
• Will the BI portal last?

Icing the BI Cake with User Experience

The true power of BI is the ability to present actionable information to decision makers.  All the data quality governance, ETL excellence, and dimensional analysis will mean nothing if the business can't intuitively interact with the information through their BI tools.  You must ice the cake with an exceptional User Experience to drive the most value from your BI investments.

 

A focus on User Experience is key to your BI program's success for the following reasons:

• Enables a faster "mean time to answer".  Reducing the number of clicks and searches makes your applications more satisfying and efficient to use.
• Consistency.  Once a user understands how to read one report or dashboard, they can apply the same methodology across all BI applications.
• Expose correlations.  Simply combining data on a visualization like a chart or a scatter plot can immediately show a correlation between 2 measures that are not as readily apparent as pure numbers.
• Guide your user through tried and tested analysis processes to expose the knowledge of power users to the larger user base.
• Simplify the experience of finding information by improving navigation structures.  Ensure your search capabilities are optimized to return the most relevant results.

In order to drive the most value from your user's experience you need to have a consistent approach across all the user touch points in your environment.  My recommendation is to designate someone to be accountable for User Experience across the board.  Depending on the size of your BI program this may be part of someone's role, a full person, or a small team.  Only with a centre of excellence can you drive consistent standards across all groups creating end user content.  This team would also serve as a consultant to projects to ensure that the reporting and visualizations are designed to be intuitive and useful.

You can have all the wonderful architecture and data quality you want, but without an effective User Experience your clients will not see the value of all your hard work and will be less likely to adopt your BI environment.  First impressions only happen once.

Related Posts:

• It Just Has to Work
• Cut to the Truth: Answer a Business Question

The Tactical Data Mart Advantage

The capabilities of current BI tools allow us to drive down the costs to develop BI applications / data marts.  This means that we can quickly develop tactical applications leveraging standard tools and methodologies to reduce development cycles.  This enables the deployment of applications to support specific decision making problems that would normally not be supported by a quality BI environment due to the short turnaround required.

Some people get upset about building these so called silos that aren't integrated.  I take a different perspective that these tactical data marts expose the power of tactical Business Intelligence, and if you manage it well they are a great complement to your core infrastructure.

"A good solution applied with vigour now is better than a perfect solution applied ten minutes later.” - General George S. Patton

It is critical that you have a checkpoint or a regular environment review that you can rely on to take one of the following actions at the end of the decision making life cycle:

1. Decision has been made and there is no need for continued access to the data mart.  Simple response, retire the data mart and free up system resources for the next initiative.  Celebrate the success.
2. The information within the data mart has continuing value to the organization.  In this case you need to have room in your requirements funnel to incorporate the data mart into your permanent BI infrastructure.

Don't hold your business back by sticking to a traditional release cycle.  Build a team within your BI program that can quickly spin up the appropriate BI solution to support tactical decision making.  You can't win the war if you don't win a battle now and then!

Data Integration and Your Organization

Today we had John Schmidt, VP of Global Integration Services at Informatica come speak to our teams about best practices for setting up an Integration Competency Centre (ICC).  John made an interesting point that your various Integration functions may be included in Competency Centres in different ways depending on the organization.  

If you have researched Business Intelligence Competency Centres (BICC) you will often find a Data Integration function as one of the functions staffed within the BICC.  However, Business Intelligence is just one part of the pie when it comes to integrating information across the enterprise.  You will also need data integration expertise for data quality, Master Data Management, and other non-BI specific projects.  A number of these projects may not impact BI significantly if at all.  If you want a holistic view of data across your organization you must either create a standalone ICC with strong ties to your BICC, or incorporate all areas of integration practice within a higher level Information Management Competency Centre.

Good BI is enabled by quality data.  Since data quality lives along the information management timeline from your source systems to your analytic databases, it is critical you have technology, process and people engaged all the way along to ensure the best data is delivered for BI.

Keeping your BI environment clean

Over the past year or so the "green" revolution has been sweeping IT as a way for organizations to reduce their environmental impact and to cut costs at the same time.  This has driven the need for robust measurement systems to manage the transition to being a green organization.  A number of the big BI vendors have come out with pre-packaged solutions to drive more "green"  for organizations by encapsulating best practices.

It is great for BI teams to provide these systems to the organization, but we would be remiss to not apply these techniques within our BI environments.

What can you do?  One thing I recommend you do is to perform a complete review of your Business Intelligence data stores and reporting at least once a year.  The overall goals of this review are to remove obsolete information and to address any deficiencies.  There are a number of activities you could incorporate into this review:

• Validate with your business stakeholders that the information has continuing value.  Solicit feedback on the information that is valuable, but is somehow incomplete.
• Review usage statistics for data marts and reports to determine what content is accessed regularly and by whom
• Validate that the report or data store reflects current business logic
• Gather metrics on batch load processes, response time, and storage usage to ensure your environment is stable and is scaling as volumes grow.  I've never heard of a Data Warehouse that shrinks in size over time.

The majority of these activities do not cost you a dime other than people's time.  This is especially attractive in a financial environment like today, when capital spending is being closely scrutinized.  Putting in place a regular program such as this will enable your organization to realize the following benefits:

• Reduce maintenance costs for your BI environment.  Less data marts and reports to support as your environment grows and changes.  You can quickly find yourself drowning in too many items to support.
• Lower the related data centre costs to support your infrastructure.  Believe it or not, all your ETL processes, database servers and storage solutions consume significant amounts of power and cooling.
• Identify duplicated information that is redundant.  Root out conflicting business definitions.
• Reduce the opportunity for information overload.  Having focused information will allow your users to find what they are looking for quicker.

Spare the environment and lower your costs by supporting less while extracting maximum value from your existing investments.  You can't beat this type of ROI!

CIA: Collaboration in Action

One of the greatest examples of effective collaboration is the partnership between 007 and Q in the James Bond movies.  Q would design and build gadgets that seemed to be uniquely suited to the next round of challenges and daring escapes James would encounter on his upcoming mission.  During each movie it appears that James just drops in to Q's lab after receiving his assignment to find everything he needs ready and waiting for him.

Being this ready for anything doesn't happen magically, but is the result of an agile development methodology.  Delivering information solutions is a constantly changing landscape that can benefit from applying the design principles used in Q's lab.

• Rapid Prototyping - Every time James would drop by, the "latest" version of a new tool is ready to be tried.  Take every opportunity to show your users the look and feel of your solution, this will unleash their creativity and you will benefit from their increased engagement and suggestions.
• Fail and Fail Fast - These gadgets would often have unintended side effects, or would explode spectacularly.  There was never any other reaction than cool, collected analysis to fix the problem.  Create an atmosphere where the ability to quickly fail, learn from the mistake, and try again happens as quickly as possible.
• Open Environments - Tests were not undertaken in closed laboratories, but were instead conducted in environments that were open to other researchers and their devilishly handsome customers.  Have a physical environment that encourages collaboration with everyone that is core to a project.  Virtual environments are great, but nothing replaces in person communication.
• Continuous Improvement - Every time 007 returns his shot up, smoking, destroyed vehicles, he provides feedback directly to the designer on what did and didn't work properly.  Find different channels to receive feedback from your users, and make a point of acting on it.

Business Intelligence is not something that is done well in isolation.  Encourage your team to use the above concepts, and look for every opportunity to engage the right people in your initiatives no matter what area of the organization they are from.

"Now do please remember to take care of all this equipment 007...DON'T TOUCH THAT!!...That's my lunch!" - Q