Basic Prerequisites: 03 · Robust Formulations and Transaction Costs & Turnover.
1. Intuition & Practical Objective
Robustness does not require uncertainty sets. Two older, blunter, and remarkably effective techniques sit between “naive MVO” and “formal robust optimization”:
- Constraints as robustness. Long-only, weight caps, sector bounds, and turnover limits are the practitioner’s default. They are not cosmetic - they change the geometry of the feasible set so the optimizer can no longer express its extreme opinions. A cap is a hard statement that “no model output, however noisy, justifies a position.”
- Resampling (Michaud). Instead of optimizing one estimated , optimize many resampled versions, then average the resulting weights. The idea (Michaud & Michaud 1998) is that a portfolio averaged over the estimation-error distribution is less brittle than the single “optimal” point.
The practical objective is to know what each actually buys you - and, crucially, what it does not. This page shows, on the shared data, that constraints are the real stabilizer, while naive resampling fails to cure a biased estimate and can even amplify it. That negative result is the honest bridge to the formal robust formulations of 03.
2. Mathematical Ground Truth & Derivations
2.1 The constrained model
The practically-used MVO is a quadratic program over a box (plus simplex):
With it is long-only (no short sales); with a common it caps concentration. This is a convex QP solved by active-set/interior-point methods - every real optimizer since Markowitz uses some version.
Turnover constraint. To control trading cost, add (an ball) - convex, and itself a robustness statement about the path, not just the endpoint (see Transaction Costs & Turnover).
Why constraints help (first principles). Unconstrained MVO’s optimum is . The problem is that this point sits outside any sane region of portfolio space, in the short-saturated tail where estimation error dominates. Clipping the feasible set to the simplex/box removes exactly those directions. The cost is real - Clarke, de Silva & Thorley (2002) quantify it as a transfer coefficient that discounts achievable information ratio () - but the benefit (survival) usually dominates.
2.2 Resampling (Michaud)
Michaud’s procedure:
- Estimate from the sample.
- Draw bootstrap samples of the return history (non-parametric resample, or parametric draws from ).
- Optimize MVO on each; collect the weight vectors .
- Report the average (and/or a resampled efficient frontier in which portfolios are ranked by their resampled risk/reward).
The claim is that is more stable than the single . The subtlety - and where the method is often over-sold - is that step 2 resamples around the same point estimate that is itself biased by the overfit. Averaging over resamples reduces the variance contribution of the frontier, but it does not remove the bias in ; if the center is wrong, all optimizations inherit the wrong center. Goldfarb & Iyengar (2003, §1) make this critique precisely: sampling-based and scenario approaches “do not provide any hard guarantees on the portfolio performance.”
3. Computational Implementation - constraints vs resampling
Same universe. We compare the unconstrained optimum, the long-only box, and the Michaud average, and we measure the dispersion of resampled weights - the quantity resampling is supposed to tame.
Two verified, and deliberately honest, results:
- The constraint is the workhorse. Clipping to the long-only box collapses the short-saturated optimum to a diversified with gross exposure . (Here the cap is not even binding - long-only alone already does the job on this universe.) The robust max-min portfolio of 03 lands in essentially the same place: box-uncertainty and hard caps both act as penalties on large positions.
- Naive resampling does not stabilize the unconstrained problem. The Michaud average has gross exposure - more extreme than the single naive solution (), and the per-draw gross exposure has standard deviation , roaming around a mean of . Resampling from a model centered on an overfit reproduces the overfit in every draw. This is the failure the formal robust formulation is designed to fix, not a bug in the code.
The design lesson. If you are starting from an unreliable center, resampling propagates the unreliability. What actually helps is (a) imposing constraints (drop the extreme feasible directions) and/or (b) shrinking the center toward something stable (shrinkage, Black–Litterman prior, or a robust worst-case set). Resampling is best used on top of those, to build a distribution of portfolios rather than to replace them.
4. Failure Modes & First-Principles Breakdowns
- Constraints are a blunt instrument with a measurable cost. Long-only and caps improve stability but discard information - the transfer coefficient (Clarke, de Silva & Thorley 2002) is exactly how much of your signal the constraints “leak.” Cap too tight and you have simply built with extra steps.
- Resampling is not a cure for a biased estimate. §3 shows it; Goldfarb & Iyengar (2003) state it. Resampling reduces frontier-sampling variance, not input bias. Marketing it as a guarantee is a category error.
- Turnover constraints can hide regime change. A tight turnover budget keeps you glued to a stale portfolio when the world has moved; robustness about inputs is not robustness about regimes.
- Cap asymmetry / hidden concentration. Capping each asset at while leaving correlations free lets the portfolio concentrate in a single risk factor. Caps on weights are not caps on risk - the residual factor exposure must be checked separately (bridge to factor risk models).
5. References
- Michaud, R. & Michaud, R. Efficient Asset Management, 2nd ed., OUP, 2008
- Lobo, Fazel & Boyd (2007), Portfolio Optimization with Linear and Fixed Transaction Costs, Annals of OR 152:341–365
- Clarke, de Silva & Thorley (2002), Portfolio Constraints and the Fundamental Law of Active Management, FAJ 58(5):48–66
- DeMiguel, Garlappi & Uppal (2009), RFS 22(5)
- Goldfarb & Iyengar (2003), Math. of OR 28(1):1–38
- Frost & Savarino (1988), For better performance: constrain portfolio weights, JPM
6. Connected Graph Bridges
- Back: 03 · Robust Formulations
- Method siblings: Transaction Costs & Turnover · Risk Parity & ERC (a constraint-free stabilizer) · HRP (inversion-free)
- Forward: 05 · Failure Modes & Practice · Index Hub