What an MVP Really Means
An MVP is the smallest useful test of value or risk.
It does not have to be a shrunken final product. It might be:
<ul>
<li>a clickable prototype</li>
<li>a concierge service</li>
<li>a fake-door test</li>
<li>a manual back-end process</li>
<li>a narrow slice for one segment</li>
</ul>
The goal is learning, not impressing everyone at once.

You want to test whether teams value automated weekly reports. Which option is the best MVP?

An MVP should include every feature users might expect in the final product.

Choose the Experiment for the Risk
Different risks call for different tests:
<ul>
<li>Desirability: do users care enough?</li>
<li>Usability: can they understand and use it?</li>
<li>Feasibility: can we technically make it work?</li>
<li>Viability: does it help the business?</li>
</ul>
The right experiment targets the biggest remaining uncertainty first.

If your biggest risk is whether users understand a workflow, what is the best experiment?

A good experiment defines success criteria before it starts.

What Makes an Experiment Actionable
A useful experiment has:
<ul>
<li>a clear hypothesis</li>
<li>a defined audience</li>
<li>a measurable success threshold</li>
<li>a decision rule for what happens next</li>
</ul>
Without that, teams often “learn” just enough to justify whatever they already wanted to build.

Which experiment plan is most actionable?