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
    Flat editorial illustration: The article is about joining public web signals with internal business metrics so BI teams can inter
    Alternative Data in BI: Bringing Public Web Data Into Your Dashboards
    23 Min Read
    Flat editorial illustration: The article is about automating the collection, preparation, and delivery of marketing data across p
    From Data to Dashboards: 5 Marketing Reporting Automation Software Picks
    12 Min Read
    Flat editorial illustration: The article contrasts passive follower totals with a behavioral path from attention and trust to cli
    Creator Analytics Beyond Follower Count: Seven Metrics That Measure Audience Behavior
    11 Min Read
    Flat editorial illustration: The article connects AI and marketing analytics with managerial judgment grounded in consumer behavi
    How an Online MBA in Marketing Connects AI and Data Analytics
    11 Min Read
    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
  • Big Data
  • BI
  • Exclusive
  • IT
  • Marketing
  • Software
Search
© 2008-25 SmartData Collective. All Rights Reserved.
Reading: It Doesn’t Work Like That: BI Development Myths
Share
Notification
Font ResizerAa
SmartData CollectiveSmartData Collective
Font ResizerAa
Search
  • About
  • Help
  • Privacy
Follow US
© 2008-23 SmartData Collective. All Rights Reserved.
SmartData Collective > Business Intelligence > It Doesn’t Work Like That: BI Development Myths
Business Intelligence

It Doesn’t Work Like That: BI Development Myths

JillDyche
JillDyche
7 Min Read
It Doesn’t Work Like That: BI Development Myths
Illustration generated with FLUX.2 [klein 4B] via Cloudflare Workers AI.
SHARE

Unattended Baggage photo by ToastyKen (via Flickr)

When I was a little kid I would travel by air to visit my grandparents. In those days, PSA was the popular airline, flight attendants were called “stewardesses,” and we all romanticized air travel. When I grew up, I wanted to be a stewardess so I could wear go-go boots to work every day. And I was convinced that the luggage conveyors were part of a vast, subterranean network of moving beltways that transported my luggage as I flew to my destination, where it would rise from the earth and reunite with me on the other side.

“It doesn’t work like that,” said my father.

More Read

How to Integrate Finance and Operations by Leveraging Cloud Storage
How to Integrate Finance and Operations by Leveraging Cloud Storage
Unseen Barriers: Identifying Bottlenecks In B2B Sales
Billboards, Brand Awareness and Big Data: What Comedy Central and Gallery Furniture Have in Common
Using Link Analysis to Plan the Healthcare System
Are Your Systems Just Interfaces to a Data Structure?

I hadn’t learned the word “buzzkill” yet, but if I had, I would have used it often with my father. And sometimes my clients should use it with me. This is because we often find managers in both IT and the business who have misinterpreted rules or learned fraught practices for BI development, formulating ineffective processes based on a set of mistaken assumptions or extrapolations. And they’re crestfallen when things don’t work out as planned.

Take the concept of the “single version of the truth.” When the phrase is mentioned, many imagine a huge, centralized database with single, enterprise-sanctioned data definitions that have been blessed by everyone via widespread consensus and executive sign-off. The database rests in the middle of a complex set of business applications, which consume its pristine and static data forevermore.

It doesn’t work like that. In reality, BI users need to see the data differently depending on where they work, what they do, how they interpret and use it. A product hierarchy in the Finance organization may be defined differently than a product hierarchy in Marketing. The company may be able to define a term at the enterprise level but that doesn’t mean there’s a single, sanctioned definition for each data element. When it comes to data, context matters. This means that as that data changes along with the business, data dimensions and definitions can likewise change, rendering the data warehouse less of a centralized behemoth, and more of a dynamic platform—or set of platforms—for the provisioning and processing of dynamic data. (See Evan Levy’s TDWI article, “SVT No More” and Peter J. Thomas’ blog post on the topic for some more myth-busting.)

Another example is business requirements gathering. Many people think it’s a matter of interviewing a few subject matter experts, poring over existing reports, and perhaps having a facilitated workshop (formerly known as a JAD session) to collect and document user input.

It doesn’t work like that. Gathering requirements for BI has changed. It’s more structured and time-boxed, it’s increasingly driven by subject matter experts on the business side, and delineating business, data, and functional requirements is a best practice. Business requirements gathering has also become more automated as new tools provide persistent documentation and definitions that can be used to inform and refine subsequent development efforts. When done correctly, business requirements gathering not only ensures that BI conforms to business needs, it can drive a rigorous development pipeline.

Many managers and executives, new to BI but already sold on its strategic and operational promise, believe that if they start with a good plan success is in the bag. They’ll retain a consulting firm to build a BI roadmap and make some organizational suggestions to ensure that BI-specific functions exist. Then they’ll scout the organization for “who’s available,” to put on the BI project, with little or no regard for previous BI experience. (We call this “warm body syndrome.”)

You saw this one coming: it doesn’t work like that. The most successful BI efforts are ones in which at least a few key delivery personnel are seasoned, having done the work on past projects, and are able to mentor those who haven’t. Even a detailed roadmap reflecting a BI-centric methodology and prioritizing specific tasks won’t guarantee success if the skills and experience are missing.

The best BI development projects involve rigorous processes, experienced staff, an understanding of the development pipeline, and adherence to guiding principles for success. But too many BI teams rely on hope and imagination to get the job done. It doesn’t work like that.

Buzzkill.

photo by ToastyKen via Flickr

Link to original post

Share This Article
Facebook Pinterest LinkedIn
Share

Follow us on Facebook

Latest News

Flat editorial illustration: The article is about joining public web signals with internal business metrics so BI teams can inter
Alternative Data in BI: Bringing Public Web Data Into Your Dashboards
Big Data Business Intelligence Exclusive Web Analytics
Flat editorial illustration: A SaaS-editorial scene showing product usage, support patterns, and renewal feedback informing a fle
Using Product Usage Analytics and Support Data to Build a B2B Product Roadmap
Business Intelligence Infographic
From Hiring To Payroll: Managing HR Data Across Business Systems -- AI-generated illustration
From Hiring To Payroll: Managing HR Data Across Business Systems
Big Data Business Intelligence Infographic
Flat editorial illustration: The article is about automating the collection, preparation, and delivery of marketing data across p
From Data to Dashboards: 5 Marketing Reporting Automation Software Picks
Analytics Business Intelligence Exclusive Marketing

Stay Connected

1.2KFollowersLike
33.7KFollowersFollow
222FollowersPin

You Might also Like

Business Analytics Error: Learn from Uber’s Mistake During the Sydney Terror Attack
AnalyticsBest PracticesBusiness IntelligenceBusiness RulesCulture/LeadershipData MiningDecision ManagementMobilityPredictive AnalyticsRisk Management

Business Analytics Error: Learn from Uber’s Mistake During the Sydney Terror Attack

2 Min Read
Momentum for Enterprise Mobile Apps - Workday, Salesforce.com and Box.net
AnalyticsBusiness IntelligenceCollaborative Data

Momentum for Enterprise Mobile Apps – Workday, Salesforce.com and Box.net

6 Min Read
Bring Your Own Software
Best PracticesBusiness RulesCloud ComputingCollaborative DataCulture/LeadershipData ManagementInside CompaniesITLocationMobilityPolicy and GovernanceSecuritySoftware

Bring Your Own Software

4 Min Read
We’re Not Artists: The Craft of Influencing Decision Makers
Business IntelligenceData MiningExclusiveInside CompaniesMarketingPredictive Analytics

We’re Not Artists: The Craft of Influencing Decision Makers

6 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
Chatbots and SEO: How Can Chatbots Improve Your SEO Ranking?
Chatbots and SEO: How Can Chatbots Improve Your SEO Ranking?
Artificial Intelligence Chatbots Exclusive

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?