Biggest business intelligence (BI) problem: overloading data

You talk and blog a lot about BI best practices and how to adopt them. What’s a BI problem or worst practice you’ve seen consistently that doesn’t seem to go away?

    Requires Free Membership to View

    When you register, you'll receive targeted emails designed to keep you informed of the latest BI, analytics, corporate performance management (CPM) trends and more.

    Hannah Smalltree, Editorial Director

    By submitting your registration information to SearchBusinessAnalytics.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchBusinessAnalytics.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

Overloading data – hands down. I still can’t believe how much time companies spend on extract, transform and load (ETL) processes at the expense of deploying user functionality. After all, the data model is done – isn’t it time to populate tables? This is when we have the “we love you, but we have to kill you” conversation with our clients.

It’s so much easier just to load all of the data. Except for two problems. One, you’ll never load all of the data as long as new requirements keep cropping up. (And I hate to break the news, but if new requirements don’t keep cropping up, you’ve got bigger issues.) And two, your business users are thinking, “They’re still loading data? What about my scorecard/portal/dashboard/reports? They must not understand my business.”

Fair? Probably not. But perception is reality, and sometimes reality bites. Chunk up slices of functionality and load the data proportionally. Of course there’s going to be some rework! But the price of data loading in a vacuum is disaffected constituents. And that reality bites even harder.

 

This was first published in November 2010

Join the conversationComment

Share
Comments

    Results

    Contribute to the conversation

    All fields are required. Comments will appear at the bottom of the article.