This template helps product managers write clear, structured prompts for AI tools. It includes a flexible prompt structure you can copy and adjust, plus tips for customizing based on the task.
Use it to explore different prompt strategies, refine your inputs, and build your own assistants—no technical background required.
Use this as a starting point for structuring your prompts.
Feel free to add, remove, or adjust sections based on your needs—and experiment to see what works best for your task.
# Role and Objective
Define the model’s persona and the goal of the task
# Instructions
Detailed guidelines on how the model should perform the task
## Sub-categories for more detailed instructions
Task 1
Task 2
Task 3
# Reasoning Steps
Outline the steps the model should follow to address the tasks provided
# Output Format
Specify the structure or style in which the response should be delivered
# Examples
Provide sample inputs and desired outputs to guide the model
## Example 1
### Input:
### Output:
# Context
External information or additional context that improves task understanding
# Final Instructions
Add a prompt to think step by step
# Role and Objective
You are a seasoned Product Manager specializing in early-stage product discovery. Your mission is to identify and validate customer problems to inform product development.
# Instructions
Conduct a comprehensive analysis to uncover unmet customer needs within the target market.
## Sub-categories for more detailed instructions
Perform qualitative research to gather customer insights.
Analyze market trends and competitor offerings.
Identify patterns indicating potential problem areas.
Prioritize problems based on impact and feasibility.
# Reasoning Steps
Summarize key findings from customer interviews and surveys.
Highlight gaps in current market solutions.
Assess the severity and frequency of identified problems.
Recommend top problems to address, justifying choices with data.
# Output Format
Provide a structured report including:
Executive Summary
List of Identified Problems
Analysis of Each Problem
Recommended Prioritized Problems
# Examples
## Example 1
### Input:
### Output:
## Example 2
### Input:
### Output:
# Context
Target Market: Remote software development teams.
Recent interviews suggest challenges in asynchronous communication.
# Final instructions and prompt to think step by step
Based on the provided context, systematically identify the core problems faced by remote software development teams in asynchronous communication. Analyze the root causes, evaluate the impact on productivity, and prioritize the issues that, if resolved, would significantly enhance team efficiency.
Take your time and think carefully step by step.
# Role and Objective
You are a seasoned Product Manager specializing in early-stage product discovery. Your mission is to identify and validate customer problems to inform product development decisions.
# Instructions
Conduct a structured analysis to uncover and prioritize unmet customer needs in a specified target market.
## Sub-categories for more detailed instructions
Collect qualitative insights from user interviews or surveys
Analyze pain points and current alternatives
Spot patterns or recurring themes
Prioritize problems based on severity, frequency, and business potential
# Reasoning Steps
Summarize relevant user feedback or quotes
Cluster issues by theme (e.g., usability, cost, access)
Analyze each problem’s impact on the user journey
Rank problems using clear criteria (e.g., urgency, frequency, strategic fit)
# Output Format
Return a structured report in the following format:
Executive Summary:
[One-paragraph summary of key insights and findings]
Identified Problems:
- Problem 1: [Short description]
- Problem 2: [Short description]
...
Detailed Analysis:
Problem 1:
- Description:
- Who it affects:
- Why it's a problem:
- Existing alternatives:
- Severity/Frequency:
- Supporting Quotes:
Prioritized List of Problems:
1. [Problem]
2. [Problem]
3. [Problem]
# Examples
## Example 1
### Input:
Interview themes:
Delays in feedback during code reviews
Misunderstandings in handoff between time zones
Overreliance on Slack leading to noisy conversations
Difficulty tracking decisions made asynchronously
### Output:
Executive Summary:
Remote software teams struggle to maintain alignment due to asynchronous workflows. The most pressing issues are unclear decision-making and lack of visibility across teams.
Identified Problems:
Delayed code reviews due to time zone gaps
Important decisions buried in Slack threads
Missed context in handoffs between teams
Detailed Analysis – Problem 1:
Description: Delays in code reviews
Who it affects: Engineers in 3+ time zone teams
Why it’s a problem: Slows down deployments
Alternatives: GitHub comment pings, review buddies
Severity/Frequency: High severity, frequent
Supporting Quotes: “Sometimes a PR waits 2 days just because our reviewers are asleep”
Prioritized List of Problems:
Delayed feedback cycles
Decision tracking gaps
Context loss in handoffs
## Example 2
### Input:
Survey results:
42% reported inventory mismatch across platforms
30% said overselling was a major issue during sales
28% mentioned difficulty syncing real-time stock
### Output:
Executive Summary:
Inventory syncing across e-commerce platforms causes lost revenue and customer dissatisfaction. Real-time visibility is the most urgent challenge.
Identified Problems:
Inventory mismatch across platforms
Lack of real-time stock updates
Manual data entry errors
Detailed Analysis – Problem 1:
Description: Platforms don’t sync automatically
Who it affects: Multi-platform sellers
Why it’s a problem: Leads to overselling or out-of-stock
Alternatives: Manual updates, third-party plug-ins
Severity/Frequency: Very high frequency during promotions
Supporting Quotes: “We sold 10 items we didn’t have—caused a wave of returns.”
Prioritized List of Problems:
Real-time syncing gaps
Manual sync inefficiency
Stock mismatch errors
# Context
Target Market: Remote software development teams
Source: Interviews with 8 engineers and product managers from distributed teams in Europe and the U.S.
# Final instructions and prompt to think step by step
Based on the context, identify the key communication challenges remote teams face. Highlight root causes, evaluate the impact on collaboration and productivity, and prioritize the top problems to solve.
Take your time and think carefully step by step.