library / lib47ae9d954ec08151
Business Intelligence Guidebook: From Data Integration to Analytics
Rick Sherman · 2014
In a sentence
A comprehensive, vendor-agnostic practitioner's guide to building a sustainable business intelligence environment from data integration through advanced analytics, with emphasis that BI success depends as much on people, process, and politics as on technology.
Business Intelligence Guidebook fills the gap between high-level BI concept books and vendor tool manuals by walking the reader through the entire lifecycle of creating a world-class BI environment: justifying the investment, defining requirements, building architectural blueprints (information, data, technology, and product), designing data models (entity-relationship and dimensional), engineering data integration processes, developing BI applications and advanced analytics, taming data shadow systems, and managing the organizational dimensions of people, process, politics, project management, and centers of excellence. Drawing on decades of consulting and implementation experience, Rick Sherman argues that BI is not a one-and-done project but an evolving program that must be built incrementally and iteratively, grounded in the recognition that raw data must be transformed into clean, consistent, conformed, current, and comprehensive information before it delivers business value. The book is deliberately product-neutral so its concepts endure beyond vendor mergers and hype cycles, and it repeatedly stresses that the hardest part of BI is not technology but the human and organizational factors that determine whether solutions are actually adopted and trusted.
The four lenses
- Science
- Statistics
- Systems
- Strategy
The model
A causal framework expressing how design levers (architectural discipline, data integration rigor, dimensional modeling, tool-based development, requirements/expectation management, training, and organizational governance) drive psychological and behavioral states (trust in information, adoption, business-IT collaboration) and contextual conditions (information quality—the five Cs—and silo proliferation), which in turn drive outcomes (business value/ROI, project success, productivity). The model is inferred from the book's repeated thesis that information quality and people/process/politics, not technology alone, determine BI outcomes.
Architectural Disciplinedesign lever
The degree to which the enterprise designs and follows an overarching four-layer architectural framework (information, data, technology, product) before selecting products, avoiding the accidental architecture and silos.
Data Integration Rigordesign lever
The extent to which data integration is engineered holistically with standards, reusable components, tools, documentation, and auditability rather than hand-coded extracts, representing the largest share of BI work.
Dimensional Modeling Qualitydesign lever
The soundness of data design using dimensional and hybrid dimensional-normalized models, conformed dimensions, surrogate keys, slowly changing dimensions, and appropriate schemas to support analytics.
Tool-Based Development Adoptiondesign lever
The degree to which BI, data integration, and database tools (selected as best fit for needs, skills, and budget) are used rather than ad hoc manual coding, enabling productivity, governance, and reuse.
Requirements and Expectation Managementdesign lever
The thoroughness of defining business, data, quality, functional, and technical requirements and the active setting and managing of realistic stakeholder expectations through justification, roadmaps, and communication.
Training Investmentdesign lever
The investment in vendor-agnostic foundational BI training, tool-specific training, and use-case-based training for both business and IT people.
Organizational Governance and Sponsorshipcontextual condition
The presence of executive sponsorship, data governance, project/program management discipline, and centers of excellence that manage people, process, and politics across the enterprise.
Information Quality (Five Cs)contextual condition
The degree to which delivered information is clean, consistent, conformed, current, and comprehensive, representing the central contextual condition that determines whether data has business value for analysis and decision-making.
Data and Application Silo Proliferationcontextual condition
The extent to which disconnected data, application, and reporting silos (including data shadow systems and spreadmarts) accumulate across the enterprise, producing inconsistent and incomplete information.
Trust in Informationpsychological state
The psychological state of business people having confidence in the data and analytics they consume, free from debate over whose numbers are correct.
BI Adoption and Usagebehavioral pattern
The behavioral pattern of business people actively using BI applications in their jobs rather than reverting to spreadsheets or data shadow systems.
Business-IT Collaborationbehavioral pattern
The behavioral pattern of business and IT groups working as partners with open communication, shared accountability, and active business participation throughout the BI lifecycle.
Business Value and ROIoutcome metric
The outcome of BI delivering tangible business benefits—revenue optimization, cost reduction, risk reduction, improved decision-making—producing return on investment.
BI Project Successoutcome metric
The outcome of BI projects being delivered on time, within budget, with quality, and—most importantly—meeting stakeholder expectations.
Business and IT Productivityoutcome metric
The outcome of business people shifting time from data gathering and reconciliation to analysis, and IT shifting from maintenance to expanding BI value.
How they connect
- architectural discipline − influences silo proliferation
- data integration rigor → predicts information quality five cs
- dimensional modeling quality → influences information quality five cs
- tool based development → influences data integration rigor
- information quality five cs → predicts trust in information
- silo proliferation − influences information quality five cs
- trust in information → predicts bi adoption
- requirements and expectation management → predicts project success
- business it collaboration → influences requirements and expectation management
- training investment → influences bi adoption
- organizational governance − influences silo proliferation
- organizational governance → influences business it collaboration
- bi adoption → predicts business value roi
- project success → predicts business value roi
- information quality five cs → influences productivity
- silo proliferation − influences productivity
- data integration rigor − influences silo proliferation
A candidate measure
Business Intelligence Guidebook: From Data Integration to Analytics — derived measurement candidates
Architectural Discipline
Architecture maturity rating; Count of unplanned silos; Percentage of projects following the framework
self-report suitability: medium
Data Integration Rigor
Percent tool-based vs. hand-coded processes; Number of reusable components; Audit/lineage coverage
self-report suitability: medium
Dimensional Modeling Quality
Expert review score against modeling best-practice checklist; Presence of date/time dimensions; Count of anti-patterns
self-report suitability: low
Tool-Based Development Adoption
Percent of development built with tools; Presence of best-fit selection process; Documentation coverage
self-report suitability: medium
Requirements and Expectation Management
Requirements completeness checklist score; Stakeholder expectation-alignment rating; Scope change frequency and handling
self-report suitability: high
Training Investment
Training hours per person; Coverage across audiences; Pre/post competence gain
self-report suitability: high
Organizational Governance and Sponsorship
Governance structure presence index; Sponsorship/resource commitment level; Stakeholder-rated governance effectiveness
self-report suitability: high
Information Quality (Five Cs)
Per-C data quality metrics; Reconciliation/number-dispute incidence; User-reported confidence in data
self-report suitability: medium
Data and Application Silo Proliferation
Inventory count of shadow systems and silos; Number of redundant BI tools; Reconciliation effort hours
self-report suitability: medium
Trust in Information
Self-reported trust scale; Frequency of number disputes; Decision reliance rate
self-report suitability: high
BI Adoption and Usage
BI usage logs (BI on BI); Active user counts and breadth; Shadow system creation rate
self-report suitability: medium
Business-IT Collaboration
Relationship/communication-quality survey; Business participation rate in requirements/testing; Shared-accountability mechanism presence
self-report suitability: high
Business Value and ROI
ROI ratio; Cost reduction and revenue metrics; Cycle-time reductions
self-report suitability: low
BI Project Success
Schedule/budget variance; Expectation-fulfillment satisfaction score; Defect/rework rate
self-report suitability: high
Business and IT Productivity
Time-allocation percentages; Reconciliation effort reduction; IT maintenance-to-value ratio
self-report suitability: medium
The story
The reader A business or IT professional tasked with creating, renovating, or sustaining a business intelligence environment who wants to deliver trustworthy, actionable information that the business will actually use.
External problem
Their organization is drowning in inconsistent, siloed data and struggling to turn it into reliable information for decision-making; BI projects are late, over budget, and fail to meet expectations.
Internal problem
They feel overwhelmed by hype, unsure what questions to ask, and anxious about being blamed when a high-profile BI effort underdelivers.
Philosophical problem
It's just plain wrong that organizations invest heavily in data yet make decisions on incomplete, inconsistent, or untrusted information when there is a proven path to doing it right.
The plan
- Justify the BI effort and set realistic expectations with a business and technical case.
- Define requirements—business, data, quality, functional, and technical—thoroughly to avoid late surprises.
- Build an architectural framework spanning information, data, technology, and product layers.
- Design data models (ER and dimensional/hybrid) and engineer robust, tool-based data integration.
- Develop BI applications and advanced analytics matched to personas and business needs.
- Tame data shadow systems and institutionalize people, process, governance, and centers of excellence.
Success
- The reader delivers clean, consistent, conformed, current, and comprehensive information that business people trust and use.
- BI becomes pervasive and adopted, expanding incrementally with strong business ROI and a sustainable, world-class environment.
- Business and IT collaborate as partners, data shadow systems shrink, and the enterprise becomes truly data-driven.
At stake
- BI projects are late, over budget, and labeled failures due to unmet expectations.
- Data silos and data shadow systems proliferate, producing inconsistent numbers, wasted reconciliation time, and decisions based on faulty data.
- Investments deliver little ROI as the organization repeats the Twilight Zone trap of blaming and replacing tools.