Maybe you built a series of normalized tables ... elegantly designed in a way that would make any IT professional proud. Maybe you hooked up Business Objects or MicroStrategy to the database, believing that you could answer any question you could think of.
Maybe you integrated your web analytics tool with your centralized customer data warehouse, expecting lightning bolts to appear from the sky about the casual visitor who browsed eight important landing pages before buying something in the store.
Or maybe you outsourced your database to a quality vendor who specializes in said activity.
I'm guessing that you're still dissatisfied with what you have.
You've probably learned the following equations:
- People > Database Design
- Database Design > Software
Database design means more than software. You need a series of summarized tables for campaign management. Don't ever let your software vendor or IT leader tell you not to store detail-level data (one row per item purchased, one row per page viewed). Your data expert needs the detail-level data to answer all the questions that cannot be answered by summarized fields.
Once those two aspects of the equation are solved, get good software.
Effective use of a database requires us to realize that people are more important than database design, and that database design is more important that software. This spring, many of you are communicating to me that your organizations view this the other way around ... you are outsourcing your analytical staff to India, you are outsourcing control of your databases, and you are relying on simple BI tools to query against summarized fields that don't adequately answer questions.
Let's turn this trend around!!