A dashboard that grows without improving decision quality is a symptom of analytics without strategy. Each area requests its report, the data team delivers, the dashboard accumulates in the BI portal and nobody marks it as the authoritative version. Platform investment grows. Impact on decisions stays the same. The problem is the absence of a semantic layer that defines the single authoritative version of each metric and the absence of a link between that metric and the business decision it should drive.
Subcapability 03 of 05 · Data & Analytics
Analytics & Business Intelligence
Semantic layer, governed self-service and KPIs wired to the result that replace expensive intuition with evidence-based decisions and eliminate the debate about which number is right in every executive meeting.
What is at stake
The company has dashboards. It has a BI platform. The problem is that the executive meeting still starts with 20 minutes debating which number is correct. When the debate is about the origin of the data, the decision that should happen in the meeting does not happen.
What it is, in practice
How we work
Semantic layer as single metric source
We implement a semantic layer that defines each business metric once, with documented and versioned calculation logic. Gross revenue means the same thing in the CFO dashboard and the sales team report. The debate about the origin of the number ends when the definition is shared.
Governed self-service BI
We structure self-service access for business analysts to explore within a defined quality perimeter, without depending on the data team for every new view. Governance defines what each profile can access, not blocks exploration.
Analytics connected to business question
We start from the question that needs to be answered to make the right decision, not from available data. Every dashboard has an explicit business question, a defined audience and a success criterion that measures whether the decision was supported.
Decision intelligence on recurring decisions
We instrument high-frequency recurring decisions with models that suggest the action based on historical pattern. Inventory replenishment decisions, service prioritization and operational resource allocation are candidates for decision intelligence.
Adoption measured by impact, not access
We measure what actually matters: the percentage of recurring decisions that start having a reference to verifiable data. A dashboard nobody uses is not adoption. An executive meeting that replaces opinion with a number is adoption.
Measurable gains
What changes in the result when this subcapability matures.
Dashboard adoption rate (active users over eligible population)
A BI platform that answers the right question for the right audience has a measurable adoption rate. A dashboard that grows in number without growing in active users is a symptom of analytics without a usage strategy.
Time between executive analysis request and delivery of data-based answer
Governed self-service reduces dependence on the data team for every new question. A business analyst who accesses data autonomously answers in hours what previously waited days in the request queue.
Percentage of executive meetings with decisions supported by verifiable data
The indicator that separates analytics with impact from analytics without impact. Increasing this percentage is the ultimate goal of any investment in data and BI platform.
Cost of maintaining eliminated manual reports
Critical reports assembled manually every month have analyst cost, operational risk concentrated in one person and no scale. Automating and governing these reports frees capacity and eliminates the risk.
Frequently asked questions
What is a semantic layer and why does it eliminate number conflicts?
A semantic layer is the software layer that defines business metrics once, with explicit calculation logic, independently of the visualization tool. When gross revenue has one definition in the semantic layer, any dashboard consuming that definition shows the same number. The conflict between the CFO's number and the sales team's number comes from the absence of this layer: each tool calculates its own version of the metric.
Does self-service BI not open a risk of bad data in the hands of people who do not understand it?
The risk exists when self-service lacks governance. With a semantic layer that defines metrics centrally, profile-based access that limits what each user sees and alerts when a view crosses data in an unexpected way, the business analyst explores within a defined quality perimeter. Governed self-service democratizes access without sacrificing reliability.
How do you measure whether analytics is generating business impact?
Two complementary indicators measure real impact: adoption rate (active users over eligible population) and percentage of recurring decisions that start having documented data reference. The first measures whether data is being accessed. The second measures whether data is changing decision behavior. A BI platform with high adoption and a low percentage of data-supported decisions indicates analytics is not answering the right question.
What is the difference between BI, analytics and decision intelligence?
BI describes what happened. Analytics diagnoses why it happened. Decision intelligence prescribes what to do based on the identified pattern. The three are complementary and evolve in maturity. A company without reliable BI cannot use strategic analytics. A company without strategic analytics cannot implement decision intelligence with defensible results.
How to choose between Power BI, Looker and Tableau?
The choice follows existing technology context, team profile and required governance level. Power BI with Fabric integrates better with Microsoft 365 and Azure. Looker with BigQuery is the reference for semantic layer and metric governance. Tableau has the largest historical adoption and the broadest visualization ecosystem. The assessment evaluates which platform best serves the context before any license commitment.
Other subcapabilities in this capability
Data Architecture & Governance
Data Management Body of Knowledge and Data Mesh with federated governance that structure data as a formal asset with owner, traceable lineage and domain accountability that scales without a central bottleneck and enables AI in production.
Data Engineering & Pipelines
Apache stack with orchestration, observability and idempotency that eliminates the artisanal pipeline without monitoring and ensures no executive dashboard ever shows a wrong number with the appearance of a correct one.
Data Quality & Master Data
Six data quality dimensions and MDM Hub Architecture that eliminate the three versions of the same customer across systems and transform data from a source of debate into a verifiable base for every executive decision.
Data Products
DATSIS principles and Data Contracts that transform ownerless datasets into products with SLA, defined consumers and explicit accountability, eliminating the central bottleneck no backlog can absorb.
Want clarity on where to invest first?
A complete technology capability assessment with an evolution roadmap connected to financial result.