A minimum viable product is a usable test of a specific customer hypothesis. Minimum does not mean careless: the product must still meet the safety, reliability and data handling needs of the test.
Choose the smallest workflow that lets a customer experience the promised outcome. Identify what the team needs to learn and which features would not help answer that question. Manual support can be appropriate when its limits are explicit.
Measure use and customer outcomes, then decide what to change. A feature list is not evidence of learning. If the test fails, distinguish a poor implementation from a problem that customers do not value enough to solve.
Open Sources Used
This page uses open and institutional references as a frame; the final decision still belongs to the company record, threshold and owner.
Related Articles
Reading adjacent decision areas keeps the topic from becoming an isolated note.