Your first MVP: one customer, one useful finished task

Start with the customer’s finish line

A minimum viable product is a first version built to test whether a useful idea works for a real customer. A shorter feature list helps only if the remaining experience still answers the question you need to test.

• Name one customer and one task before deciding which screens to build.
• Define what the customer should know or receive at the end.
• A clickable prototype can test a risky assumption without fulfilling a real transaction.

For a live pilot, join the customer-facing steps to the people and systems doing the work. This is Infyny’s practical application of the guidance, not a government rule for commercial MVPs.

Worked example: a lunch-preorder pilot

This is a hypothetical startup example, not an Infyny client result. The pilot serves office workers who want to reserve tomorrow’s lunch for collection.

• The customer chooses an available meal and submits the necessary order details.
• The kitchen checks capacity. Until accepted, the interface says received or pending rather than confirmed.
• Acceptance includes the meal, agreed price and collection details. If unavailable, explain the alternative or how to cancel the request.

1. Draw each step from choosing a meal to receiving a decision.
2. Write who owns the stock check and the expected response time.
3. Test a sold-out meal, a repeated submission and a missing confirmation.
4. Observe a consenting pilot user and record the point they needed help.

A team member can perform early operational steps manually. Be clear about that pilot experience and keep appropriate privacy, safety and accessibility provisions. Automation comes after you understand the work.

Decide what to build next

A dashboard, loyalty programme and recommendation engine may become useful. The first pilot should tell you which missing capability blocks the actual customer task.

• Track progress through the journey, not just visits or button clicks.
• Record the issue and the support needed without storing unnecessary personal data.
• Fix the most important observed obstacle, then test again.

The downloadable sheet turns this lesson into a scoped plan; the CSV gives your team a simple place to record real observations. All sample rows are labelled illustrative.

Your MVP readiness checklist

Use this checklist after mapping the journey. Tick an item only when the team can demonstrate it; an unchecked essential needs an owner and a clear fix before the relevant live transaction is accepted.

• Customer and outcome: one named audience, one task and an observable finish line.
• Order and operations: separate pending from accepted; assign each manual step an owner and a response time.
• Failure and learning: test unavailable stock, duplicate requests and failed notifications, then record pilot issues.

1. Walk through a successful order with someone who did not build the product.
2. Repeat the failure cases with the business operator.
3. Write a fix and an owner beside any unchecked essential.

Save the checklist card or use the downloadable checklist alongside the scope sheet and CSV tracker. This is a practical planning aid, not a certification that a product is safe or ready in every respect.