It's crazy what results PMs can get with ChatGPT-4o.
But just a few write good prompts.
(1/7)🧵
(2/7)
The 9 most powerful techniques:
1. Communicate the Why 2. Explain the strategic context 3. Clearly state your objectives 4. Specify the key results (desired outcomes) 5. Provide an example or template
(3/7)
6. Apply the thinking hats technique 7. Set constraints and limitations 8. Provide step-by-step instructions 9. Explain a specific technique (the Internet is often wrong)
(4/7)
Top high-ROI use cases:
1. Get new product ideas 2. Identify hidden assumptions 3. Plan the right experiments 4. Summarize a customer interview 5. Summarize a meeting
(5/7)
6. Social listening (sentiment analysis) 7. Write user stories 8. Generate SQL queries for data analysis 9. Get help with PRD and other templates
(6/7)
The most important advice?
Experiment. If the first response isn't what you need, give constructive feedback and try again.
Ultimately, you end up with a set of custom, validated prompt templates.
The results might not be perfect, but they do 80% of the job. And let you focus on what matters most.
(7/7)
That's a wrap.
Enjoy this?
1. Follow me @PawelHuryn for more of these 2. RT the thread to share it with your friends
A Product Trio is a fundamental concept for product teams.
But contrary to what many believe, it is not:
- A framework to follow
- A strictly defined set of roles
- An exclusive group that performs product discovery alone
Three pieces of advice:
🧵
1. Reject working in silos
You do not want silos in your Product Trio. Product Discovery is teamwork.
I loved insights from "Lean UX," in which Jeff Gothelf and Josh Seiden argue that while everyone has a core competency, allowing others to contribute in any area results in more engaged, more effective teams.
"Silos are the death of collaborative teams." - Lean UX
A picture is worth a thousand words: OKRs vs. KPIs vs. Metrics
When comparing OKRs and KPIs, many forget a critical aspect - the relationships between them.
In short, the Key Results in the OKR always refer to quantitative metrics, some of which might be KPIs.
Let's dive into more details.
1. What are OKRs?
OKR stands for “Objectives and Key Results.” The 2 components:
- Objective (What, When): A qualitative, inspirational, time-bound goal for a team to focus on. Typically set quarterly.
- Key Results (What): Quantitative metrics (typically three) that monitor progress towards the Objective.
OKRs are about:
- Setting a single, inspiring goal.
- Empowering a team to determine the optimal way to achieve it.
- Continuously monitoring the progress, learning from failures, and improving.
Top 29 free PM templates that will make PM a breeze:
Product Discovery:
- Customer Interview (PPTX)
- User Persona (PPTX)
- User Journey Map (PPTX)
- Opportunity Score: Introduction (PDF)
- Opportunity Score: The official Dan Olsen's template (PPTX)
- Jobs-to-be-Done Opportunity Score calculation (XLSX)
- 5-Day Design Sprint: The only official template (Miro)
- Opportunity Solution Tree (Miro)
- Acquisition: How do users find you?
- Activation: How do they experience value?
- Retention: Do they stay with you?
- Revenue: How do you make money?
- Referrals: Do they tell others about your product?
- Engagement: How do they interact with your product?
🧵
This list is based on the AARRR framework. It is universal and fits every organization that works on customer-facing tech products.
---
Remember, you don't need to track everything.
Instead, focus on just a few key metrics that matter the most.
Download now:
- The Ultimate List of Product Metrics (Google Drive):