The Data-to-Decision Loop

The executive question: where are we in the data-to-decision loop?

Most analytics mistakes come from losing track of the loop. A team starts with a model but has not named the action. A dashboard monitors a metric but has no threshold. A causal analysis estimates an effect but does not connect to a decision cadence. An AI workflow answers questions but has no evaluation or escalation path. Each failure is a broken link between data and action.

Figure 1 is the front-door operating model for the book. Part I begins in the source record. Part II turns records into visual evidence. Part III asks whether an action caused an outcome. Part IV predicts and ranks future cases. Part V brings text, documents, images, embeddings, and language models into the loop. Part VI asks how the organization runs the loop repeatedly without losing ownership, quality, or governance.

Data-driven versus data-decorated

A decision is data-driven only when three things are named:

1. The action. A specific lever someone can pull.
2. The comparison. What would happen if the firm did not act or acted differently.
3. The threshold. The signal, effect size, ROI, quality level, or risk standard required to act.

Anything missing one of these may still be useful description. It may be a good dashboard, a good analysis, or a promising model. But it is not yet a decision.

The decision ladder

The book's evidence languages climb a ladder of business questions. The lower rungs do not disappear when the upper rungs arrive. A prediction model still depends on a clean target. A causal design still depends on a well-defined unit, timing, and outcome. A language model workflow still needs source data, storage, evaluation, monitoring, and human review.

The ladder is a routing device:

• What happened? Read the data and define the metric.
• Where and for whom? Visualize, segment, compare, and diagnose.
• What caused it? Construct a credible counterfactual.
• How much does the lever matter? Estimate effects, elasticity, and heterogeneity.
• What is likely next? Predict, rank, and evaluate.
• What does the text, image, or document say? Use unstructured data and AI workflows.
• How do we operate this? Monitor, govern, communicate, and learn.

Six evidence languages

The important point is not the numbering. It is the discipline of choosing the evidence language that fits the decision. A dashboard should not be asked to prove causality. A predictive model should not be treated as an intervention. A language model should not be trusted because it is fluent. A causal estimate should not ship if no one knows what action it changes.

The artifacts that survive the work

The book does not end each method with "and now you know the method." It ends with an artifact that a firm can reuse, audit, and refresh.

The artifact family matters because modern analytics is not a sequence of one-off clever analyses. It is infrastructure for repeated decisions. A metric card can be reused in a dashboard. A predictive task contract can be reused by a modeling team. A model card can be used by risk, legal, product, and operations. An AI workflow card can be audited when the workflow changes. A decision memo can show what evidence led to action and how the firm will learn afterward.

The cases

One through-line company, Bean & Basket Coffee, appears throughout the book. Standalone cases add real empirical grounding where a specific method needs a richer dataset.

The purpose of the cases is not to decorate chapters. It is to make the loop concrete. Every case asks: what activity generated the data, where is it stored, what evidence language fits the decision, what artifact should survive, and how would the organization monitor what happens next?

Where Part I begins

Part I now begins after the full system is visible. We zoom in from the operating loop to the basic object inside it: a dataset. The first question becomes almost physical: what does one row mean? That question sounds small, but it controls everything that follows. Grain, structure, variable type, joins, reshaping, metrics, and data quality are the mechanics that make the larger loop trustworthy.