It's not secret that we here at Blue Sky firmly believe in the importance of real-time analytical tools. However, as I've said before on this blog, it's not always about having access to all information possible at all times. That creates "analysis paralysis" and can hinder more than it helps. Part of this is that plenty of information isn't useful until it's been curated, and can be placed on a timeline, chart, or really be compared to other data points.

This is what we call "Slow BI." Don't worry, it's not a negative term at all. Here, Slow BI simply means tracking that is truly only useful in a retrospective and long term analysis. For example, if you implement a new method in your operations, whatever that may be, if you only take the measurements of productivity for the first day or week or even month to determine its success, you're really doing a disservice to yourself. It could simply have been a slow week, or you had half your employees out with the flu, or the change was so great that it took some time to get used to the new system.

What will really separate good use of BI and great use of BI is finding the appropriate moments to analyze one piece of information over another. Making this determination will allow for more useful information to be gathered, and create stronger analysis, which will in turn allow for greater improvements to your operations.