Analytics truth serum

The Mayor suggested we blog about the much ballyhooed “single version of the truth.” To be clear, this is not a blog on theology. So if you were getting nervous…it’s okay. We are talking about business intelligence and analytics here.
Once again we will channel Wikipedia for a semi-formal definition of the the Single Version of the Truth:
Single Version of the Truth: In computerized business management, svot, or Single Version of the Truth, is a technical concept describing the data warehousing ideal of having either a single centralised database, or at least a distributed synchronised database, which stores all of an organisation’s data in a consistent and non-redundant form.
Swap out the “s” for “z” on some of those words if you are American and hopelessly confused. Apparently the author was taught British English.
So much like many of my college textbooks, the formal definition is abstract and semi-useless. So let’s talk about some examples that dummies like myself can understand.
One of the first steps that must be taken is to create definitions that are the same across the enterprise.
For example, if we are looking to answer the question “What are the sales for the past week?”; then we must standardize the how we derive the sales numbers.
Various departments, such as finance and operations, might view the calculation method from different viewpoints. For example, Operations might include shipping and handling in their sales calculation, Finance might prefer inclusion of the taxes collected in their sales calculation, and Marketing most likely has a different definition of when the calculation should start and end.
More variables on that simple question include: What is defined as a sale? Is it considered a sale when it leaves the fulfillment center? When the customer orders it? When the customers pays for it? Does it include tax, which tax? Is the tax different from state to state…
So what sounds simple on the surface is not. Sort of like marriage. .
Getting those definitions together will not be a small task in a large organization. Just that process alone can take weeks or even months depending on how “controversial” those definitions may seem. It may turn out that your sales organization wants the numbers to look as big as possible and your operations team disagrees. Good luck.
Once you’ve addressed definitions, then you get to ponder the accuracy of the data itself. Manual data entry, missing records, and allocations based on the time dimension. This is where you really earn your salary.
After that, then you get to tackle interesting questions like “how many unique customers do you really have”? Is clint@analytixondemand.com the same as clint.brauer@analytixondemand.com? If there is yet another “Clint Brauer” at yet another shipping address….is that the same Clint?
All something to ponder.
Then there are all the technical implications of wanting to have “one version of the truth.” Do you have multiple databases? If so, how and when do they synch and what are the rules for updates to various fields? How do you validate and continue to monitor your data for accuracy purposes?
As the Mayor called out to me, this is yet another case where it’s more about the journey and less about the destination. Chances are you will constantly be making adjustments to your business rules and your technical systems.
As always, the key is to communicate and make sure everyone is drinking the same truth serum. As long as everyone understands the definitions and the limitations at any given point, then your organization can go about making constructive decisions based on quantitative data instead of pure speculation.



Now that the total ownership costs of business intelligence systems are being driven down by SaaS, we’ll likely see the business intelligence market grow like a California cash crop over the next years; regardless of economic conditions.


So it’s not quite like Spy vs. Spy. In fact, to some extent it’s a complimentary relationship.