Act as a Product Manager

Original Prompt

Please acknowledge my following request. Please respond to me as a product manager. I will ask for subject, and you will help me writing a PRD for it with these headers: Subject, Introduction, Problem Statement, Goals and Objectives, User Stories, Technical requirements, Benefits, KPIs, Development Risks, Conclusion. Do not write any PRD until I ask for one on a specific subject, feature, or development.

Analysis

Strengths

1. Structured Approach: The prompt clearly defines the structure of the PRD, ensuring a comprehensive and organized document.
2. Clarity of Role: It specifies the desired role (Product Manager), which helps in contextualizing the responses.
3. Sequential Process: The instruction to wait for a specific subject before writing allows for focused and relevant output.

Weaknesses

1. Lack of Specificity: The prompt does not specify the type of product or market, which could lead to generic responses.
2. Missing Context: It doesn't provide information about the target audience or stakeholders, which are crucial for crafting relevant user stories and technical requirements.
3. No Examples Provided: There are no examples of subjects or features to guide the conversation, which might hinder creativity and clarity.

Suggested Improvements

To enhance the prompt, I would focus on adding context and specificity, as well as encouraging ongoing dialogue. Here’s an extended version:

Extended Prompt

Please acknowledge my following request. Please respond to me as a product manager for a [specific product type or market]. I will provide a subject, and you will help me write a PRD for it with these headers: Subject, Introduction, Problem Statement, Goals and Objectives, User Stories, Technical Requirements, Benefits, KPIs, Development Risks, and Conclusion. After providing the PRD, please suggest potential follow-up questions or areas of exploration to refine the document further. Do not write any PRD until I ask for one on a specific subject, feature, or development.

Continuing the Conversation

If the user uses this prompt, they can continue the conversation effectively by:

1. Providing Specific Subjects: Clearly stating the feature or product they want to develop can help tailor the PRD more closely to their needs.

   Example: "Let's write a PRD for a new user onboarding feature for a mobile app."

2. Asking Clarifying Questions: Users can seek more details on sections of the PRD, like, "What KPIs should I consider for measuring success?"

3. Requesting Iterations: After receiving an initial draft, they could ask for revisions based on feedback or new insights, e.g., "Can you adjust the user stories based on our target audience's feedback?"