06-reference

data science for business

Thu Apr 02 2026 20:00:00 GMT-0400 (Eastern Daylight Time) ·book ·by Foster Provost, Tom Fawcett

Data Science for Business — Foster Provost & Tom Fawcett

Summary

The definitive bridge between data science technique and business application. Provost and Fawcett map the canonical data mining tasks, the CRISP-DM process, and the organizational structures that make data science actually work. Core mental models:

  1. Two Types of Data-Driven Decisions. (a) Discovery-based: finding unknown patterns in data. (b) Repetitive at scale: decisions made millions of times where even small accuracy improvements compound. The type determines the approach.

  2. Canonical Data Mining Tasks. Classification (predict category), regression (predict number), similarity matching (find alike items), clustering (group by similarity without a target), co-occurrence grouping / market-basket analysis (find items that appear together in transactions), profiling (characterize typical behavior for anomaly detection), link prediction (predict connections between items), and causal modeling (understand what actually influences what). The critical skill: decompose a business problem into pieces that map to known tasks.

  3. A Model Is a Simplified Representation of Reality Created to Serve a Purpose. This definition is load-bearing. Models don’t need to be “right” — they need to be useful for the decision at hand. Descriptive models tell you what churning customers look like; predictive models tell you who will churn. Different purposes, different standards.

  4. CRISP-DM Process. Business Understanding -> Data Understanding -> Data Preparation -> Modeling -> Evaluation -> Deployment. The critical insight is that data mining is closer to R&D than engineering — it requires problem formulation skill, rapid prototyping, and comfort with ambiguity, not just technical execution.

  5. The Over-the-Wall Problem. “Your model is not what the data scientists design, it’s what the engineers build.” Data science engineers — people who understand both the production system and the data science — are the critical bridge role. Data scientists should remain involved through deployment; engineers should be involved from the start.

  6. Overfitting as Organizational Hazard. Looking too hard at data finds something that won’t generalize. This applies to business decisions too — optimizing too narrowly on historical patterns creates brittleness. Evaluation environments that mirror production are essential before deployment.

Relevance

Open Questions