Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Part of the The Bayesian Investor — A Primer for the CIO series.

Phase 2 — Core Modeling: From Coin Flips to Real Decisions

Coin flips are the sandbox. Now the team climbs out of it and builds models that describe real markets. This is the phase where they work through the Bayesian Analysis with Python material and its companion repository — the practical playbook of this discipline.

What a “model” is, in plain words

A model is a simplified story of how the world produces the numbers you observe. It is not the world. It is a flight simulator — not the actual plane, but a careful imitation that predicts how the plane behaves. Every investment team already runs models in their heads (“if rates rise, cap rates follow, so property values compress”). The difference here is that your team will learn to write those stories down with precision, so the computer can play them forward, test them, and tell you how confident the story makes you.

Every model has parameters — the dials or settings of the story. If the story is “property value depends on interest rates and income,” then the dials are things like “how strongly does each factor move the value?” Estimating means using the evidence to find the best settings for those dials, with an honest statement of how sure you are about each one.

Sampling, and why it’s not cheating

Here is the crucial move that makes modern Bayesian work possible, and it’s worth dwelling on because it is the single most misunderstood idea in the whole roadmap.

To know what your model believes, you could try to compute the answer with pure mathematics — but for real-world models that math is usually impossibly hard. So instead, your team does something almost cheeky: they sample — that is, they draw possible outcomes at random from the model, the way rolling a die over and over lets you feel its odds without calculating them. Draw enough samples and the picture emerges: the distribution — the full chart of possible outcomes and how likely each is — reveals itself from the frequencies of the draws.

Think of it as estimating the shape of a mountain range by taking thousands of random hikes and recording where you end up, rather than trying to derive the mountain’s shape from a surveyor’s formula. It sounds crude. It is not crude; it is a recognized, rigorous, and powerful technique — and it works precisely because randomness, repeated enough times, stops being random and becomes a reliable portrait of the underlying pattern.

The hiker in the fog: MCMC

The specific sampling technique your team will master is called MCMC (Markov chain Monte Carlo). Let’s unpack that awful acronym gently, because the idea behind it is actually lovely.

Imagine a hiker lost in a foggy landscape. She cannot see the whole terrain — the mountain peaks, the valleys, the shape of everything. She can only feel the ground directly under her feet. Her goal: figure out where the high ground is (where the likely answers live) and how much of the terrain is high vs. low. Her method: take a step in a random direction. If the ground rises, take the step — always. If the ground falls, take the step sometimes — because a dip might be a valley between two peaks, and crossing it could lead to even higher ground. Over thousands of steps, she spends time on each part of the landscape in proportion to how high it is. That visiting pattern is the answer.

MCMC is exactly this hiker. It explores the landscape of possible dial settings, spending time where the answer is most likely, and in doing so it produces a complete map of what the model believes — including all the uncertainty. The three letters just describe the hiking rules: it walks a chain of steps where each step depends only on where it currently stands (Markov), and it uses random draws (Monte Carlo, named after the casino — because it gambles its way to the answer). For an investor, the practical meaning is: your team can get a full, honest picture of what the data and the model together imply — without needing a single closed-form formula.

The committee vs. the organization: hierarchical models

The next big concept is the hierarchical model, and the analogy is organizational.

Imagine a firm with many small regional offices, each managing a handful of properties or a handful of positions. Each office has very little data on its own. A naive analyst in one office might conclude “with only five data points, I can’t estimate our vacancy risk at all.” But here’s the insight: these offices are not isolated islands. They share the same economy, the same market forces, the same broad dynamics.

A hierarchical model says: let every office learn from the whole firm, and let the whole firm learn from every office. Each office still gets its own tailored estimate — Boston isn’t forced to be identical to Houston — but it is gently pulled toward the firm-wide pattern, with the strength of that pull proportional to how little local data it has. When an office has lots of data, it stands on its own. When it has almost none, it leans on the firm.

Why this matters for a CIO: it’s the principled version of “borrowing strength.” Small samples no longer mean guesswork. A portfolio of many small exposures becomes a source of shared wisdom, not a collection of lonely estimates. This is how you get defensible numbers out of thin slices of data — and in commercial real estate, where individual deals are few and idiosyncratic, that is most of the job.

Drawing the line: regression

The team will also master regression — a word that sounds technical and means something simple. Regression is drawing the best-fitting line through history. If you plot historical data points — say, interest rates against cap rates — regression finds the straight line that comes as close as possible to all the points at once, and it draws a shaded band around that line showing how confident it is.

The line is the trend; the band is the honesty. A tight band means the relationship is clear and the forecast is trustworthy. A wide band means the data is scattered and the forecast should be treated as a guess. For a decision-maker, never look at the line without looking at the band.

The payoff: separating skill from luck

The finance application your team will build in this phase is the alpha/beta model, and it deserves a plain explanation because it’s genuinely important.

Think of any portfolio’s return as a coin with two sides. One side is beta — the part of your return that simply comes from the market moving. If the market rises and you’re invested, you rise with it; that’s not skill, that’s exposure. The other side is alpha — the part of your return that comes from your decisions, over and above what the market gave you for free.

The question every investor must answer honestly: did we add value, or did the market just go up? A naive analysis can fool itself, especially in a bull market. The Bayesian version separates the two cleanly, and — this is the key — it puts an honest uncertainty band around the answer. “Your alpha is positive” is one thing. “Your alpha is positive, but the band is wide enough that we can’t actually be sure” is a completely different, and far more valuable, sentence. This phase gives your team the ability to deliver the second kind of sentence.