We use cookies, including third-party cookies from Google to serve personalized ads through AdSense, to operate this site and understand how it is used. By continuing to browse, you accept this use. See our Privacy Policy and Terms of Use for details, including how to opt out of personalized advertising.
Accept
SmartData CollectiveSmartData Collective
  • Analytics
    AnalyticsShow More
    What Kind of Problem-Solving Distinguishes Data Analysts From Software Engineers -- AI-generated illustration
    What Kind of Problem-Solving Distinguishes Data Analysts From Software Engineers
    7 Min Read
    chatgpt image jul 21, 2026, 04 34 30 pm
    4 Core Benefits of Predictive Maintenance after Vibration Analysis
    10 Min Read
    How Does Data Mining Boost Customer Satisfaction in Logistics? Harnessing Analytics for Results -- AI-generated illustration
    How Does Data Mining Boost Customer Satisfaction in Logistics? Harnessing Analytics for Results
    11 Min Read
    chatgpt image jul 13, 2026, 04 23 45 pm
    How Data Analytics Helps Companies Improve User Engagement
    19 Min Read
    chatgpt image jul 13, 2026, 03 59 46 pm
    How Data Analytics Improves Multi-Location Search Strategies
    10 Min Read
  • Big Data
  • BI
  • Exclusive
  • IT
  • Marketing
  • Software
Search
© 2008-25 SmartData Collective. All Rights Reserved.
Reading: Data Warehouse Design
Share
Notification
Font ResizerAa
SmartData CollectiveSmartData Collective
Font ResizerAa
Search
  • About
  • Help
  • Privacy
Follow US
© 2008-23 SmartData Collective. All Rights Reserved.
SmartData Collective > Big Data > Data Warehousing > Data Warehouse Design
Data Warehousing

Data Warehouse Design

Editor SDC
Editor SDC
6 Min Read
Data Warehouse Design
Illustration generated with qwen-image-Q4_K_M (local ComfyUI) + quality 20-step CFG 4.
SHARE
One of the main problems with Data Warehouses is that they are designed to answer any question. The problem is that they usually fail to answer the one someone is asking. DWs are usually good for referential information – meaning I can answer questions like “How many customers do we have that have spent over $100,000?” or “Which customers bought the blue widget?”

There are a number of points of failure that hamper DW projects:

  • They are usually complex and very costly
  • The business changes (regions, product lines, sales hierarchies, etc) in the middle of the process
  • The end use is not well defined
  • Lack of analytical skill and knowledge of data structure in the business users to get the right data
  • The end result is too complex for the users to understand where to go to get the right information
  • No one tells the organization “thou shalt” use the data warehouse – so people get data from all different sources making a common version of the truth difficult to get to
  • There are often no rules of engagement for how to use the environment, or data in general

If organizations only use 6-10% of the data they collect, how do you design the DW for greater adoption?

For starters, understand the common business questions and the potential levers that can be pulled. For example, one of the areas that always surprises me is the lack of information around the success of marketing campaigns. Marketing campaigns and price are really the only levers we can pull in the short term to increase revenues. What we often fall back to is the sales whip – where we put more pressure on the sales team to perform. This is a strategy of hope (which is not a recognized as a successful strategy practice). We apply the pressure without providing much in the terms of support.

Instead, let’s say we are ending the 3rd quarter and our numbers are a little behind and the pipeline is not as strong as we would like. We know we have some time, but the programs have to be very tactical to find low hanging fruit. Instead of reviewing the potential marketing programs or trying something new, we cross our fingers and yell at the sales team. We could cull the DW to find large groups of customers who had not bought specific groups of products and offer incentives for them to buy. We could identify the groups/verticals of customers with the shortest sales cycle and build a promotion and program for them as well.

Yet why do we not do this… we typically lack the information in a format we can use in a timely manner.

So if we design the data warehouse (or perhaps data marts) around specific business levers we stand a better chance of answering the one question we need. We just might trigger some very interesting questions about our business.

Come visit the blog (http://purestone.wordpress.com) for more information.

Posted in Analytics, Analytics & Business Intelligence, Customer Value, Initiative Management, Operational Performance Management, Process Improvement Tagged: Analytics, Business Questions, Data Mart, Data Warehouse, Marketing Campaigns, Marketing Performance, Report Design

Share This Article
Facebook Pinterest LinkedIn
Share

Follow us on Facebook

Latest News

Flat editorial illustration: The article describes an AI safety incident where an agent bypassed sandbox controls by exploiting D
OpenAI Pauses Advanced AI Work After Agent Bypasses Sandbox Controls
Artificial Intelligence News Security
Flat editorial illustration: The article explains that training robots for physical interaction requires three distinct data cate
Physical AI: What Data Do You Need to Train a Robot?
Artificial Intelligence Exclusive Robotics
What Kind of Problem-Solving Distinguishes Data Analysts From Software Engineers -- AI-generated illustration
What Kind of Problem-Solving Distinguishes Data Analysts From Software Engineers
Analytics Big Data Exclusive Software
Flat editorial illustration: The article examines AI agents that escalate from legitimate data retrieval to attempted intrusions
OpenAI’s Government Website Incidents Raise a Hard Question for AI Agents: When Should They Stop?
Artificial Intelligence News Security

Stay Connected

1.2KFollowersLike
33.7KFollowersFollow
222FollowersPin

You Might also Like

NoSQL Vs. RDBMS for Interactive Analytics: Leveraging the Right and Left Brain of Data
AnalyticsBig DataBusiness IntelligenceCloud ComputingData ManagementData MiningData WarehousingExclusiveHadoopPredictive AnalyticsR Programming LanguageSQLUnstructured DataWeb Analytics

NoSQL Vs. RDBMS for Interactive Analytics: Leveraging the Right and Left Brain of Data

9 Min Read
Lost Weekend: Troubleshooting a MySQL Installation
Data Warehousing

Lost Weekend: Troubleshooting a MySQL Installation

5 Min Read
Three Ways HR Analytics Can Boost the Bottom Line
AnalyticsBusiness RulesCulture/LeadershipData WarehousingPolicy and Governance

Three Ways HR Analytics Can Boost the Bottom Line

5 Min Read
How Data Became Big
Data MiningData QualityData Warehousing

How Data Became Big

21 Min Read

SmartData Collective is one of the largest & trusted community covering technical content about Big Data, BI, Cloud, Analytics, Artificial Intelligence, IoT & more.

5 Great Tips for Using Data Analytics for Website UX
5 Great Tips for Using Data Analytics for Website UX
Big Data
From Bolts to Bots: How AI Is Fortifying the Automotive Industry
From Bolts to Bots: How AI Is Fortifying the Automotive Industry
Artificial Intelligence

Quick Link

  • About
  • Contact
  • Privacy
Follow US
© 2008-26 SmartData Collective. All Rights Reserved.
Welcome Back!

Sign in to your account

Username or Email Address
Password

Lost your password?