Big Data Analytics

Chapter 10
Visualization, Communication and Decision Support

Bachelors Program in Business Analytics
Big Data Analytics   •   Bachelor

Visualization, Communication and Decision Support

Introduction

Big data analytics creates value only when analytical results influence decisions. A highly accurate model can fail organizationally if managers cannot interpret it, do not trust its assumptions, or cannot connect it to an operational action. Visualization, communication and decision support therefore form the bridge between data engineering, statistical analysis and managerial practice.

This chapter examines how analysts convert large and complex data into effective dashboards, visual narratives and decision-support systems. It distinguishes descriptive, predictive and prescriptive analytics; explains how to define metrics and key performance indicators (KPIs); shows how to communicate uncertainty; and considers ethical, technical and organizational risks.

Learning Objectives

By the end of this chapter, students should be able to:

  1. Distinguish data, measures, metrics, KPIs and analytical insights.
  2. Select visual encodings and dashboard structures appropriate to a decision task.
  3. Design visual narratives for descriptive, predictive and prescriptive findings.
  4. Calculate and interpret common business metrics.
  5. Communicate uncertainty, assumptions and model limitations responsibly.
  6. Translate analytical evidence into managerial choices and actions.
  7. Evaluate dashboards for usability, accessibility, governance and ethical quality.

From Data to Decision

A useful analytical communication chain is:

Data → Measure → Metric → Insight → Decision → Action → Outcome

Data are recorded observations, such as transactions or sensor readings. A measure is a quantified attribute, such as revenue or delivery time. A metric is a measure defined for a particular purpose, population and time period. A KPI is a strategically important metric linked to an objective, target and accountable owner. An insight is an interpretation that changes understanding or suggests action. A decision selects among alternatives, while an action implements that choice.

The chain is not automatically causal. A dashboard may show that sales and advertising expenditure increased together, but this association alone does not establish that advertising caused the sales increase. Analysts must distinguish description from explanation, prediction and intervention.

Four analytical questions

Analytical questionTypical outputManagerial use
What happened?Descriptive summary or trendMonitor performance
Why might it have happened?Diagnostic analysisInvestigate drivers
What is likely to happen?Forecast or probabilityPrepare resources
What should we do?Prescriptive recommendationChoose an action

Descriptive analytics summarizes historical or current data. Diagnostic analytics examines patterns, comparisons and possible drivers. Predictive analytics estimates future or unobserved outcomes. Prescriptive analytics evaluates actions, constraints and consequences. These categories overlap in practice, but each makes different claims and requires different evidence.

Metrics and KPI Architecture

A metric should have a precise definition. A robust metric specification includes:

  • name and business purpose;
  • numerator and denominator, if applicable;
  • population and inclusion rules;
  • time window and reporting frequency;
  • data source and refresh schedule;
  • unit of measurement;
  • target, threshold or benchmark;
  • owner and expected decision;
  • known limitations.

For example, “customer retention” is incomplete unless the organization specifies which customers are included, the starting cohort, the observation period and the treatment of cancellations or inactivity.

Common business formulas

Revenue from transactions can be represented as:

Revenue = ∑ᵢ Priceᵢ × Quantityᵢ

Here, i indexes transactions or products. Price and revenue use currency units, while quantity uses product units. The formula assumes that recorded prices and quantities are valid and that returns, discounts and taxes have been treated consistently.

A simple conversion rate is:

Conversion rate = Completed outcomes ÷ Eligible opportunities × 100%

The denominator must contain only eligible opportunities. For example, website conversion should not divide purchases by all page views unless that definition is explicitly intended.

Customer acquisition cost (CAC) is commonly defined as:

CAC = Attributable acquisition expenditure ÷ New customers acquired

The numerator and denominator must refer to the same period and attribution rule. CAC is not comparable across campaigns if one includes only media expenditure and another includes media, labor and technology costs.

Average order value (AOV) is:

AOV = Revenue ÷ Number of completed orders

A rate metric can hide volume. A region with a 10% conversion rate from 100 opportunities produces fewer conversions than a region with a 5% rate from 10,000 opportunities. Dashboards should therefore present rates alongside relevant counts.

Worked example: defining a KPI

A retailer records 24,000 eligible website sessions in April and 960 completed orders. April revenue is $72,000.

Conversion rate = 960 ÷ 24,000 × 100% = 4%.

AOV = $72,000 ÷ 960 = $75 per order.

These metrics answer different questions. Conversion rate concerns the proportion of opportunities that became orders; AOV concerns the value of each completed order. A manager should not conclude that the site is performing well from AOV alone, because a high AOV may coexist with a low conversion rate.

Leading and lagging indicators

Lagging indicators measure outcomes, such as profit, churn or completed deliveries. Leading indicators provide earlier signals, such as qualified leads, service backlog or product defects. A balanced KPI system combines both. Overemphasis on leading indicators can reward activity without results; overemphasis on lagging indicators can make intervention too late.

Targets should be challenging but credible. A target without a decision rule is merely a number. A useful KPI states what happens when performance is above, within or below the acceptable range.

Principles of Effective Visualization

Visualization uses visual position, length, size, color, shape and orientation to encode data. Encodings differ in perceptual accuracy. Position along a common scale is generally easier to compare than area, angle or color intensity. Consequently, a bar chart is often more effective than a pie chart for comparing many categories.

Match the chart to the analytical task

TaskSuitable visual formsImportant caution
Compare categoriesOrdered bar chart, dot plotUse a common baseline where possible
Show change over timeLine chart, slope chartAvoid implying continuity for unrelated periods
Show distributionHistogram, box plot, density plotExplain binning and outliers
Show relationshipScatter plot, hexbin plotCorrelation is not causation
Show compositionStacked bar, area chartAvoid too many segments
Show geographyChoropleth or symbol mapNormalize for population or exposure
Show processFlow diagram, funnelDefine each stage precisely
Show uncertaintyIntervals, bands, error barsState what the interval represents

A chart should have a clear title, labeled axes, units, source, time period and relevant definitions. Decorative effects such as three-dimensional bars, excessive gradients and unnecessary icons often reduce accuracy. Truncated axes can exaggerate differences, especially in bar charts; if a nonzero baseline is necessary, it should be clearly signaled and justified.

Color should encode a meaningful variable rather than serve as decoration. Sequential palettes suit ordered magnitude, diverging palettes suit deviation around a meaningful midpoint, and categorical palettes suit distinct groups. Red-green combinations create accessibility problems for many users; redundant encodings such as labels or patterns improve access.

Dashboard design

A dashboard is an interactive display that supports recurring monitoring or investigation. It is not simply a collection of charts. Its design should begin with the decision and user, not the available visualizations.

A practical dashboard structure has three levels:

  1. Overview: a small set of KPIs, status indicators and major trends.
  2. Diagnosis: breakdowns by product, region, customer segment or process stage.
  3. Action: alerts, forecasts, recommendations, responsible owners and next steps.

The overview should answer “What requires attention?” Drill-down views should answer “Where and why?” Action views should answer “What can be done, by whom and by when?”

Dashboard requirements should also specify latency. A real-time operational dashboard may require seconds or minutes, while a strategic performance dashboard may be refreshed daily or monthly. Faster refresh is not always better if it increases noise, cost or false alarms.

A dashboard should display data quality status, last refresh time and definitions. Filters must be visible and reversible. Interaction should not create hidden changes to denominators or comparisons. A user should be able to reproduce the displayed result from documented data and logic.

Visual Storytelling and Communication

Visual storytelling organizes evidence into a coherent argument. A strong narrative generally contains:

  1. Context: What decision or problem matters?
  2. Evidence: What pattern is visible?
  3. Interpretation: What explanations are plausible?
  4. Uncertainty: What is not known or may change?
  5. Recommendation: What action is supported?
  6. Follow-up: How will the result be evaluated?

The narrative should distinguish observation from interpretation. “Returns increased from 6% to 9%” is an observation. “A packaging defect may be contributing to the increase” is a hypothesis requiring investigation. “Replace the packaging immediately” is a recommendation whose cost, feasibility and expected effect must be evaluated.

Audience adaptation is essential. Executives usually need implications, trade-offs and exceptions. Operational staff need definitions, timing, thresholds and workflows. Technical stakeholders need data lineage, model performance and assumptions. The same analysis may therefore require a concise executive view and a detailed technical appendix.

Pre-attentive features—position, contrast, size and limited color emphasis—can direct attention. They should identify the decision-relevant exception, not manipulate the viewer. Annotation can explain a policy change, system outage or unusual event, preventing users from interpreting an operational break as a natural trend.

Communicating Uncertainty

Uncertainty is an attribute of knowledge, not a defect to hide. It may arise from sampling, measurement error, missing data, model assumptions, changing environments or ambiguity in the target definition.

For a sample mean, the standard error is commonly represented as:

SE(x̄) = s ÷ √n

Here, x̄ is the sample mean, s is the sample standard deviation and n is the sample size. This expression describes sampling variability under conditions where observations are reasonably independent and the standard deviation is estimated appropriately. It does not capture systematic measurement bias or model misspecification.

A confidence interval for a mean may be written as:

x̄ ± t* × SE(x̄)

Here, t is a critical value from the relevant t distribution, determined by the desired confidence level and degrees of freedom. The interval is appropriate under assumptions such as a suitable sampling design and, for small samples, an approximately normal sampling distribution. A 95% confidence interval is not correctly interpreted as a 95% probability that one fixed parameter lies in this particular interval; under repeated sampling, approximately 95% of intervals constructed by the method would contain the parameter if assumptions hold.

For forecasts, uncertainty can be communicated through prediction intervals, which include both uncertainty in the estimated mean forecast and variation of individual future outcomes. Prediction intervals are generally wider than confidence intervals for the mean. A forecast should also show the historical window, forecast horizon, model version and important scenario assumptions.

Probability statements must define the event and reference population. “The model predicts a 20% probability of default” is meaningful only when the population, time horizon, outcome definition and calibration context are specified. A probability is not a guarantee and should not be converted into certainty through color coding alone.

Sensitivity analysis tests how conclusions change when assumptions vary. Scenario analysis may compare, for example, baseline, optimistic and adverse demand conditions. These are not claims that the future must fit three categories; they are structured tools for examining robustness.

Decision Support: From Prediction to Action

Prediction estimates what may happen; decision support evaluates what should be done given objectives, constraints and consequences. A decision can be represented conceptually as:

Choice → Expected consequences → Costs and benefits → Constraints → Decision rule

Suppose an organization is considering an intervention with possible outcomes. Expected monetary value can be expressed as:

EMV(a) = ∑ⱼ P(outcomeⱼ | a) × Value(outcomeⱼ, a) − Cost(a)

Here, a is an action, j indexes possible outcomes, P is the probability of an outcome conditional on the action, Value is the monetary consequence, and Cost is the action cost. The formulation assumes that outcomes and values are defined consistently and that monetary value is an acceptable decision criterion. It should not be used as the sole criterion when safety, equity, legal duties or irreversible harm are central.

Worked decision example

A firm can launch a retention campaign costing $8,000. Without the campaign, expected profit is $30,000. With the campaign, there is a 0.6 probability of profit of $50,000 before campaign cost and a 0.4 probability of profit of $25,000 before campaign cost.

Expected value with campaign = 0.6 × $50,000 + 0.4 × $25,000 − $8,000 = $30,000 + $10,000 − $8,000 = $32,000.

The expected value without campaign is $30,000, so the expected monetary advantage of the campaign is $2,000. This does not prove that the campaign should be launched. Management should consider uncertainty in the probabilities, cash-flow timing, customer fairness, operational capacity and whether the campaign effect was established causally.

Prescriptive systems may use optimization, simulation or rules. An optimization model is useful only when the objective function, constraints and data are credible. A mathematically optimal solution can be operationally infeasible if it ignores labor availability, supplier commitments or regulatory requirements.

A Decision-Support Architecture

A modern architecture commonly includes:

  • source systems such as transactions, applications, sensors and external data;
  • ingestion and storage in warehouses, lakes or lakehouses;
  • transformation and semantic modeling;
  • metric definitions and governed KPI layers;
  • analytical models and feature pipelines;
  • visualization and decision interfaces;
  • workflow integration, alerts and feedback data.

The semantic layer is particularly important. It defines shared concepts such as “active customer,” “net revenue” and “on-time delivery.” Without it, two dashboards may use the same label for different calculations, creating what appears to be disagreement among managers.

Data lineage records where data originated, how it was transformed and where it is used. Access controls, encryption, retention policies and audit logs protect sensitive information. Role-based access should follow least privilege: users receive the access necessary for their work, not unrestricted access by default.

Illustrative Case: Regional Delivery Performance

Background

A fictional national retailer operates 2,000 stores and an online delivery service. Its operations team reports that on-time delivery fell from 94% to 88% in one quarter. Senior managers request a dashboard and a recommendation.

Problem

The initial KPI counted all orders, including orders whose promised delivery time had been changed after dispatch. Warehouse managers used a different denominator that excluded customer-requested changes. Regional comparisons were therefore disputed.

Analysis

The analytics team first created a governed definition: on-time delivery equals deliveries completed by the original customer-confirmed promised time divided by eligible delivered orders. Canceled orders and customer-requested rescheduling were documented separately. The dashboard displayed the numerator, denominator, refresh time and exclusion rules.

A trend chart showed a decline concentrated in three distribution centers. A process-stage view showed that picking time was stable, while carrier handoff delays increased. A map initially suggested that rural areas were worst affected, but normalization by order volume showed that one high-volume urban center generated the greatest absolute number of late deliveries.

The team added uncertainty and data-quality indicators. Two weeks of carrier scans were incomplete, so those results were marked as provisional. A forecast predicted continued service deterioration if volume increased, but the forecast interval was wide because a new carrier had limited historical data.

Approach and solution

Management considered three actions: add temporary sorting labor, reroute selected orders to another center, or change customer promises. The decision-support view compared expected delay reduction, cost, capacity and customer impact. The team recommended temporary labor at the constrained centers and selective rerouting, while rejecting broader promise changes because they would conceal rather than solve the operational problem.

Outcome

In this illustrative case, the organization reduced late deliveries during the following month and retained a separate measure for promise accuracy. More importantly, managers agreed on a single KPI definition and an escalation rule: a center entered operational review when its seven-day on-time rate fell below 90% with at least 500 eligible deliveries.

Learning points

The case demonstrates that visualization cannot repair an undefined metric. It also shows why rates need volumes, why data quality should be visible, why prediction does not automatically determine action, and why decision support must include constraints and accountability.

Challenges, Ethics and Governance

Common analytical and visual risks

  • Metric ambiguity: identical labels conceal different denominators.
  • Selection bias: dashboards represent only observed or included cases.
  • Aggregation bias: overall performance can conceal subgroup differences.
  • Simpson’s paradox: an aggregate trend may reverse after stratification by a relevant group.
  • Overfitting and drift: model performance may decline when behavior or conditions change.
  • False precision: many decimal places imply accuracy not supported by the data.
  • Alert fatigue: excessive warnings cause users to ignore important alerts.
  • Interactive opacity: filters and hidden calculations make results difficult to reproduce.

Ethical communication requires honesty about limitations and avoidance of misleading scales, selective time windows or unsupported causal language. Fairness analysis should examine whether errors and benefits differ across relevant groups. Privacy requires data minimization, purpose limitation and suitable protection for personally identifiable or sensitive information. Laws and regulations vary by jurisdiction, but organizations commonly face obligations concerning privacy, data protection, employment decisions, financial reporting and consumer transparency.

Automated recommendations should have a clear owner and an appeal or override process when stakes are high. Human review is not meaningful if the reviewer lacks time, authority or information about model limitations. AI-generated summaries can accelerate communication, but they may hallucinate explanations, omit uncertainty or reproduce bias. Generated content should therefore be checked against governed data and approved definitions.

Contemporary Developments and Best Practices

Cloud platforms, streaming data and embedded analytics allow decisions to be made closer to operational time. Natural-language interfaces can help users query governed metrics, but conversational convenience does not replace semantic definitions or access control. Augmented analytics can identify anomalies and generate explanations, yet explanations should be treated as hypotheses unless supported by appropriate analysis.

Best practice is to:

  1. Start with a decision, user and action rather than a chart type.
  2. Define metrics, denominators, time windows and ownership before publishing.
  3. Use the simplest visual form that answers the question accurately.
  4. Show counts, rates, targets, comparisons and relevant uncertainty together.
  5. Make data freshness, quality and lineage visible.
  6. Separate observation, explanation, prediction and recommendation.
  7. Test dashboards with representative users and accessibility needs.
  8. Monitor KPI definitions, model performance and unintended consequences.
  9. Design escalation and feedback loops so decisions produce learning data.
  10. Document assumptions and preserve an audit trail for consequential decisions.

Chapter Summary

Visualization and communication transform analytical outputs into usable organizational knowledge. Effective dashboards begin with decisions and users, use perceptually appropriate charts, define metrics precisely and make data quality visible. KPIs connect measures to strategic objectives, targets, owners and actions. Descriptive, predictive and prescriptive analytics make different claims and should not be conflated. Uncertainty should be expressed through intervals, probabilities, scenarios and sensitivity analysis rather than hidden behind precise-looking numbers. Decision support adds objectives, costs, constraints and consequences to analytical evidence. Ethical practice requires transparency, privacy protection, fairness assessment, accessibility and accountable human oversight. The ultimate test of an analytical communication system is not visual attractiveness but whether it supports sound, explainable and responsible decisions.

Key Terms

Dashboard: An interactive display designed to support monitoring, investigation or action.

Data lineage: A record of data origins, transformations and downstream uses.

Descriptive analytics: Analysis that summarizes what has happened or is happening.

Diagnostic analytics: Analysis that investigates patterns and possible contributors.

Expected monetary value: Probability-weighted value of possible outcomes minus action cost.

Insight: An interpretation of evidence that informs understanding or action.

Key performance indicator: A strategically important metric linked to an objective, target and owner.

Leading indicator: A measure that provides an early signal of future performance.

Lagging indicator: A measure of an outcome observed after activity has occurred.

Metric: A defined quantitative measure used for a specified purpose.

Prescriptive analytics: Analysis that evaluates or recommends actions.

Prediction interval: An interval expressing uncertainty about a future individual outcome.

Semantic layer: Governed business definitions and calculations shared across analytical tools.

Sensitivity analysis: Examination of how results change when assumptions or inputs vary.

Storytelling: Structuring evidence into context, interpretation, uncertainty and action.

Uncertainty: Imperfection or variability in knowledge, measurement, estimation or prediction.

Visualization: Visual encoding of data to support perception, analysis and communication.

Data quality: Fitness of data for its intended use, including accuracy, completeness and timeliness.

Review Questions

Short Answer Questions

  1. Distinguish a metric from a KPI.
  2. Why should a rate generally be presented with its underlying count?
  3. State two characteristics of an effective dashboard.
  4. What is the difference between a confidence interval and a prediction interval?
  5. Why must descriptive findings be separated from causal explanations?

Long Answer Questions

  1. Explain how an organization can design a KPI architecture from strategic objectives to operational actions.
  2. Compare descriptive, predictive and prescriptive analytics, including the evidence and limitations associated with each.
  3. Discuss principles for selecting visual encodings for comparison, distribution, time series and uncertainty.
  4. Explain how data lineage, semantic definitions and access controls contribute to trustworthy decision support.
  5. Evaluate the ethical risks of automated dashboards and AI-generated analytical narratives.

Analytical / Application Questions

  1. A website receives 50,000 eligible sessions, produces 1,500 orders and $120,000 in revenue. Calculate the conversion rate and AOV, then explain one managerial action that could improve performance.
  2. A manager claims that a region with a 12% conversion rate is superior to one with a 7% rate. The first region has 250 opportunities and the second has 10,000. Analyze why the conclusion may be incomplete and identify additional evidence required.
  3. Design a dashboard for the delivery case described in this chapter. Specify three KPIs, their definitions, suitable visual forms, an uncertainty or data-quality indicator, and an escalation rule.

Multiple Choice Questions with Answers

Question 1

Which statement best distinguishes a KPI from a general metric?

A. A KPI is always measured in currency.

B. A KPI is strategically important and linked to an objective, target and owner.

C. A KPI is calculated only from real-time data.

D. A KPI cannot be used in operational decisions.

Correct Answer: B. A KPI is strategically important and linked to an objective, target and owner.

Question 2

A site has 24,000 eligible sessions and 960 completed orders. What is its conversion rate?

A. 2%

B. 4%

C. 24%

D. 40%

Correct Answer: B. 4%

Question 3

Which chart is generally most suitable for comparing many categories on a common scale?

A. Three-dimensional pie chart

B. Ordered bar chart

C. Decorative infographic

D. Radar chart with overlapping axes

Correct Answer: B. Ordered bar chart

Question 4

What does a prediction interval primarily communicate?

A. The exact value of every future observation

B. Uncertainty about an individual future outcome

C. Only the historical sample mean

D. A guaranteed management target

Correct Answer: B. Uncertainty about an individual future outcome

Question 5

Which sequence correctly represents the analytical communication chain?

A. Action → data → measure → decision → outcome

B. Data → measure → metric → insight → decision → action

C. Metric → action → data → insight → outcome

D. Decision → insight → data → metric → action

Correct Answer: B. Data → measure → metric → insight → decision → action

Question 6

Why should dashboard rates be accompanied by counts?

A. Counts eliminate all sampling error.

B. Rates are always invalid without counts.

C. Counts provide scale and prevent small-denominator interpretations from being misleading.

D. Counts automatically establish causation.

Correct Answer: C. Counts provide scale and prevent small-denominator interpretations from being misleading.

Question 7

In the worked retention example, what was the expected value of launching the campaign after its cost?

A. $22,000

B. $30,000

C. $32,000

D. $40,000

Correct Answer: C. $32,000

Question 8

Which statement about a 95% confidence interval is correct under its assumptions?

A. There is a 95% probability that the fixed parameter is inside this already calculated interval.

B. Approximately 95% of intervals from repeated samples would contain the parameter.

C. It contains 95% of all individual future observations.

D. It proves that the estimate is causally correct.

Correct Answer: B. Approximately 95% of intervals from repeated samples would contain the parameter.

Question 9

What is the primary purpose of a semantic layer?

A. To add decorative colors to charts

B. To define shared, governed business concepts and calculations

C. To remove the need for data security

D. To guarantee that forecasts are accurate

Correct Answer: B. To define shared, governed business concepts and calculations

Question 10

Which is an example of prescriptive analytics?

A. Reporting last month’s revenue

B. Displaying the distribution of delivery times

C. Forecasting next month’s demand

D. Recommending inventory levels subject to capacity constraints

Correct Answer: D. Recommending inventory levels subject to capacity constraints

Big Data Analytics
Chapter 10 of 14