Capital CasebookMarket Wizards

All analyses

A system includes its operator

Examine the interaction between rules and the person using them.

Open the interactive lesson & exercises ↗

Illustration for: A system includes its operator
Conceptual illustration · not a historical photograph or market data

The systematic trader

Seykota’s interview combines trend-following ideas, risk limits and provocative observations about behaviour. A written system is only part of the real system: the person may override signals, change size or stop following it after discomfort. The implemented process can therefore differ sharply from the one described on paper.

Our interpretation asks what the process rewards in practice. Does it encourage careful observation, or excitement and frequent action? This is a review of incentives, not a diagnosis of hidden motives. Compare intended rules with recorded decisions, including overrides that happened to make money. If discretion is part of the method, define it rather than hiding it.

Worked example

A fictional model records +8 units; discretionary overrides add −5 and costs subtract 2. Implemented result is +1. Reporting only +8 describes a model, not the actual process.

Limits

The claim that people get what they want from markets is a provocative opinion, not proof that losses are desired. Do not generalise its psychological anecdotes into medical or personal diagnoses.

Case connection

The crash adds an external dependency: even perfect rule-following needs workable execution. A complete system includes both human behaviour and market conditions.

Black Monday: when exits become crowded

A risk-control rule can look sensible in isolation and become dangerous when many portfolios act on it together.

The documented sequence

On 19 October 1987, the Dow Jones Industrial Average fell 22.6% in one session. Federal Reserve History describes international selling pressure, market-structure weaknesses and portfolio-insurance strategies that amplified selling as prices fell. The next day, the Federal Reserve affirmed its readiness to provide liquidity. The episode also encouraged the development of trading pauses. These are selected facts, not a claim that one mechanism explains the entire crash. [1]

Interpretation: protection is a process

A dynamic hedge changes exposure as market conditions change. Unlike a contractual payout from a solvent counterparty, it may depend on completing transactions. If a rule requires selling more after a decline, the protection depends on finding buyers at usable prices. At portfolio level, reducing exposure appears defensive. At system level, simultaneous defensive selling can consume the very liquidity that the defence assumes. That distinction is a mechanism to examine, not a reason to reject every hedge or every systematic strategy.

Why a stop is not a price guarantee

The lesson for the interviews is about the gap between intention and execution. An exit level expresses a decision. It does not create a buyer, remove a queue or guarantee the next available price. In a hypothetical market with a last trade at 100 and the next executable bid at 85, a sell instruction triggered below 95 cannot manufacture a fill at 95. A limit order changes the problem by constraining price, but may not execute. Neither order type abolishes the trade-off.

A decision before the event

Suppose a fictional learner has a model that behaves well on ordinary daily data. Before accepting its reassuring results, the learner asks whether several positions need the same exit, whether the model allows trading interruptions, and whether execution costs increase during stress. These questions do not require predicting a specific crash date. They test dependencies. A strategy that cannot tolerate the model being wrong about liquidity has a different risk profile from one with spare capacity and smaller exposure.

Connect the interviews without flattening them

Schwartz emphasises accepting a mistake instead of defending pride. Dennis highlights the danger of judging a process by a few trades. Jones discusses changing exposure and revising a view when expected action fails to appear. Seykota draws attention to the relationship between rules and the person following them. Black Monday lets us ask each a different question: can you act, will you follow the plan, when should the plan be reviewed, and what market conditions does the plan quietly require?

Uncertainty and the wrong takeaway

A common misunderstanding is that one famous crash proves all computerised trading is harmful, or that a discretionary trader would necessarily have escaped. The cited history identifies several contributors; it does not supply a controlled experiment that ranks every possible strategy. Equally, a crisis response by a central bank is not a commitment that a future position will be rescued. Learning from an event means extracting a testable vulnerability without turning the ending into a universal law.

The memorable lesson

Write an execution assumption beside every risk rule. “Exit at the threshold” should prompt “under what trading conditions, at what possible cost, and with what remaining exposure?” This does not eliminate uncertainty. It makes it visible early enough to shape the scale of a hypothetical experiment. The best review examines both the intended decision and the practical ability to carry it out.

Consider

What would remain exposed if your preferred exit could not execute immediately?

Analysis guide

List the position, shared liquidity dependencies and delay. Consider a smaller starting exposure or pre-funded buffer in a hypothetical plan. Do not assume a different order type guarantees both execution and price.

Federal Reserve History · Stock Market Crash of 1987

Reflection

What does your routine reward besides the stated goal?