Reporting

Information Silos and Other Images

Images of the “Information Silo”, the “Data Warehouse”, “Data Management” and “Business Intelligence” could undoubtedly conjur up humorous images for the graphically or artistically endowed technologist.  Traveling through farmland as I often do, I often see the farm silos and chuckle to myself as I think of ”Information Silos”.  I wish I had the talent to create caricatures of the images I think of when encountering these terms - I’m sure they could evoke a chuckle from somebody other than I.

Anyway, that being said, these terms are no laughing matter for those faced with the real challenge of making simple the complexity of data available to companies today.  From my experience I’d say that most companies - even those single location small companies, have a multitude of information stored in a multitude of systems.  The “systems” containing this data may be an individual PC, a company ERP system on a server, a sales (CRM) system (maybe on a multitude of salespersons laptops) - each its own “silo”. 

There are many stories of failed BI implementations.  Why?  I would posit that users trust their data and information, but not necessarily that coming from say, the IT department.  They know where “their” data is coming from, how it was collected, and it’s meaning - because its “theirs”!  Whether it presents a complete picture, or is applicable in all instances is totally irrelevant - just ask that branch manager, or department manager … or whoever has the data.

That being said, I’d say that perhaps key to getting the most value from the data you have available is getting the buy-in of the end-users of the data in regard to data source and reliability.  If a data source is to be used, do the end-users “trust” the data?  No trust - Don’t use it!  An interesting post suggesting 3 causes of failure for BI implementations is available here - an interesting read.

Small Business Reporting, Business Intelligence and Dashboards

As I write this I am really wondering whether business intelligence and dashboards really go along with small business reporting. Now, I am not particularly analytical - nor am I a fan of statistics in general. However, when it comes to looking at business data I find myself constantly looking to create relationships to and amidst the data I’m looking at. For example, I might look at a report of production from a particular type of machine which shows high dollars shipped. Then I might wonder — well — great that we shipped so much - but how much profit was produced? How does that compare to last month? Last Year? etc. One question leads to another.

This scenario is perfect for the creation of a “dashboard” presentation. However, very much like the “business intelligence” applications that are available, creating the dashboard can be cost prohibitive. What a shame!

In my opinion the well run small business, be they multi-location or single-location, has perhaps more to gain from such information availability and presentation than does the larger company. There is more at stake for the smaller company.

I find myself constantly on the lookout for reasonably priced software (under $1000 - preferably in the $500-600 range) which can be used to create such a reporting application. For the small businesses that I deal with, spending $25,000 or so for a BI/Dashboard application just doesn’t make it. What I have found so far as a tool to use to create the application I’d like to provide is very expensive, cumbersome to use, and requires extensive programming beyond my particular skill set.

Where’s my reasonably priced tool out there? I’ll be searching, but if you have pointers please respond to this blog and help all of us out.

How to Measure Application Value - Part 1

When it comes to applications and the buy, build or ignore decision, one of the first considerations must be to find an answer to the question of what value the application is expected to bring forth.  That sounds simple enough, but how exactly does one measure the multiple values which any given application may be expected to provide.  On top of that, many applications once implemented can produce results which were totally unexpected.   Then of course there is always the challenge of putting A monetary value to the benefits.  All of these present challenges for both the developer organization and end customer.  So - where does one begin.

 I certainly don’t pretend to have the “answer”.  In fact, I believe, there really is no one answer for any organization, and the answers and methods used to evaluate “value” will vary from project to project.  My experience would show that sometimes the applications that prove of greatest value weren’t on anybodys radar, but were championed by someone within the organization with enough “clout” to say simply “do it!”

To set the record straight, I’m not saying here to “build it and they will come”, but I am saying that with proper consciousness to the business processes it is possible to hit a home run with an application that if analyzed early on with a “cost / benefit” analysis would fail miserably.  In following posts I intend to bring forth some of the perhaps “odd” methods I’ve been familiar with.

In the mean time, If you have anything you think should be addressed about application value — please post.

Small Business and Business Intelligence

Business Intelligence — I have heard it referred to as an oxy-moron, but I think I’ll not go there.  Reading through the technical press one needs not look very far before coming upon writings about BI — implementation issues, how to’s, pitfalls and about BI project ROI.  There is much ado about BI - but what about BI for the small business?  Does it fit, and if so how?   Continued »

Establishing Application Requirements

Establishing Application Requirements often seems to me to be a “which came first, the chicken or the egg?” scenario.  Just where does one start when looking at a new application?  What IS the “best” place to start?  As an application developer, whether for a small business or a departmental application for a larger corporation, we are often asked to develop something from nothing.  In my experience, what we are given to start with (if anything) is at best vague.  Continued »