Chapter 13: 13. Visualization, Decision Analytics and Organizational Application

1. Introduction

Quantitative and qualitative analysis creates value only when evidence is translated into understanding, action, and accountable decisions. Statistical results, themes from interviews, predictive models, and evaluation findings are not self-executing. They must be communicated to people who have different levels of technical knowledge, different responsibilities, and different interests. Visualization, decision analytics, dashboards, scenario analysis, and uncertainty communication provide the bridge between analysis and organizational action.

In contemporary organizations, this bridge is especially important because digital transformation generates large volumes of data from enterprise systems, customer platforms, sensors, applications, social media, and connected devices. The challenge is not simply to produce more information. It is to identify what matters, represent it accurately, interpret it in context, and connect it to decisions that support organizational strategy. A sophisticated dashboard can still produce poor decisions if its measures are misleading, its data are biased, or its users do not understand uncertainty.

This chapter examines how analytical findings can be converted into defensible managerial and policy decisions. It treats visualization as an analytical language, decision analytics as a structured approach to selecting actions, and organizational application as a process of embedding evidence within governance, culture, and digital-transformation strategy.

2. Learning Objectives

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

1. Explain the role of visualization and decision analytics in organizational decision-making.

2. Select visual forms appropriate to data type, analytical purpose, and audience.

3. Design dashboards that distinguish strategic, tactical, and operational information.

4. Apply scenario analysis, sensitivity analysis, and decision models under uncertainty.

5. Communicate statistical, model, and measurement uncertainty responsibly.

6. Integrate quantitative and qualitative evidence in managerial and policy analysis.

7. Evaluate the ethical, governance, and strategic implications of analytics applications.

8. Critically assess the implementation of analytics within digital-transformation programs.

3. Meaning and Concept

Visualization is the deliberate representation of data, evidence, or analytical results in graphical, spatial, interactive, or narrative form. Its purpose is not decoration. Effective visualization supports pattern recognition, comparison, explanation, exploration, and action. A chart communicates a claim about the data; therefore, design choices such as scale, aggregation, color, ordering, and annotation influence interpretation.

Decision analytics is the systematic use of data, models, assumptions, and decision criteria to evaluate alternatives and choose actions. It extends beyond descriptive reporting. Descriptive analytics asks what happened, diagnostic analytics asks why it happened, predictive analytics asks what may happen, and prescriptive or decision analytics asks what should be done given objectives, constraints, and uncertainty.

Organizational application refers to the institutional use of analytical knowledge in processes such as budgeting, service delivery, risk management, marketing, human-resource planning, public policy, and strategic transformation. Application requires more than technical capability. It depends on data quality, leadership, governance, user trust, process redesign, and the willingness to act on evidence.

A defensible decision is one that can be explained in relation to its objective, evidence, assumptions, alternatives, risks, and accountability arrangements. Defensibility does not mean that the decision is guaranteed to succeed. It means that the reasoning process is transparent, proportionate, reviewable, and ethically acceptable.

4. Fundamental Principles

4.1 Start with the decision, not the data

An analytical product should begin with a decision question. “Which branches require intervention?” is more useful than “What data do we have?” The decision question determines the population, measures, time horizon, alternatives, and acceptable level of uncertainty.

4.2 Match representation to purpose

A line chart is generally appropriate for trends, a bar chart for category comparison, a scatterplot for relationships, a map for spatial distribution, and a network diagram for connections. No visual form is universally superior. The appropriate choice depends on the analytical task and the audience.

4.3 Preserve proportionality and context

Visual encodings should represent quantities proportionately. Truncated axes, inappropriate three-dimensional effects, excessive color, and unequal category widths can exaggerate or conceal differences. Contextual benchmarks, denominators, time periods, and data definitions should be visible or easily accessible.

4.4 Separate observation from interpretation

A dashboard may show that waiting times increased after a policy change. It should not imply that the policy caused the increase unless the research design supports a causal conclusion. Analysts must distinguish data patterns, plausible explanations, causal claims, and recommended actions.

4.5 Make uncertainty visible

Point estimates alone can create false confidence. Confidence intervals, prediction intervals, probability ranges, scenario bands, data-quality indicators, and narrative qualifications help users understand what is known and what remains uncertain.

4.6 Integrate multiple forms of evidence

Quantitative indicators may show the magnitude of a problem, while interviews or observations explain how and why it occurs. Mixed-method decision support is strongest when each form of evidence has a defined role and the integration process is explicit.

4.7 Design for the user and the decision context

Executives, analysts, frontline employees, regulators, and citizens require different levels of detail. A chief executive may need a small set of strategic indicators, whereas an operations manager may require drill-down capability. Accessibility, language, device constraints, and organizational literacy must be considered.

4.8 Create a traceable analytical chain

Users should be able to move from a displayed indicator to its definition, source, transformation, model, assumptions, and responsible owner. Traceability supports auditability, learning, and correction.

5. Major Components / Elements

5.1 Data and measurement layer

This layer contains source systems, data definitions, metadata, quality checks, sampling procedures, and measurement rules. A metric such as “customer retention” is incomplete unless the organization specifies the customer population, observation period, exclusion rules, and calculation method.

5.2 Analytical layer

The analytical layer includes descriptive statistics, inferential tests, qualitative coding, predictive models, optimization, simulation, and evaluation methods. The method should be proportionate to the decision. A complex model is not automatically better than a transparent one.

5.3 Visualization layer

This layer converts analytical outputs into charts, maps, tables, narrative explanations, and interactive interfaces. It should emphasize hierarchy: the most important message should be immediately visible, while detail remains available for investigation.

5.4 Decision layer

Decision analytics identifies objectives, alternatives, constraints, criteria, risks, and trade-offs. It may use cost-benefit analysis, multicriteria decision analysis, expected utility, scenario planning, or optimization.

5.5 Communication and narrative layer

A narrative explains what the evidence means for a particular audience. It should state the finding, its practical significance, limitations, and recommended action. Narrative is not permission to simplify inaccurately; it is a means of making evidence intelligible.

5.6 Governance and feedback layer

Governance defines ownership, access, privacy controls, model validation, approval processes, documentation, and monitoring. Feedback mechanisms reveal whether a decision improved outcomes and whether the model continues to perform adequately.

6. Process / Framework / Methodology

A practical framework for organizational decision analytics consists of ten stages.

Stage 1: Define the decision and its purpose

Specify who must decide, what action is being considered, the relevant time horizon, and how success will be judged. A policy decision may involve equity and public accountability in addition to efficiency.

Stage 2: Identify stakeholders and consequences

Map decision-makers, affected groups, data owners, implementers, and oversight bodies. Consider who benefits, who bears risks, and who may be excluded from the data.

Stage 3: Construct the evidence plan

Identify required data, qualitative sources, indicators, comparison groups, and analytical methods. Define the minimum evidence needed to make a responsible decision.

Stage 4: Assess data quality and comparability

Examine missingness, measurement error, bias, duplicate records, changes in definitions, and differences between units. Comparisons across departments or countries may be invalid if the underlying measures differ.

Stage 5: Analyze and triangulate

Use appropriate quantitative and qualitative methods. Compare results across data sources, time periods, models, and stakeholder accounts. Contradictions should be investigated rather than concealed.

Stage 6: Visualize the evidence

Develop exploratory displays for analysts and explanatory displays for decision-makers. Use annotations to identify thresholds, unusual events, policy changes, and limitations.

Stage 7: Develop alternatives and scenarios

Define feasible courses of action. For each alternative, estimate costs, benefits, risks, distributional effects, implementation requirements, and likely unintended consequences.

Stage 8: Test sensitivity and uncertainty

Vary important assumptions, such as demand growth, adoption rates, costs, or model parameters. Identify which assumptions could reverse the recommendation.

Stage 9: Decide, document, and implement

Record the selected option, rejected alternatives, evidence considered, assumptions, responsible owners, milestones, and safeguards. Implementation should include measurable indicators and escalation rules.

Stage 10: Monitor, evaluate, and learn

Track outcomes rather than merely activity. Compare actual results with forecasts, examine subgroup effects, and update the model or intervention when evidence changes.

7. Important Theories and Models

7.1 DIKW hierarchy

The data-information-knowledge-wisdom model describes a progression from raw observations to interpreted information, organizational understanding, and judgment about action. The model is useful as a communication device, although the stages are not always linear. Knowledge can reveal the need for new data, and practical wisdom includes ethical and contextual considerations that a database cannot provide.

7.2 Descriptive, predictive, and prescriptive analytics

Descriptive analytics summarizes past and current conditions. Predictive analytics estimates future outcomes or probabilities. Prescriptive analytics evaluates possible interventions under objectives and constraints. An organization should not use a predictive score as though it were a prescription; prediction and action require different assumptions.

7.3 Expected utility and decision trees

Expected utility evaluates alternatives by weighting possible outcomes by their probabilities and value to the decision-maker. A decision tree represents choices, uncertain events, and resulting consequences. These models are useful when probabilities and consequences can be estimated, but they can create an appearance of precision when inputs are weak.

7.4 Multicriteria decision analysis

Multicriteria decision analysis is appropriate when alternatives must be assessed against several criteria, such as cost, quality, equity, feasibility, environmental impact, and risk. Criteria are weighted, alternatives are scored, and sensitivity analysis examines whether rankings change under different weights.

7.5 Scenario planning

Scenario planning develops several plausible futures rather than forecasting a single outcome. Scenarios may differ in economic conditions, technological adoption, regulation, workforce availability, or customer behavior. The objective is organizational preparedness, not prediction of one inevitable future.

7.6 Logic models and theories of change

A logic model links inputs, activities, outputs, short-term outcomes, and long-term impacts. A theory of change explains why those links are expected to operate. These models help organizations distinguish implementation failure from theory failure and select indicators at each stage.

7.7 Balanced Scorecard

The Balanced Scorecard connects financial, customer, internal-process, and learning-and-growth perspectives. Its value lies in linking measures to strategy rather than accumulating indicators. Poorly designed scorecards can encourage target gaming and excessive focus on measurable outcomes.

7.8 Statistical process control

Control charts distinguish ordinary process variation from unusual variation requiring investigation. They are valuable in manufacturing, healthcare, service operations, and information systems. A process should not be redesigned merely because one observation is above or below an arbitrary target.

8. Practical Applications

In healthcare, visualization can display patient-flow bottlenecks, readmission rates, infection patterns, and disparities by population group. Decision analytics can compare staffing models or prioritize preventive interventions. In finance, dashboards monitor liquidity, credit exposure, fraud signals, and scenario-based capital requirements. In marketing, cohort analysis and customer-journey visualization support retention strategies while requiring careful attention to consent and profiling risks.

In public administration, dashboards can track service access, case-processing times, budget execution, and regional inequality. However, public dashboards must explain definitions and limitations because citizens may interpret rankings as judgments of institutional quality. In education, analytics can identify patterns of disengagement, but automated risk scores should support—not replace—professional judgment and student dialogue.

In information technology management, visualization supports incident management, service-level monitoring, cloud-cost optimization, cybersecurity risk analysis, and digital-adoption measurement. Qualitative evidence from service desks and user interviews can explain why a technically available system is not being adopted.

9. Examples

A retailer observes that online conversion is lower on mobile devices. A basic dashboard shows the difference, but decision analytics investigates page-load time, payment failure, device type, customer segment, and traffic source. A/B testing may estimate the effect of a redesigned checkout, while interviews reveal that customers distrust the payment screen. The decision should consider incremental revenue, development cost, security, and accessibility rather than conversion rate alone.

A university observes declining completion rates in an online doctoral course. Quantitative analysis identifies a relationship with delayed feedback, while qualitative interviews reveal that students cannot interpret assessment criteria. The intervention therefore combines faster feedback, clearer rubrics, and academic advising. Success is assessed through completion, learning quality, student experience, and subgroup equity.

10. Technology and Digital Applications

Business-intelligence platforms support data integration, interactive dashboards, role-based access, and scheduled reporting. Statistical and programming environments support reproducible analysis, simulation, and model validation. Geographic information systems enable spatial analysis, while process-mining tools reconstruct workflows from event logs and identify bottlenecks.

Machine-learning systems can generate forecasts, anomaly alerts, and recommendations. Their use requires monitoring for drift, subgroup performance differences, explainability needs, and inappropriate automation. Natural-language interfaces may allow managers to query data conversationally, but generated answers must remain connected to governed sources and documented definitions.

Cloud data platforms, application programming interfaces, and data catalogs facilitate scalable access and metadata management. Digital twins and simulation environments can test operational changes before implementation. Technology should be selected because it improves a decision process, not because it is fashionable.

11. Strategic / Managerial Importance

Visualization and decision analytics align operational activity with strategic priorities. They help leaders identify capability gaps, allocate resources, detect emerging risks, and evaluate whether digital investments produce organizational value. They also create a common language across technical and managerial communities.

Strategically, analytics can support dynamic capabilities: sensing changes, seizing opportunities, and transforming processes. Managerially, it can clarify accountability by assigning metric ownership and decision rights. Yet measurement can distort strategy when employees optimize indicators rather than outcomes. Leaders must therefore combine performance metrics with professional judgment, qualitative review, and periodic reassessment of what the organization truly values.

12. Detailed Case Study

The following is a fictional illustrative case.

Background

Northbridge Municipal Services operates a digital platform for housing-repair requests. The city has invested in mobile applications, automated routing, and a public performance dashboard. Despite these investments, resident satisfaction has declined and complaints about unequal service have increased.

Problem

The public dashboard reports average completion time, but the average has remained stable while some neighborhoods experience severe delays. Managers initially propose adding contractors. Community organizations argue that the problem includes language barriers, poor status communication, and inconsistent triage.

Analysis

The analytics team disaggregates completion time by neighborhood, repair type, tenancy status, language preference, and request channel. A median and percentile analysis reveals that the average conceals a long upper tail. Process mining shows that requests submitted by telephone are re-entered manually and are more likely to be misclassified. Qualitative interviews indicate that residents often submit duplicate requests because they cannot see status updates. A map identifies concentration of delays near two maintenance depots.

A predictive model estimates the probability that a request will exceed the service standard. Model review finds lower accuracy for residents whose records contain incomplete contact information. The team therefore rejects automatic prioritization based solely on the model and treats missing information as a service problem rather than evidence of low priority.

Strategy / Solution

Northbridge adopts a combined solution. It redesigns the intake form, provides multilingual status messages, establishes a manual review queue for high-risk cases, and reallocates contractors according to workload and travel time. The dashboard is revised to show median completion time, the 90th percentile, backlog age, repeat requests, and results by neighborhood. A governance committee approves definitions, reviews subgroup impacts monthly, and publishes an explanation of limitations.

Scenario analysis considers three staffing options under low, medium, and high demand. The selected option is not the cheapest under the central forecast, but it is more resilient under high-demand conditions. A six-month evaluation compares outcomes before and after implementation while monitoring seasonal effects.

Outcome

After six months, the long-delay tail decreases, duplicate requests fall, and satisfaction improves most in neighborhoods previously experiencing the greatest delays. Overall average completion time changes little, demonstrating why a single headline metric would have understated the improvement. The city also identifies continuing problems in contractor availability and retains a contingency plan.

Learning Points

The case illustrates that visualization can expose distributional inequality, not merely central tendency. Qualitative evidence can explain mechanisms that administrative data do not capture. Predictive models require fairness and data-quality review. Scenario analysis supports resilience, while governance ensures that performance improvement does not depend on hidden or unjustifiable practices.

13. Advantages / Benefits

Effective visualization reduces cognitive effort, reveals trends and outliers, supports rapid comparison, and enables users to explore complex evidence. Decision analytics makes assumptions explicit, clarifies trade-offs, improves resource allocation, and supports consistent evaluation of alternatives. Organizational application can strengthen accountability, improve service quality, detect risk earlier, and align digital investments with measurable outcomes. When quantitative and qualitative evidence are integrated, organizations gain both scale and contextual understanding.

14. Limitations / Challenges

Visualization can mislead through poor design, selective reporting, aggregation, or inappropriate scales. Dashboards may encourage short-term target management rather than long-term value. Models may encode historical discrimination, fail when conditions change, or be misunderstood by users. Data integration is difficult when systems use incompatible definitions. Organizations may also suffer from dashboard proliferation, alert fatigue, weak data literacy, and resistance from professionals who see analytics as surveillance.

Uncertainty is often difficult to communicate because decision-makers prefer definite answers. Conversely, excessive technical qualification can make evidence unusable. The analyst must find a balance between accessibility and accuracy. Finally, evidence does not eliminate political, ethical, or value-based disagreement; many decisions involve legitimate conflicts among objectives.

15. Ethical and Governance Considerations

Ethical analytics requires attention to privacy, consent, fairness, transparency, accountability, security, and proportionality. Data should be collected and used for legitimate purposes, with access restricted according to role and need. Sensitive attributes should not be ignored automatically; they may be necessary for detecting disparate impacts, subject to appropriate safeguards.

Organizations should document data provenance, model purpose, training data, validation results, limitations, and decision authority. Automated recommendations require human oversight when consequences are significant. Individuals should have avenues for explanation, correction, appeal, and redress. Governance should also address secondary use, data retention, vendor accountability, cybersecurity, and the risk that public or employee rankings create harmful incentives.

16. Current and Emerging Trends

Important trends include augmented analytics, real-time event monitoring, privacy-enhancing computation, synthetic data, process mining, digital twins, responsible artificial intelligence, and decision intelligence platforms. Generative AI is increasingly used to summarize dashboards and produce natural-language explanations, but it can hallucinate, omit uncertainty, or reproduce biased interpretations. Organizations are therefore developing retrieval controls, human review, provenance indicators, and model-risk management.

There is also growing interest in equity-centered analytics, climate and sustainability dashboards, interoperable data spaces, and outcome-based public management. The movement is from isolated reports toward continuously monitored decision systems. This increases the importance of governance because errors can propagate rapidly across interconnected processes.

17. Best Practices

1. Begin with a clearly defined decision and intended user.

2. Use a limited set of meaningful indicators linked to strategy.

3. Display denominators, time periods, benchmarks, and data definitions.

4. Show distributions and subgroup results, not only averages.

5. Communicate uncertainty and distinguish correlation from causation.

6. Integrate qualitative evidence where context or mechanisms matter.

7. Test visualizations with representative users, including accessibility users.

8. Document data lineage, transformations, models, and assumptions.

9. Conduct sensitivity, fairness, and scenario analysis before high-impact use.

10. Assign ownership for each metric and establish review schedules.

11. Monitor outcomes and unintended consequences after implementation.

12. Retire indicators and dashboards that no longer support decisions.

18. Future Scope

Future decision systems will increasingly combine streaming data, simulation, machine learning, human expertise, and participatory input. The most valuable systems will not simply automate decisions; they will help organizations compare alternatives, understand uncertainty, and learn from implementation. Advances in causal inference may improve intervention evaluation, while privacy-enhancing methods may enable collaboration without exposing sensitive records.

Doctoral-level research opportunities include measuring the organizational effects of dashboards, designing fair decision-support systems, evaluating human-AI collaboration, developing uncertainty visualizations for nontechnical audiences, and studying how analytics changes power and accountability. The central future challenge is sociotechnical: building systems that are technically capable, organizationally usable, and publicly legitimate.

19. Chapter Summary

Visualization and decision analytics translate analytical findings into organizational understanding and action. Effective practice begins with a decision question, uses valid and contextualized evidence, represents information appropriately, and makes uncertainty explicit. Dashboards should support strategy rather than merely display activity. Scenario analysis, decision trees, multicriteria models, logic models, and process control provide complementary ways to evaluate alternatives and monitor results. Quantitative and qualitative evidence should be integrated when magnitude and context are both important. Technology enables scale, but governance, ethics, human judgment, and organizational learning determine whether analytics produces responsible value.

20. Key Terms

1. Visualization — Graphical or interactive representation of data and analytical results.

2. Decision analytics — Structured use of evidence, models, objectives, and constraints to select actions.

3. Dashboard — A user interface presenting selected indicators for monitoring or decision-making.

4. Descriptive analytics — Analysis that summarizes past or current conditions.

5. Predictive analytics — Analysis that estimates future outcomes or probabilities.

6. Prescriptive analytics — Analysis that evaluates recommended actions under specified conditions.

7. Scenario analysis — Examination of possible futures based on alternative assumptions.

8. Sensitivity analysis — Testing how results change when assumptions or inputs vary.

9. Uncertainty — Incompleteness or variability concerning data, parameters, models, or outcomes.

10. Data lineage — Record of data origins, transformations, and movement through systems.

11. Multicriteria decision analysis — Evaluation of alternatives against multiple weighted criteria.

12. Logic model — Representation linking inputs, activities, outputs, outcomes, and impacts.

13. Process mining — Analysis of event logs to understand and improve organizational processes.

14. Triangulation — Comparison of evidence from multiple sources, methods, or perspectives.

15. Metric ownership — Assignment of responsibility for defining, maintaining, and interpreting an indicator.

16. Model drift — Decline in model performance as data or conditions change.

17. Fairness — Equitable treatment and impact across relevant groups.

18. Data governance — Policies and responsibilities governing data quality, access, use, and protection.

21. Review Questions

Short Answer Questions

1. What distinguishes descriptive, predictive, and prescriptive analytics?

2. Why should dashboards display distributions rather than only averages?

3. What is the purpose of sensitivity analysis?

4. How can qualitative evidence strengthen a quantitative decision analysis?

5. Define data lineage and explain its importance.

Long Answer Questions

1. Explain the principles of effective organizational visualization and illustrate how poor design can produce misleading decisions.

2. Discuss a complete framework for converting analytical findings into an implemented and evaluated decision.

3. Compare expected utility, multicriteria decision analysis, and scenario planning.

4. Analyze the ethical and governance requirements for high-impact predictive analytics.

5. Explain how dashboards can support digital-transformation strategy while also creating dysfunctional incentives.

Analytical / Application Questions

1. A hospital dashboard shows that average waiting time has improved, but complaints have increased. Design an analytical investigation using quantitative, qualitative, visualization, and governance techniques.

2. A public agency must choose among three technology investments with different costs, benefits, risks, and equity effects. Propose a multicriteria decision model and explain how you would test its sensitivity.

3. A predictive employee-turnover model performs well overall but poorly for a minority group. Recommend whether and how it should be used, including validation, fairness, human oversight, and appeal mechanisms.

22. Multiple Choice Questions with Answers

Question 1

Which statement best describes prescriptive analytics?

A. It summarizes historical performance.

B. It estimates the probability of future events.

C. It evaluates possible actions under objectives and constraints.

D. It stores data definitions and metadata.

Correct Answer: C. It evaluates possible actions under objectives and constraints.

Question 2

Why is displaying the 90th percentile useful when analyzing service completion time?

A. It removes the need for qualitative evidence.

B. It reveals the experience of cases near the long-delay tail.

C. It guarantees a causal explanation.

D. It always produces a lower value than the average.

Correct Answer: B. It reveals the experience of cases near the long-delay tail.

Question 3

What is the primary purpose of sensitivity analysis?

A. To test how conclusions change when assumptions vary.

B. To replace all managerial judgment with automation.

C. To eliminate uncertainty from a model.

D. To ensure that every indicator has the same weight.

Correct Answer: A. To test how conclusions change when assumptions vary.

Question 4

Which visualization is generally most appropriate for showing change over time?

A. Line chart

B. Network diagram

C. Treemap

D. Pie chart

Correct Answer: A. Line chart

Question 5

In the Northbridge case, why was automatic prioritization based solely on the predictive model rejected?

A. The model had no relationship to service outcomes.

B. Incomplete records created possible unfairness and reflected a service problem.

C. Predictive models cannot be used in public administration.

D. The city lacked any historical data.

Correct Answer: B. Incomplete records created possible unfairness and reflected a service problem.

Question 6

What does data lineage enable an organization to do?

A. Guarantee that a forecast will be correct.

B. Trace data origins and transformations.

C. Remove the need for data governance.

D. Convert qualitative data into quantitative data automatically.

Correct Answer: B. Trace data origins and transformations.

Question 7

Which method is most suitable when alternatives must be assessed using cost, equity, feasibility, and environmental impact?

A. Multicriteria decision analysis

B. Simple frequency analysis

C. A single control chart

D. Random data deletion

Correct Answer: A. Multicriteria decision analysis

Question 8

What is model drift?

A. A deliberate change in dashboard color.

B. Declining model performance as conditions or data change.

C. The movement of data between secure systems.

D. A method for assigning criteria weights.

Correct Answer: B. Declining model performance as conditions or data change.

Question 9

Which practice best supports responsible uncertainty communication?

A. Showing only a single point estimate.

B. Hiding limitations to avoid confusing users.

C. Using ranges, intervals, scenarios, and clear qualifications.

D. Replacing all statistical results with anecdotes.

Correct Answer: C. Using ranges, intervals, scenarios, and clear qualifications.

Question 10

What is the central strategic risk of optimizing a performance indicator in isolation?

A. The organization may improve the metric while harming the underlying outcome.

B. The organization will necessarily collect too little data.

C. The indicator will become impossible to visualize.

D. Qualitative research will automatically become invalid.

Correct Answer: A. The organization may improve the metric while harming the underlying outcome.