What it corrects
Experience is not automatically a teacher. In a kind environment, the rules are stable, the same patterns recur, and feedback arrives quickly and clearly. A chess move is followed by a visible position; repeated games make the signal hard to miss.
Business is often wicked. Important decisions are rare, results arrive years later, competitors react, and luck can make a poor process look brilliant. The team may receive confident feedback from an outcome that cannot distinguish its strategy from timing, selection, or chance.
The distinction stops a case study from becoming a recipe. A result is evidence, but first ask what that environment was capable of teaching.
How it works
- Name the feedback the decision will produce and when it will arrive.
- Ask whether the same decision can be repeated under comparable conditions.
- Separate signals caused by the choice from luck, selection, and delayed effects.
- Build a smaller, earlier feedback loop when the natural one is too wicked.
In a Business Case Weekly case
In the Nike case, the eventual success of an own-brand strategy cannot prove that every earlier step was sound. Supplier behaviour, demand, financing, and timing all shaped the result. A better learning design would test repeat demand, unit economics, and supplier dependence separately before the full outcome arrives.
In your answer
- “The first useful feedback is … and it arrives by …”
- “That result cannot distinguish our strategy from …”
- “To learn earlier, I would repeat or isolate …”
Common misuse
Do not label all business feedback wicked and give up on learning. The method is a design prompt. Even when the final outcome is noisy, teams can create kinder sub-environments: staged rollouts, repeated customer cohorts, pre-declared forecasts, matched comparisons, and review dates. The goal is not perfect certainty; it is feedback that makes one hypothesis more credible and another less credible.