Prompt

Outline the essential features for the MVP (Minimum Viable Product) of [PRODUCT CONCEPT]. Focus on the features that deliver the core value to users and address the primary problem [PRODUCT] solves. For each feature, provide a brief description and justify why it’s needed in the MVP. Indicate the priority or importance of each feature (e.g., must-have vs nice-to-have) and, if possible, note an estimate of the effort or complexity to implement. Ensure the feature set is lean – include only what’s necessary to learn from early users and validate the concept.

How to Use

1. Define Your Inputs: Write down a short description of your product concept, including its main goal or the problem it addresses. This fills in [PRODUCT CONCEPT]. Also, list any specific functionality you have in mind. For example: “A task management app for freelancers to track time and invoices.” These details help the AI understand the context.

2. Customize the Prompt: Plug your product concept into the prompt. If you already have some features in mind, you can mention them or ask the AI to prioritize among them. Make sure the prompt asks for justification of each feature – this yields reasoning you can use to decide what goes into the MVP. You might also specify how many features to list (e.g., top 5 features) to keep it focused.

3. Optional Add-ons: If you want a structured prioritization, you can instruct the AI to use a framework. For example, ask it to categorize features using the MoSCoW method or RICE scoring for priority. (Optional prompt addition: “Categorize each feature as Must-have, Should-have, or Could-have.”) You could also specify constraints like a development time limit or budget, so the AI considers effort in its suggestions.

4. Run the Prompt: Run the prompt on your AI platform. The AI will generate a list of features with descriptions and rationales. It should identify the critical “must-have” features for launch and possibly some lower-priority ones to exclude for now. Look for mentions of impact on users and implementation effort – the prompt’s wording encourages those factors.

5. Review & Select: Go through the proposed MVP feature list. Check that each feature truly aligns with the core value proposition of your product. The justifications will help you see if a feature is truly essential or if it can be postponed. Pay attention to any effort or complexity estimates; features labeled high complexity but low user impact might be candidates to drop from MVP. Refine the list as needed, possibly combining or rephrasing features. The end goal is a clear, justified MVP scope.

6. Expected Outcome: An outlined MVP feature set consisting of the key features your product needs for its first version. Each feature entry will typically include a title or short name, a description of what it does, and a justification for why it’s included (often referencing user needs or business goals). You’ll also see an indication of priority (e.g., “must-have”) and maybe complexity. For example, the AI might output something like:
   • Feature: User Login & Profile – Must-have. Allows users to save preferences; essential for any personalized functionality. Complexity: Low (standard implementation).
   • Feature: Task Creation & Tracking – Must-have. Core feature for managing tasks, delivers primary value. Complexity: Medium.
   • Feature: Team Collaboration – Could-have. Nice to attract teams but not required for single-user validation. Complexity: High (defer to later).

     This gives you a prioritized blueprint of what to build first.