Cookies help us display personalized product recommendations and ensure you have great shopping experience.

By using this site, you agree to the Privacy Policy and Terms of Use.
Accept
SmartData CollectiveSmartData Collective
  • Analytics
    AnalyticsShow More
    data analytics and truck accident claims
    How Data Analytics Reduces Truck Accidents and Speeds Up Claims
    7 Min Read
    predictive analytics for interior designers
    Interior Designers Boost Profits with Predictive Analytics
    8 Min Read
    image fx (67)
    Improving LinkedIn Ad Strategies with Data Analytics
    9 Min Read
    big data and remote work
    Data Helps Speech-Language Pathologists Deliver Better Results
    6 Min Read
    data driven insights
    How Data-Driven Insights Are Addressing Gaps in Patient Communication and Equity
    8 Min Read
  • Big Data
  • BI
  • Exclusive
  • IT
  • Marketing
  • Software
Search
© 2008-25 SmartData Collective. All Rights Reserved.
Reading: People, Process and Politics – We All Hate Data Silos, So Why do They Happen?
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 > People, Process and Politics – We All Hate Data Silos, So Why do They Happen?
Data Warehousing

People, Process and Politics – We All Hate Data Silos, So Why do They Happen?

RickSherman
RickSherman
5 Min Read
SHARE

IStock_000006846616XSmall different teams Why are data silos so prevalent when we really ought to know better? We know that it’s risky to have inconsistent data. We strive for the “single version of the truth” along with our IT and high tech vendors.

So, with all this awareness, why does almost every company end up with data silos?

There are two causes that I’ve seen in my consulting work. First, companies typically organize BI and DW related projects on a tactical and project-by-project basis. This makes data silos very, very likely. Second, these tactical projects are designed without an overall information architecture blueprint. This absolutely, positively guarantees a silo. You “can’t get there from here” if you don’t know where you are trying to go.

There are several reasons why otherwise smart people create projects on a tactical basis without an overall architecture:

More Read

I Have a Query
Web 2.0 Data Scalability
What you need to be a Business Intelligence Consultant ??
What Skills Does an Oracle BI Developer Need in 2009?
Images from “Contact lenses with circuits, lights a…

Funding – Projects are funded by a group representing an organization or business process. These groups are focused mainly on their own information needs and delivering business value in the context of those needs. Building an enterprise-wide solution is not in their minds nor in their charter.

Confusion – Industry jargon creates the impression that . …

IStock_000006846616XSmall different teams Why are data silos so prevalent when we really ought to know better? We know that it’s risky to have inconsistent data. We strive for the “single version of the truth” along with our IT and high tech vendors.

So, with all this awareness, why does almost every company end up with data silos?

There are two causes that I’ve seen in my consulting work. First, companies typically organize BI and DW related projects on a tactical and project-by-project basis. This makes data silos very, very likely. Second, these tactical projects are designed without an overall information architecture blueprint. This absolutely, positively guarantees a silo. You “can’t get there from here” if you don’t know where you are trying to go.

There are several reasons why otherwise smart people create projects on a tactical basis without an overall architecture:

Funding – Projects are funded by a group representing an organization or business process. These groups are focused mainly on their own information needs and delivering business value in the context of those needs. Building an enterprise-wide solution is not in their minds nor in their charter.

Confusion – Industry jargon creates the impression that things are different, when they’re actually similar. There are many similarities between CRM (customer relationship management), SCM (supply chain management), budgeting and forecasting, performance management and balanced scorecards. Many people do not see that each has data, data integration and business intelligence that can be shared across projects.

Technology – People tend to treat different technologies as different projects and applications. ETL (extract, transform and load), SOA (service oriented architecture), EAI (enterprise application integration) and data virtualization are considered different and treated as separate entities rather than different methods to implement data integration.

Disconnects – Data warehousing and enterprise applications are treated as separate worlds. Even though the business person may need reporting from operational applications and the DW, different projects are created to implement reporting from each of these data sources. And often IT splits its ERP and DW people into separate groups, further perpetuating silos.

No Architecture  – Finally, without an information architectural blueprint how is anyone to know that these projects should be connected? If you split up building a house amongst various contractors and specialists such as electricians and plumbers without a blueprint and without these groups talking to each other it is unlikely the house gets built correctly. It’s the same with a DW or BI project. You need the blueprint (information architecture) – especially if the projects are set up tactically and on a project-by-project basis. This is called accidental architecture and it creates data silos.

Data silos result in poor quality data that is often inconsistent, wastes resources and time on overlapping and redundant projects, costs more money to build and maintain, and ultimately results in the business not getting information in a consistent, comprehensive and current manner. Data silos also encourage the creation of data shadow systems or spreadmarts, further exacerbating the problems.

How do we get out of this? Stay tuned for more posts in the People, Process and Politics series.


Link to original post

Share This Article
Facebook Pinterest LinkedIn
Share

Follow us on Facebook

Latest News

data analytics and truck accident claims
How Data Analytics Reduces Truck Accidents and Speeds Up Claims
Analytics Big Data Exclusive
predictive analytics for interior designers
Interior Designers Boost Profits with Predictive Analytics
Analytics Exclusive Predictive Analytics
big data and cybercrime
Stopping Lateral Movement in a Data-Heavy, Edge-First World
Big Data Exclusive
AI and data mining
What the Rise of AI Web Scrapers Means for Data Teams
Artificial Intelligence Big Data Exclusive

Stay Connected

1.2kFollowersLike
33.7kFollowersFollow
222FollowersPin

You Might also Like

How Data Became Big

21 Min Read

A new IBM national survey of 30,000 U.S. consumers calls…

1 Min Read

Reference Domains Part II: Modelling Classifications

6 Min Read

For the first time in history, more people live in cities than…

1 Min Read

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

ai chatbot
The Art of Conversation: Enhancing Chatbots with Advanced AI Prompts
Chatbots
giveaway chatbots
How To Get An Award Winning Giveaway Bot
Big Data Chatbots Exclusive

Quick Link

  • About
  • Contact
  • Privacy
Follow US
© 2008-25 SmartData Collective. All Rights Reserved.
Go to mobile version
Welcome Back!

Sign in to your account

Username or Email Address
Password

Lost your password?