Run the smallest test that can answer the question

Shrink your experiment so the feedback cycle is fast and the cost of being wrong is low.

Why it works

Large, elaborate plans have long feedback cycles and high emotional investment, both of which make it costly to admit the approach is not working. A minimum viable test deliberately limits scope so that the result arrives quickly, revision is cheap, and attachment to the method stays low enough to allow honest evaluation. The iterative power of PDSA lives entirely in cycle speed.

How to do it

1. Identify the single most important question your plan needs to answer.
2. Design the smallest action that can generate a usable answer to that question.
3. Run it in a real context but with low stakes — a conversation, a day, a draft, not a month-long commitment.

Evidence

Rapid experimentation and shortened feedback loops are central to validated improvement methodologies (Agile, Lean, PDSA); the principle that fast cycles beat large bets is consistent across organizational and individual learning research. (mechanistic)

Most direct evidence is from organizational contexts; transferability to personal skill-building is principled rather than independently trialed.

Common mistake

Over-engineering the plan phase until the "test" is really a full-scale launch — which makes abandoning it feel like failure rather than learning.