Home / Blog / Quantum Error Correction After Willow and Heron: What Changed and What Didn't
Quantum Hardware · Analysis

Quantum Error Correction After Willow and Heron: What Changed and What Didn't

2026-02-26 · Suman Reddy T · 8 min read

Two hardware milestones reframed every quantum conversation we have with enterprise clients: Google's Willow chip demonstrating below-threshold error correction, and IBM's Heron-class processors anchoring a modular scaling roadmap. Both matter. Neither means what the headlines implied. Here's the engineering read.

The threshold result, in plain terms

Qubits are error-prone, so quantum error correction encodes one reliable logical qubit across many physical qubits. The catch: error correction itself uses noisy components, so it only helps if physical error rates sit below a critical threshold. Above it, adding qubits makes things worse; below it, adding qubits makes the logical qubit exponentially better.

Willow's significance is demonstrating that crossing in practice: as Google grew the surface-code patch from distance-3 to distance-5 to distance-7, logical error rates fell by roughly half at each step. That's the regime fault tolerance requires, shown on real hardware rather than in simulation. It converted "does scaling even work?" from a physics question into an engineering one.

What it didn't change

The arithmetic of useful fault tolerance remains brutal. One good logical qubit costs on the order of a thousand physical qubits at meaningful code distances; commercially transformative algorithms — Shor-scale factoring, deep chemistry simulation — want hundreds to thousands of logical qubits plus the ability to execute trillions of operations with magic-state distillation overheads on top. Willow's ~100 physical qubits demonstrate the principle. The destination is three to four orders of magnitude away in scale, plus formidable work in real-time decoding, wiring, and cryogenic I/O.

Willow proved the staircase exists. It did not climb it.

IBM's different bet

IBM's Heron line embodies a complementary thesis: rather than maximizing qubits on one die, build moderately sized, high-fidelity chips with tunable couplers, then scale by linking them — classical links first, quantum interconnects on the roadmap — under an architecture that pairs quantum processors tightly with classical compute for error mitigation and, increasingly, error correction with efficient qLDPC codes rather than vanilla surface codes. The qLDPC direction matters because those codes promise dramatically lower physical-per-logical overhead, attacking exactly the brutal arithmetic above.

Strategically: Google demonstrated the textbook path works; IBM is wagering a cheaper path exists. For timeline forecasting, you want both to succeed — they de-risk different segments of the road.

What strategists should do with this

  • Update the cryptography clock, soberly. Below-threshold demonstrations strengthen, not change, the post-quantum migration case. Harvest-now-decrypt-later was already the rational threat model; your PQC inventory and migration plan shouldn't have been waiting on hardware news anyway.
  • Track logical metrics only. Logical error rate, logical qubit count, and decoder latency are the numbers that move timelines. Physical qubit counts stopped being informative years ago.
  • Expect a logical-qubit era before a useful era. The next several years will feature systems with tens of logical qubits — profound scientifically, narrow commercially. Budget attention accordingly: a quarterly tracking habit, not a procurement line.

The honest summary: error correction graduated from theory to engineering, and engineering problems have a way of yielding to capital and iteration. The fault-tolerant era now has a visible on-ramp. It remains a long ramp — and the organizations that benefit first will be the ones who spent the interim building evaluation muscle, not collecting press releases.

Ship AI that earns its place in production.

Tell us what you're building. We'll tell you, candidly, how we'd build it — architecture, timeline, and cost.

Average first response: under 24 hours · straight engineering answers, no pitch theatre