Your cart is empty
Add prompt packs to continue
Boost your career to the next level with the definitive collection of prompts designed specifically for high-performing Product Managers. This strategic arsenal covers everything from deep user discovery to flawless technical execution, allowing you to confidently lead in Big Tech and high-growth startup environments. Optimize your decision-making processes and master the most advanced methodologies in the industry. Each prompt has been structured to generate actionable results in real frameworks such as Continuous Discovery by Teresa Torres, roadmapping in Productboard and advanced analysis in Amplitude. Whether you're preparing for an interview for an L5 position or presenting a Business Case at C-level, this tool provides you with the analytical clarity and narrative precision needed to stand out. Transform your product vision into a measurable, scalable reality today.
100 resources included
Acts as a Senior Technical Product Manager with more than 15 years of experience leading communication between business teams and high-performance software engineering departments. Your objective is to transform an initial product vision into a highly precise technical specification for the development of [Project/Feature Name]. This document should serve as the ultimate bridge to eliminate ambiguities, reduce premature technical debt, and ensure that the proposed architecture supports long-term business objectives. Product and Problem Context: The project focuses on [Detailed Description of the Problem to be solved]. Currently, we have a user base of [User Volume/Estimated Traffic] and we operate under an ecosystem of [Current Technological Stack: E.g. Microservices in Go, Frontend in React, AWS, etc.]. I need you to analyze how this new functionality will impact existing services, identifying possible bottlenecks in the database [DB Type: SQL/NoSQL] and suggesting the best integration strategy (RESTful APIs, Webhooks, Messaging Queues, etc.). Functional and Non-Functional Requirements: Breaks down in detail the technical requirements necessary to comply with [List of Business Objectives]. For each requirement, define technical acceptance criteria (Performance, Latency, Security). Be sure to consider horizontal scalability and critical dependencies with third-party services such as [Third-Party Providers/External APIs]. It is essential that the technical design considers observability from day one, including logging, monitoring and tracing strategies. Edge Case Analysis and Error Handling: Identify at least five complex scenarios or 'edge cases' that could arise during the implementation of [Project Name/Feature], such as network failures, data inconsistency in distributed transactions or unexpected load spikes. For each case, propose a technical mitigation strategy (Circuit Breakers, Retries with Exponential Backoff, Fallbacks) that guarantees the resilience of the system without degrading the end user experience. Definition of Technical KPIs and Implementation Roadmap: Propose a phase structure for technical deployment, prioritizing the development of a functional but robust MVP. Define specific technical success metrics such as [Ex: Response Time < 200ms, Availability 99.9%, Error Rate < 1%]. The final result should be a technical document ready to be reviewed by a Staff Engineer or CTO, providing a clear roadmap for the development team in charge of [Team Name/Squad].
Acts as a Senior Product Manager and UX Researcher expert in product discovery and Jobs-to-be-Done (JTBD) methodologies. Your mission is to design a comprehensive user recruitment protocol to conduct in-depth interviews about the product [Product or Project Name]. The primary goal is to identify users who have recently experienced the 'trigger event' that led them to seek a solution for [Specific Problem or Need]. I need this protocol to guarantee that the people selected not only meet demographic criteria, but also have the emotional and experiential charge necessary to reveal the 'steps of progress' they are trying to achieve. First, define the key informant profile based on JTBD theory. Specify what previous behaviors, current frustrations, and workarounds (indirect competition) these users must have tried before being considered eligible for the study. Detail the inclusion and exclusion criteria rigorously to avoid the bias of 'professional survey users' or people who do not have a real 'pain' to solve in the context of [Context of Use]. Second, build a 'Screener' of 6 to 8 strategic questions. Questions should be largely behavioral, focusing on past actions ('When was the last time you...?') rather than hypothetical preferences. It includes a trick question to filter out inattentive candidates and an open-ended question designed to assess the user's ability to articulate their current workflow in [Area of Interest]. Third, develop a multi-channel recruitment strategy that includes specific contact templates for [Recruitment Channel, ex: LinkedIn, Email, Intercom]. Messages should be brief, empathetic and clearly highlight the value of your participation, mentioning the incentive of [Incentive Type] for a session of [Session Duration] minutes. The tone should be [Communication Tone: e.g. Professional but approachable]. Finally, establish the post-recruitment logistical flow. This should include the automated scheduling process, sending reminders to minimize the 'no-show' rate, and scripting to obtain legal and ethical informed consent before recording begins. The end result should be an operational document that any member of the product team can execute to fill the interview pipeline with high-quality candidates.
Acts as a Senior Product Manager specialized in data analysis and growth strategy. Your mission is to design a comprehensive "Health Indicator Monitoring" system for the product: [Product/Service Name]. This system must not only measure current performance, but also predict deviations that affect the long-term sustainability of the business. To start, define a hierarchy of metrics that includes the 'North Star Metric' specific to [Industry Type/Business Model], followed by critical health metrics (Input Metrics) such as cohort retention rate, segmented Churn Rate, and customer acquisition to lifetime value ratio (LTV:CAC). It is imperative that you identify 'Counter-metrics' to ensure that optimizing a KPI does not degrade user experience or service quality in the [Specific Market Segment] segment. It then translates these health indicators into a framework of OKRs (Objectives and Key Results) for the next quarter. The main Objective should be [Describe Primary Business Objective], and each Key Result should be directly linked to a health metric that we have previously defined. Explains the logic behind each KR and how constant monitoring of this data will allow agile decision-making in the face of anomalies detected in user behavior. Finally, propose an executive dashboard design and an automated alert strategy. The dashboard must categorize the data into three levels: 'Critical Status', 'Under Observation' and 'Optimal'. Detail what visualization tools you would recommend integrating and how to set proactive alert thresholds for the product team when a metric like [Specific Metric] falls below [Percentage Deviation] for more than [Time Period].