The Last Mile of Business Intelligence
By Zach Gemignani
November 1, 2007
Find more about:
bi
reporting
“The last mile” is a term that often is applied in the telecom industry in reference to “the final leg of delivering connectivity from a communications provider to a customer.” It is an expensive and complex step due to the challenge of pushing information from centralized, high capacity channels to many diverse end-points where information is ultimately used.
We think there is a “last mile” problem in business intelligence too. This critical bridge between data warehouses and communication of insights to decision-makers is often weak or missing. Your investments and meticulous efforts to create a central infrastructure can become worthless without effective delivery to end-users. “But how about my reporting interface?” you wonder. That’s a creaky and narrow bridge to rely on for the last mile of business intelligence.

Listening to our clients, we are confident the last mile is a real problem. The ultimate source of this failure is less clear. Here are a few of theories:
1. The engineers who built the data warehouse build the interface. No offense to the talented individuals who can push around, clean, normalize, and integrate data—but they may not be ideally suited to designing a user interface for non-technical users. A designer wouldn’t create charts that look like this (our favorite example of chart-based encryption):

In the worst case, developers are dismissive of user experience. I’ve met with IT folks who felt confident that providing a massive data table would provide a suitable solution for delivering information to users. “Hey, they’re getting their data. Is there a problem?”
2. Reporting is considered the fundamental mechanism for working with data. Here’s a framework we’ve started to consider in thinking through the multiple approaches for getting value from data:

- Reporting lets you monitor things that are well-understood and relatively predictable.
- Exporation or analysis helps you understand new processes and erratic and shifting behaviors.
- Presentation is about communicating insights and understanding, often building on both reporting and analysis.
Many people assume that a reporting tool is sufficient to do in-depth analysis and communicate results. That’s like trying to build a deck with a screwdriver.
3. Poor fundamentals in information display. Despite the efforts of folks like Edward Tufte and Stephen Few, general literacy in this area is still low. Shiny, 3D pie charts are still acceptable, even desirable in some places. Particularly disturbing is the persistence and pervasiveness of this problem in Excel where there still remains some confusion as to why this is bad information display:

You don’t have to go any further than the Dashboard Spy to find examples of the visual muck that is commonplace.





16 comments | Show all comments only the last 5 are shown
Jorge Camoes said:
Zach, with low literacy levels you can't say "this is good, this is bad", because people will not understand why. A reference model is not enough, you must guide them step by step, make them compare outputs and explain why a 3D pie chart is not good for them. This is not easy and takes a long time, but there is no other way, I think.
Rob said:
Jorge, check the link to Stephen Few's website. He's got a whole page of "bad graph" examples along with analysis and explanation of a proper solution. Pretty good reading so far.
Dave Katz said:
I like the framework, but I think it's missing the cyclical relationship between these three activities:
1) Start with exploration/analysis, until you get to the point where the thing you're analyzing is "well-understood."
2) Develop some reports that help you identify patterns, trends, and notable exceptions.
3) Present the "insights and understanding" that you found along the way to your colleagues - this is bound to generate new questions, which brings us back to step 1.
This is admittedly oversimplified, but I think its a workable model.
I envision the diagram of this process as a circle with arrows showing the process flow, rather than as a triangle.
Zach said:
Dave, I agree that there is a flow between these modes. The problem is when people don't recognize that they are using reporting for presentation or presentation for analysis, and so on. Also, I thought about placing "dashboards" between reporting and presentation as it is a kind of hybrid.
Jorge Camoes said:
Rob, I know the page and it is a good starting point. This is one of the things I also try to do in my blog. But you need some sort of interaction, to explain, overcome objections, etc.
I would say that we are selling something that no one wants to buy. Imagine an ad were everyone is happily drinking and socializing. Then we must sell the message "don't drink and drive". People know you're right, but they'll keep drinking (and using 3D pie charts because the boss likes them).
Mohit Mahendra said:
Spot on identifying the problem, and I like the model you presented. The last mile challenge is probably more a people issue than any other. Exploration, understanding and presentation of insight require unique and uncommon skills, and talent. There is only so much that can be embedded and automated in a system. After that it comes down to the people that deliver the last mile.
Dave Katz said:
Friends don't let friends build 3D pie charts.
Tony said:
Hahaha, nice one Dave!
What's worse than a pie chart? A 3D pie chart!
Sanjay Tamta said:
I'm surprised that you think of the "last mile" as a pervasive issue. Yes, it is true that several interfaces leave a lot to be desired in terms of content and usefulness, but I contend that leading corporations are very familiar with and extremely good at mitigating the risk of "lost in translation" between technical and management teams. With 15+ years of robust global business growth and the emergence of IT as key enabler, corporate success is in large part attributed to the availability and relevance of key business insight through the use of well designed EIS and BI systems. So I agree with your hypothesis in part but would say that it is really a matter of the experience level of the people involved. When you look at leading BI implementations, you will see tech and management working in concert to create value for the organization. It’s really no different from building any other kind of system.
michel g said:
I keeping thinking of Mr Covey when I deal with clients facing this issue. I believe it is either his 1st or 2nd principle that says, "begin with the end in mind." I can't help but think that the last mile is so challenging because we start with a list of requirements or features and not of desired outcomes.
Jennifer E said:
We are in the "Last Mile" in my project where I am embarrassed to say that I manage the User Interface. I struggle with everything you have mentioned above. Unfortunately, the company I work for does not feel it important to invest in UI and my team is sparse and has been over run with the Data Modelers with no design sense. If just 2% of our time was spent on usability we would have much easier to understand product and the training to use it would be greatly reduced.. I will keep reading your blogs.
Zach said:
Jennifer: I'm sorry to hear about our situation. It raises the question: Does a lone, screaming user interface person in the Data Modeler woods make a sound? We'd be happy to lend a sympathetic ear if you want to reach out.
Sanjay: Our experience has been very different from what you describe. We've found it rare that management and tech work so smoothly "in concert." I have yet to see a BI implementation that consistently brings joy and insight to end-users. Furthermore, it seems a stretch to attribute 15+ years of global business growth to the success of these EIS/BI systems. On the other hand, it seems like you have a Harvard Business Review article in you.
Sanjay Tamta said:
Zach:
That was funny and your point is well taken. Actually, I think an HBR article may just hit the spot.
Good blog btw.
Sanjay
James Taylor said:
Nice post and inspired me to post on something similar over at http://www.edmblog.com/weblog/2007/11/mistakes-in-the.html
JT
Mark said:
Good post and you can see similar examples at <a hfre="http://www.dashboardzone.com">Dashboard Zone</a>
Sanjay Tamta said:
Zach:
Has your firm done any BI work in the area of Social Network Analysis?
Thx
said:
Add a comment