Skip to content
AI.info

Kinds of learning

Choosing the Learning Strategy Under Real Constraints

Integrate the learning families into a decision framework based on target availability, interaction, label cost, shift, safety, and evaluation evidence.

By the end you can

Comparison

Start from the evidence, not the brand name

These common situations point toward different first candidates. Hybrid designs remain possible.

The first branch — reliable targets exist — is the one that fails most quietly. A column that is present in the data is not the same thing as the target you want. A commercial health risk algorithm used across US hospitals was trained on future health-care costs, a convenient proxy for health need. Less is spent on Black patients with equal illness. So the model learned that those patients were healthier. Obermeyer and colleagues dissected it in Science in 2019. The Algorithmic Bias Playbook, hosted by the US Federal Trade Commission, has a name for the failure — “label choice bias” — and is precise about what did not go wrong: “it predicted a biased target very well”.

The size of the error was measurable, which is the point. The abstract gives it in one line: “Remedying this disparity would increase the percentage of Black patients receiving additional help from 17.7 to 46.5%.” Regulators moved on the same algorithm the same week. On 25 October 2019 the New York Department of Financial Services and Department of Health wrote jointly to UnitedHealth Group about Optum's Impact Pro. Nothing in the pipeline was broken. The target was chosen because it was already in the data. That single decision is what “audit target provenance” and “do not invent labels by convenience” are asking you to make explicit before anything is fitted.

FigureComparison · 4 columns

Reliable targets exist

Begin with supervised baselines and protected evaluation.

  • Classification, regression, or ranking
  • Audit target provenance
  • Check future population coverage
  • Add complexity only after diagnosis

Labels are scarce but inputs are abundant

Consider transfer, self-supervision, semi-supervision, or active learning.

  • Preserve a trusted labeled anchor
  • State representation assumptions
  • Measure marginal value of unlabeled data
  • Budget expert review

Actions change future outcomes

Consider planning, bandits, imitation, or reinforcement learning.

  • Define horizon and reward
  • Bound exploration
  • Check causal support
  • Compare prediction plus optimization

No target is agreed

Use exploratory unsupervised analysis or redesign the objective.

  • Do not invent labels by convenience
  • Treat clusters as hypotheses
  • Seek external validation
  • A model may be premature

Learning strategy is a portfolio of assumptions

Every approach exchanges one scarce resource for another. Direct labels cost annotation; weak labels cost source design; self-supervision costs objective and compute; reinforcement learning costs interaction and safety; transfer costs trust in the source.

Write these assumptions as risks that can be tested. A strategy is stronger when its weakest assumption has a clear experiment or fallback.

Google Flu Trends is what an untested weakest assumption looks like at scale. The model was fitted by matching 50 million search terms to 1,152 CDC data points. One assumption carried the whole design: that search behaviour is a stable proxy for illness. It was never given an experiment or a fallback. From August 2011 the model missed high in 100 of 108 weeks. In February 2013 it predicted more than double the CDC's proportion of doctor visits for influenza-like illness. Lazer and colleagues set out the diagnosis in Science in 2014: “In short, the initial version of GFT was part flu detector, part winter detector.” The trivial fallback was never beaten either. Three-week-old CDC data projected current flu prevalence better than the model did. An independent epidemiological reassessment in PLOS Computational Biology in 2013 found that the model had completely missed the first wave of the 2009 A/H1N1 pandemic and had overestimated the 2012/2013 A/H3N2 season.

Some risk survives every test a team actually runs. D'Amour and colleagues at Google gave that risk a name: underspecification. They trained 50 ResNet-50 models on ImageNet through identical pipelines, differing only in the random seed, and reported it in the Journal of Machine Learning Research in 2022. On the ImageNet validation set the fifty were interchangeable: 75.9% top-1 accuracy, standard deviation 0.11. On stress tests they were not. Variation across the ensemble on some ImageNet-C corruption tasks was an order of magnitude larger than variation on the clean test set, and the two were not usefully correlated. So the differences could not be explained away as some models simply being better trained. A pipeline that pins down everything the team wrote down still leaves the model free to choose which shortcut to lean on. The held-out test set cannot see the choice.

Visual

A practical approach-selection tree

Use this as a conversation starter rather than an automatic classifier of projects.

Step 5 is the step teams skip, because a vendor model arrives with the claim already made. Epic's proprietary sepsis prediction model arrived that way. Wong and colleagues at Michigan Medicine tested it anyway, on 27,697 patients and 38,455 hospitalisations, and published in JAMA Internal Medicine on 21 June 2021. The abstract gives the number: “The ESM had a hospitalization-level area under the receiver operating characteristic curve of 0.63 (95% CI, 0.62-0.64).” It alerted on 18% of hospitalisations and missed 67% of sepsis cases. A second, unrelated validation in JAMIA Open covered 145,885 encounters at two county emergency departments in 2023. It found sensitivity of 14.7% and a median alerting lead time of 0 minutes. On the median alert, the model told the clinicians something they already had. Two teams, two datasets, one conclusion that a target-only baseline would have produced before deployment rather than after.

Step 6 has a literature of its own. Ferrari Dacrema and colleagues examined 18 neural recommendation methods from top conferences in 2019: only 7 could be reproduced with reasonable effort, and 6 of those 7 were beaten by simple nearest-neighbour or graph heuristics. It won best paper at RecSys that year. A year later Rendle and colleagues at Google re-ran the experiments that had launched neural collaborative filtering. Their abstract opens: “First, we show that with a proper hyperparameter selection, a simple dot product substantially outperforms the proposed learned similarities.” Two independent groups, in consecutive years, counting the same thing.

FigureProcess · 6 steps
  1. 1. Is there a decision?

    If no action or analysis changes, define the purpose before modeling.

  2. 2. Is a target observable?

    If yes, test supervised baselines and target quality.

  3. 3. Are actions interactive?

    If choices alter later opportunities, assess bandit, planning, or RL structure.

  4. 4. Is unlabeled structure useful?

    Consider representation, semi-supervised, or exploratory methods with external checks.

  5. 5. Can knowledge transfer?

    Test pretrained or source models against target-only baselines.

  6. 6. Can the design be simpler?

    Compare rules, retrieval, optimization, process change, or human workflow.

Example

A staged strategy for equipment maintenance

A factory need not choose one learning family forever. Each stage below exists because the previous one exposed a limitation it could not fix, which is the only order in which added machinery can be evaluated at all.

  • Stage 1: deterministic thresholds catch known safety limits immediately.
  • Stage 2: supervised regression estimates remaining useful life from confirmed repairs.
  • Stage 3: anomaly detection surfaces unfamiliar sensor patterns for engineering review.
  • Stage 4: active learning selects uncertain cases for costly teardown analysis.
  • Stage 5: transfer learning tests whether knowledge moves across machine models.
  • Stage 6: a constrained scheduler converts predictions into maintenance plans.

Key idea

Complexity must purchase identifiable evidence

Adding self-supervision, online updating, multi-task training, or reinforcement learning creates new data dependencies and failure modes; the method is justified only when it addresses a diagnosed limitation of a simpler design.

Record what each layer is expected to improve and how that improvement will be measured. Otherwise complexity becomes untestable optimism.

Two benchmarks built by different labs show how often the extra machinery survives that test. DomainBed set nine algorithms against seven multi-domain datasets under three model-selection criteria. Gulrajani and Lopez-Paz built it in 2020, and their abstract reports what came out: “We conduct extensive experiments using DomainBed and find that, when carefully implemented, empirical risk minimization shows state-of-the-art performance across all datasets.” The thing that decided the comparison was not a new method. It was making model selection explicit. The independent WILDS benchmark of 10 real-world distribution shifts reports the same shape of result from the other direction: the in-distribution/out-of-distribution gap “remains even with models trained by existing methods for tackling distribution shifts”. Nine algorithms and ten shifts, and the honest baseline was not displaced in either place.

Every sophisticated component should have a named job, baseline, and retirement condition.

Case

$62 million on an oncology advisor no patient ever used

The bill for unmeasured complexity can be itemised. MD Anderson Cancer Center built an Oncology Expert Advisor on IBM Watson. A University of Texas System audit released in February 2017 found the centre had spent about $62 million on the project, that it had bypassed the institution's normal IT procurement process, and that invoices were “paid in full regardless of whether contracted services were delivered as agreed upon”. Support for the system ended in September 2016. It was never piloted outside MD Anderson. The Journal of the National Cancer Institute summarised the arc in May 2017: “five years and $62 million later, M. D. Anderson let its contract with IBM expire before anyone used Watson on actual patients.” No stage of that project had a measurement it was required to pass before the next stage was funded.

Steps

Write a one-page learning-strategy memo

A concise memo makes assumptions and alternatives reviewable before a large build begins.

Step 4 is where memos go thin, because “we will compare against a baseline” is a sentence that costs nothing. Dressel and Farid paid for it. In 2018 they set COMPAS — a commercial recidivism tool using 137 features — against the cheapest comparisons available, and published the result in Science Advances. Their abstract: “We further show that a simple linear predictor provided with only two features is nearly equivalent to COMPAS with its 137 features.” The two features were age and number of prior convictions. They also ran the human baseline that most memos never mention. Untrained people recruited online reached a mean accuracy of 62.1% and a median of 64.0%, no less accurate than the deployed product. The rules baseline held as well. Independently, Angelino and colleagues produced certifiably optimal sparse rule lists about as accurate as COMPAS on the Broward County data.

Four comparisons, one dataset, and a number for each: that is what step 4 is asking for. A memo that names its baselines with figures can be argued with before the build; a memo that names them as a category cannot.

FigureProcess · 6 steps
  1. 1. State the decision

    Name the user, timing, action, and consequence of the output.

  2. 2. List feedback sources

    Separate labels, outcomes, preferences, demonstrations, rules, and unlabeled data.

  3. 3. Rank assumptions

    Identify the most fragile claims about target, transfer, interaction, or shift.

  4. 4. Define baselines

    Include rules, simple models, retrieval, and current human workflow.

  5. 5. Plan evidence

    Assign datasets, experiments, slices, and stop conditions to each claim.

  6. 6. Stage complexity

    Add methods only after the previous stage exposes a specific limitation.

“Do not use machine learning” is a valid technical result

A target may be unobservable, a policy may create the labels, a simpler rule may already meet the need, or errors may be too costly for available evidence. Declining deployment can be the most rigorous conclusion.

England ran that argument at national scale in the summer of 2020. Ofqual's own research report on that year's A levels analysed 457,420 entries and records what the standardisation model did to them. It produced a grade below the teacher's centre assessment grade for 39% of entries, and above it for just over 2%. 10.3% of candidates were three or more grades down in total. On 17 August 2020 Ofqual instructed awarding bodies to reissue the higher of the two grades, which withdrew the model in the middle of its deployment. The Office for Statistics Regulation reviewed the episode independently and, on 2 March 2021, put the conclusion to the people who commission such systems in one sentence: “A statistical model might not always be the best approach to meet your need.” The failure was not in the fitting. It was in never having asked whether a model was the right instrument for the decision.

The capstone treats a no-model recommendation as successful when it follows a clear analysis of feedback, assumptions, alternatives, and risk.

Case

Amazon’s résumé scorer, and the decision not to ship it

Amazon reached that conclusion the expensive way, by building the thing first. A team formed in 2014 trained models on ten years of submitted résumés to score candidates. Most of those résumés had come from men. By 2015 the system was penalising résumés containing the word “women’s” — as in “women’s chess club captain” — and downgrading graduates of two all-women’s colleges. Engineers edited the programs to be neutral to those particular terms, but could not guarantee the models would not find other proxies for the same thing. Executives disbanded the team by the start of 2017. Reuters reported all of it on 10 October 2018. The finding was real and the engineering was competent. The correct deliverable was that it should not ship.

Key takeaways