Rapid Battle Cards 29–42
- Populate DW vs implement BI portfolio — get integrated data into analytical stores vs deliver consumer-appropriate analytical capabilities.
- Operational reporting vs business query/reporting — current/tactical workflow/status vs analytical/ad hoc use of integrated warehouse/mart data.
- Tactical BI vs Strategic BI — shorter-horizon operational/management decision vs long-term goals, trends, planning and performance.
- Self-service BI vs unmanaged analysis — business-created analysis inside governed data/semantic/security/support guardrails vs uncontrolled local data/definitions/access.
- OLAP vs standard report — interactive multidimensional exploration vs predefined report output.
- Data dictionary vs lineage — meaning/structure/context vs origin/movement/transformation path.
- Lineage vs impact analysis — where data came/went vs what would be affected by a proposed change.
- Release vs iteration — coordinated deployable business-facing package vs development cycle/increment.
- Pilot/sandbox vs production — exploratory/limited validation vs supported live environment with readiness controls.
- Usage metric vs license count — actual connections/query activity vs entitlement/capacity.
- Subject coverage vs query response — breadth of analytical business/data scope vs service speed/performance.
- SLA vs customer satisfaction — formal expected service behavior vs user perception/trust/usefulness.
- Reporting strategy vs BI tool inventory — governed access/user-fit/report behavior/distribution/timing/support vs list of products.
- Governance vs execution blockage — risk-based decision rights/controls vs arbitrary obstruction.
Fast drill
- Trace a report value to ERP fields → lineage.
- Ask what breaks if Product changes → impact analysis.
- 10,000 licenses but 400 monthly users → usage/adoption issue.
- Marketing absent from Product analytics → subject-area coverage.
- Four-hour refresh takes six → load/performance/SLA.
Source: pp. 377–393.