Paper Breakdowns  /  PaLM
Paper 82~10 min readGoogle 2022worked math + runnable code
Paper Breakdown

PaLM,
explained.

Scale a model up and, for a while, some tasks just... don't work. Multi-step word problems: flat at chance. Then you cross some size, and — snap — the model can do them. PaLM, at 540 billion parameters, put this emergence on the map: abilities that are absent in smaller models and appear, seemingly out of nowhere, in bigger ones. It looks like magic. It isn't. The cleanest explanation is a single exponent, and once you see it, the "sudden breakthrough" becomes almost inevitable. Here's the math behind the jump.

Video breakdown
The animated walkthrough is in production.
Read the full breakdown below in the meantime ↓
01

The sudden jump

PaLM is a 540-billion-parameter dense transformer, trained across thousands of TPU chips with Google's Pathways system (which the model is named after). It set state-of-the-art on a broad sweep of benchmarks. But its most quoted contribution isn't a number on a leaderboard — it's a shape of curve: the demonstration that certain abilities are emergent, near-absent below a scale and present above it.

With chain-of-thought prompting, PaLM solved multi-step arithmetic and commonsense problems that smaller models failed outright; it could even explain why a novel joke is funny. Plotted against scale, these tasks stay pinned at chance and then leap. That discontinuity provoked a lot of philosophizing about "phase transitions" in intelligence. The more grounded story is simpler and worth understanding, because it demystifies the whole phenomenon.

The one-sentence version

A task that needs many sequential steps right scores per-step-accuracy to the power k — so a smooth improvement in per-step accuracy becomes a sharp, sudden jump on the composed task once the model is big enough.

02

What emergence is

An emergent ability is one that's essentially at random-chance performance in smaller models and then rises, sometimes abruptly, once scale crosses a threshold. The defining feature is discontinuity: you scale and scale, the metric stays flat, and then it moves. Smooth quantities like loss keep improving predictably (that's scaling laws); emergent task metrics are the ones that look like a cliff.

PaLM made this vivid across many BIG-bench tasks. But "the model suddenly gained a new skill" is a strong claim — and mostly the wrong frame. What actually changed smoothly under the hood was the model's per-step competence; what looked discontinuous was a composed metric built on top of it. To see why, follow a multi-step task and count where it can go wrong.

03

Why steps compound

A multi-step reasoning problem is an all-or-nothing chain: get any single step wrong and the final answer is wrong. So if a task needs k sequential steps and the model gets each one right with probability p, the whole task succeeds only when every step lands.

Why a smooth per-step gain looks like a task-level cliff
Per-step pImproves smoothly with scale — no jump here.
Compose kTask needs all k steps right → success rate = pk.
Small ppk is tiny — the task looks stuck at chance.
p climbsOnce p is high, pk rises sharply — the apparent breakthrough.

That single power is the whole trick. While per-step accuracy is modest, raising it to a high power crushes the task score toward zero — it looks like the model simply can't do the task. As per-step accuracy climbs past a point, the same power law snaps the task score upward. Nothing discontinuous happened to the model; a smooth curve got run through an exponent. Harder tasks (bigger k) need higher per-step accuracy before they clear the bar, so they emerge later — exactly the ordering observed.

04

One exponent

Let per-step accuracy p rise smoothly with scale, and let a task require k correct steps. Task accuracy is:

Atask  =  pk     (all k steps must be right)

A tiny per-step failure rate compounds: at p=0.8, an 8-step task scores 0.8⁸ ≈ 0.17; at p=0.95 it's 0.95⁸ ≈ 0.66. A modest per-step gain nearly quadruples the task score.

The amplification grows with the chain length. Compare two per-step accuracies; the task-level advantage of the better model is the per-step ratio raised to k:

Atask(p₂) / Atask(p₁)  =  (p₂ / p₁)k   ⟹   longer chains  =  bigger jumps

The same per-step edge (say 0.8→0.9) is a 1.8× task advantage at k=5 but a ~10× advantage at k=20. So the longer the reasoning chain, the more a smooth per-step improvement looks like an abrupt emergence — and the later (in scale) it kicks in. The runnable version below turns a smooth per-step curve into the sharp task jump.

RUN IT YOURSELF

Make emergence out of a smooth curve

Emergence needs no magic — just an exponent. Let per-step accuracy rise smoothly (a logistic in scale, from chance toward 1). A task that needs k sequential steps scores that accuracy to the power k, so at small scale an 8-step task sits near chance and at large scale it's near-perfect — a sharp jump from a smooth input. The same per-step gain (0.8→0.9) is amplified far more for a 20-step task than a 5-step one, and harder (longer) tasks clear the bar at a larger scale. Change k or the scale and watch the cliff move.

CPython · WebAssembly
05

What PaLM did

Beyond the emergence story, PaLM was a milestone in scale and engineering:

ResultSignificance
540B dense, one modelAmong the largest dense LMs of its time — pushed how far a single dense transformer scales.
Emergent reasoningWith chain-of-thought, solved multi-step problems smaller models couldn't — the headline demonstration.
Pathways / high MFUTrained across two TPU v4 pods with high model-FLOPs utilization — the systems feat behind the scale.
Broad SOTAState-of-the-art across many language, reasoning, and code benchmarks, plus some multilingual ability.

The joke-explanation demo is the one people remember: given a joke it hadn't seen, PaLM could articulate why it lands. Whether you call that "understanding" or sophisticated pattern completion, it was a concrete signal that qualitatively new behaviors were showing up as scale grew — which is precisely why the emergence framing stuck.

06

Scale as a strategy

PaLM helped cement scale as a deliberate research strategy: keep making models bigger and qualitatively new capabilities keep appearing. It also sharpened a debate that's still live — how much of "emergence" is a real phase change versus an artifact of using harsh, all-or-nothing metrics. The compositional exponent above is the strongest version of the skeptical view: use a continuous metric and the cliff often becomes a smooth ramp. Both can be true — the underlying skill improves smoothly, while the useful composed task genuinely flips from unusable to usable.

Practically, the takeaway outlived the model. Emergence is why techniques like chain-of-thought matter so much: by breaking a hard composed task into steps the model can each do reliably, you keep per-step accuracy high and dodge the pk collapse. PaLM itself was soon surpassed and Google moved to the Gemini line, but its lesson — that where you set the metric determines whether progress looks smooth or sudden — is now part of how the field reads every scaling curve.

Worth knowing

Chain-of-thought and the pk view are two sides of one coin: prompting the model to show its steps lets each step be graded and kept accurate, so the composed task avoids the exponential collapse that made it look impossible in the first place.

Frequently asked

Quick answers

What is PaLM?

Google's 2022 540-billion-parameter dense transformer trained with the Pathways system, a landmark for scale and emergent abilities.

What are emergent abilities?

Capabilities near random-chance in smaller models that appear, often abruptly, once scale crosses a threshold — like PaLM's multi-step reasoning.

Why the sudden jump?

A k-step task scores per-step accuracy to the power k, so a smooth per-step improvement becomes a sharp task-level jump once accuracy is high.

What is Pathways?

Google's distributed ML system that trained a single 540B model across TPU pods with high model-FLOPs utilization — the model is named after it.

Finished this one? 0 / 101 Paper Breakdowns done

Explore the topic

See this alongside everything else on the same subject — handbooks, system designs, challenges and tools, in one place.

More Paper Breakdowns