Question
What does it mean that failed predictions are data not failures?
Quick Answer
When your prediction is wrong you have learned something about where your schema is off.
When your prediction is wrong you have learned something about where your schema is off.
Example: You predict that giving your team more autonomy will increase their output, because your schema says motivated people produce more when unconstrained. Two months later, output has dropped. The instinct is to feel you failed as a manager. But the prediction error is data: your schema was incomplete. It did not account for the fact that this particular team lacked shared context about priorities, so autonomy without alignment produced divergence, not acceleration. The failed prediction did not reveal your incompetence. It revealed a missing variable in your model — and now you know to add it.
Try this: Select a prediction you made in the last six months that turned out wrong. Write it down with as much specificity as you can: what you predicted, what actually happened, and the gap between the two. Now perform a schema autopsy. Do not ask "what did I do wrong?" Ask "what does this prediction error reveal about the model I was using?" Identify the specific assumption, missing variable, or structural flaw in your schema that produced the incorrect prediction. Write a one-paragraph schema update — the revised model that incorporates what the failure taught you. Finally, derive one new testable prediction from the updated schema. This is the full cycle: prediction, error, diagnosis, update, re-prediction.
Learn more in these lessons