Everything that is actually possible. Nothing that isn't.
Operations research is the mathematics of deciding well when you cannot have everything. It routed your parcel, staffed tonight's hospital shift, and priced your flight twice while you were looking at it, and it is the field quantum computing is most often accused of being about to revolutionise. This is a course in it, from the top.
1. You have a decision to make, and you can't do everything. There are limits on time, money, people, trucks, machines, beds.
2. Write the limits down as inequalities. The set of choices that satisfy all of them at once is the feasible region. Everything outside it is fantasy.
3. Write down what "good" means as a single number to push up or down. That's the objective.
4. Operations research finds the best point in that region, and proves that nothing better exists.
That last clause is the part people miss, and it is the entire reason the field matters. A heuristic gives you an answer. OR gives you an answer plus a certificate that no better answer exists.
The first is that it already decides your day. This is not a niche academic discipline. It is the quiet infrastructure layer under logistics, energy, healthcare, manufacturing and finance, and it has been running there since the 1940s. Which route, which shift, which price, which warehouse, which power station at 6pm: all of it is somebody's objective function.
The second is that you cannot judge a quantum claim without it. When somebody says a quantum computer will "solve optimisation problems no classical computer can touch", this is the field they are making a claim about. You cannot evaluate that (you cannot even understand what is being asserted) without knowing what classical optimisation already does, how fast it already is, and where it genuinely struggles. Most quantum-optimisation hype survives entirely on the reader not knowing that a good solver will chew through a model with hundreds of thousands of variables before lunch.
So the honest order is: learn what the classical machinery does first. Then the quantum question becomes answerable instead of atmospheric. That is what this page is for, and why it sits beside the quantum material rather than inside it.
Start with what a feasible region is (topic 01) and why the best point of a linear problem sits at one of its corners (02). Topic 16 is the algorithm that walks from corner to corner to find it, topic 03 shows that every such problem has a mirror problem whose answer is the price of each limit, and topic 17 lets the objective curve, ending at Goemans–Williamson's semidefinite relaxation of Max-Cut, the classical result that QAOA on the quantum side has to beat. Turn six of these shapes over in 3D →
Integer programming (topic 04) is where the corner theorem stops being enough, and branch and bound (05) is the machinery that copes. Topic 19 shares this course's language of variables and constraints but drops the objective: sometimes the honest question is not “what's best” but “does anything work at all.” Topic 21 asks when the simplest rule of thumb is provably good enough, and topic 10 is what you reach for once exact methods die.
Network flow and min-cut (topic 06), its special case the transportation problem (18), which keeps only two flat layers of nodes, matching and assignment (07), and shortest paths with dynamic programming (08): the structure real shipping, scheduling and routing problems have.
Topic 08 solved the shortest path under a quiet assumption: choosing an edge means taking it. Topic 20 removes that assumption on the same network, and topic 22 removes the assumption that the numbers are known before you commit; the two honest ways to cope (average over what might happen, or armour against the worst of it) give different answers on the same problem. Topic 09 is the mathematics of waiting when arrivals and service are random.
Topic 23 keeps one decision-maker but gives them several objectives that genuinely conflict, so “optimal” stops being a point and becomes a curve. Game theory (topics 11 to 15) drops the other assumption: when another party is also choosing in response to you, your best plan depends on theirs and there is no single answer to compute, only an equilibrium to find. It underwrites markets that clear through auctions, security proofs written as games between an adversary and a defender, and populations that settle into stable mixes of strategy.
Topics 11 to 15 asked who gains when several players choose. These nine go further: what changes when the moves come in turns (25), when players hold secrets (26), when they meet again (27), when they learn as they go (28), when a shared signal is allowed (29), when each chooses a route (30), when the question is how hard an equilibrium is to find (31), the one place where quantum physics changes a game's value (32), and then a market you design and attack yourself (33).
The course closes on the oldest applied problem in the field, the one Ford Whitman Harris wrote a formula for in 1913, and shows how many of the threads of this course meet inside a warehouse.
Neither can be won by feel. Both were built the way everything else here is: the answer was computed offline in exact arithmetic first, and the game only ever reports what that arithmetic says. Par is a proven number in both, but it means different things: in The Bottleneck it is the best score reachable, found by enumerating every purchase sequence, so you can hit it. In The Prune it is a floor (the count of branches that no strategy on earth could safely skip) and on the larger levels it is provably out of reach, which is why those levels are cleared against a measured target instead.
Game one · topic 03, made expensive
You have inherited a plant that is short of everything, and a board that will fund exactly one upgrade a quarter.
Game two · topic 05, at full scale
Four thousand and ninety-six possible hauls. You will look at about thirty-five, and prove the rest cannot win.
The question has no answer in the abstract and a perfectly good one on a named instance. So here is a named instance (the same crates you just loaded) attacked five ways, with the column that almost every comparison leaves out: what each method can actually prove when it stops.
That column is the whole argument. A number without a certificate is a claim. Four of these five finish holding a claim, and one of the four is the quantum one.
The Verdict · five methods, one problem
This table computes itself in your browser. It needs JavaScript.
Watch what happens as you move up the instances. On the first two, Grover’s query count sits below branch and bound’s node count, 6 against 14, then 18 against 27. Quantum genuinely wins those rows and the table says so plainly. The verdict flips at the third, where 50 queries meets 31 nodes, and by the fourth it is 201 against 29. Greedy, meanwhile, goes from exactly optimal to 23 short, and annealing stops without ever knowing which of those two it did.
It flips because the problem acquired structure, not because the quantum method got worse. Grover is doing precisely what it always does, and that is the point. Its speedup is quadratic but still exponential, and identical whether the haystack is a knapsack or pure noise, because it never reads the structure. The bound is made of that structure, so it barely grows at all.
This is the honest shape of nearly every quantum-optimisation claim you will read: true on an instance small enough that you did not need a quantum computer, and untested at the size where you would.
These are not analogies. Each is a place where the same mathematics is load-bearing on both sides.
Nearly every combinatorial problem can be rewritten as minimising Σ wij si sj over spins of ±1: the ground state of a magnet (Lucas, 2014). This is the format quantum annealers and QAOA actually consume, so it is the doorway every quantum optimisation claim has to walk through. Constraint satisfaction (topic 19) is a standing source of these instances: each violated constraint becomes an energy penalty, so satisfying every constraint becomes finding the ground state. It is also the format three real classical hardware families now consume directly: coupled oscillators, coupled lasers, and fluctuating bits, engineered to settle into that same ground state.
Play it. Graph City → Can classical hardware actually do this? →Simulated annealing is the classical baseline that quantum annealing imitates. Knowing how well the classical version does is the only way to judge whether the quantum one is beating anything. See topic 10.
Play it. The Annealing Volcano →The best one, and almost nobody says it out loud: a quantum computer's error correction runs in real time because of an operations research algorithm. Decoding the surface code is minimum-weight perfect matching. Edmonds, 1965. See topic 07.
Play it: the Decoder Duel →Every post-quantum security proof on this site is stated as a game between a challenger and an adversary: exactly topic 12's minimax framing, used in earnest. "Secure" means no adversary's winning probability can be pushed above a negligible bound, whatever strategy they run.
See it on the PQC pages →The sharpest bridge of the five, because it is a head-to-head. Goemans–Williamson's SDP relaxation of Max-Cut (topic 17) proves an unconditional 0.878567 for a classical polynomial-time algorithm. QAOA was introduced on the same problem, and at its shallowest depth its own authors' bound sits below that number, not above it, with a later result showing a simple classical algorithm still matching or beating it one depth up. This is the honest, checkable version of "can quantum beat classical at optimisation", not the atmospheric one.
See it worked through: topic 17 →Historically neither. It began in pre-war Britain in 1937, when a group of scientists was asked not to improve radar but to work out how to use it well, and it expanded enormously once the war started two years later. It kept the habit of starting from a real operation rather than from a theorem. Today it overlaps heavily with combinatorial optimisation in computer science and with parts of economics and statistics, and the boundaries are not worth policing.
No, and the distinction is useful. Machine learning mostly predicts: given data, what will happen? OR mostly decides: given what will happen, what should we do about it, subject to what we cannot change? Real systems chain them: forecast demand with ML, then decide inventory with OR. Topic 08 is where the two genuinely meet.
Topics 01–10 all assume one decision-maker facing fixed limits: a machine-hour cap, a network, a queue. However hard the problem, there is one objective to optimise and the world does not react to your choice. Game theory (topics 11–15) is what you need the moment a second decision-maker is also choosing, in response to you: your best move now depends on theirs, which depends on yours, and there is no longer a single number to compute: only an equilibrium to find, a value to guarantee, or a fair split to prove unique.
Not on any evidence currently available. Quantum optimisation is real research and worth watching, but there is no known quantum algorithm that beats a strong classical solver on a problem anyone actually needs solved, and the quadratic speedup that is proven for unstructured search does not apply to the structured problems where classical methods do their best work, as topic 05 shows. Anyone telling you otherwise should be asked for the resource estimate.
To understand the pictures and intuitions in this course, no: school algebra is genuinely enough, which is why every topic leads with a drawing. To write models professionally you need linear algebra and comfort with proofs. To invent new algorithms, considerably more. The first step is much smaller than people expect.