George from 🕹️prodmgmt.world
@nurijanian.bsky.social
I help smart Product People expand skills, make smart choices & lead confidently
✨Get My 100+ AI Prompts for Product Work ➡️ http://tiny.cc/100-ai-prompts
get 20% off all my products ➡️ http://tiny.cc/product-bundle
✨Get My 100+ AI Prompts for Product Work ➡️ http://tiny.cc/100-ai-prompts
get 20% off all my products ➡️ http://tiny.cc/product-bundle
Your first product strategy doc isn't about perfection.
It's about structured thinking + stakeholder alignment.
After helping a few of my fellow PMs craft their first strategy, here's the exact process that works 👇
It's about structured thinking + stakeholder alignment.
After helping a few of my fellow PMs craft their first strategy, here's the exact process that works 👇
May 9, 2025 at 12:57 PM
Your first product strategy doc isn't about perfection.
It's about structured thinking + stakeholder alignment.
After helping a few of my fellow PMs craft their first strategy, here's the exact process that works 👇
It's about structured thinking + stakeholder alignment.
After helping a few of my fellow PMs craft their first strategy, here's the exact process that works 👇
This approach - from Bob Moesta's Demand-Side Sales - transformed how I work.
Here's how:
Most customer conversations fail because we accept surface answers.
"Why did you buy our product?"
"It seemed easy to use."
This tells you nothing about their real motivation.
Here's how:
Most customer conversations fail because we accept surface answers.
"Why did you buy our product?"
"It seemed easy to use."
This tells you nothing about their real motivation.
May 8, 2025 at 4:01 PM
This approach - from Bob Moesta's Demand-Side Sales - transformed how I work.
Here's how:
Most customer conversations fail because we accept surface answers.
"Why did you buy our product?"
"It seemed easy to use."
This tells you nothing about their real motivation.
Here's how:
Most customer conversations fail because we accept surface answers.
"Why did you buy our product?"
"It seemed easy to use."
This tells you nothing about their real motivation.
Greg McKeown in his book Effortless suggests we ask: "Why is this so hard?" followed by "What if this could be easy?"
This simple inversion challenges everything in product culture.
Every time you feel you're pushing a boulder uphill, that's your cue: there's probably an easier path.
This simple inversion challenges everything in product culture.
Every time you feel you're pushing a boulder uphill, that's your cue: there's probably an easier path.
May 8, 2025 at 1:56 PM
Greg McKeown in his book Effortless suggests we ask: "Why is this so hard?" followed by "What if this could be easy?"
This simple inversion challenges everything in product culture.
Every time you feel you're pushing a boulder uphill, that's your cue: there's probably an easier path.
This simple inversion challenges everything in product culture.
Every time you feel you're pushing a boulder uphill, that's your cue: there's probably an easier path.
maybe this time it'll be different
May 7, 2025 at 4:04 PM
maybe this time it'll be different
Technical folks transitioning to product often struggle with product thinking.
Here's what I think works for developing product sense 📋
Here's what I think works for developing product sense 📋
May 7, 2025 at 12:56 PM
Technical folks transitioning to product often struggle with product thinking.
Here's what I think works for developing product sense 📋
Here's what I think works for developing product sense 📋
I spent years writing specs nobody read while less talented PMs got promoted.
Then I read Power by Jeffrey Pfeffer, and everything clicked.
Here’s the uncomfortable truth that changed my career in 5 minutes: 🧵
Then I read Power by Jeffrey Pfeffer, and everything clicked.
Here’s the uncomfortable truth that changed my career in 5 minutes: 🧵
May 6, 2025 at 4:02 PM
I spent years writing specs nobody read while less talented PMs got promoted.
Then I read Power by Jeffrey Pfeffer, and everything clicked.
Here’s the uncomfortable truth that changed my career in 5 minutes: 🧵
Then I read Power by Jeffrey Pfeffer, and everything clicked.
Here’s the uncomfortable truth that changed my career in 5 minutes: 🧵
love this visual of the whole product/market fit journey, and what to measure along the way
(h/t iwantproductmarket.fit/)
(h/t iwantproductmarket.fit/)
May 6, 2025 at 2:57 PM
love this visual of the whole product/market fit journey, and what to measure along the way
(h/t iwantproductmarket.fit/)
(h/t iwantproductmarket.fit/)
2 types of companies
May 6, 2025 at 12:58 PM
2 types of companies
SVP doing skip level 1:1s
May 5, 2025 at 3:00 PM
SVP doing skip level 1:1s
Every enterprise software company's leadership page
May 4, 2025 at 2:56 PM
Every enterprise software company's leadership page
if you want to win in a large org, make everything worse 😂
“the appearance of thinking is more valuable than actual progress”
from @si
“the appearance of thinking is more valuable than actual progress”
from @si
May 4, 2025 at 2:00 PM
if you want to win in a large org, make everything worse 😂
“the appearance of thinking is more valuable than actual progress”
from @si
“the appearance of thinking is more valuable than actual progress”
from @si
love this list of product development biases by @johncutlefish
should i write about these in more detail?
should i write about these in more detail?
May 3, 2025 at 3:57 PM
love this list of product development biases by @johncutlefish
should i write about these in more detail?
should i write about these in more detail?
You left engineering because you were tired of:
- PMs who don't understand system dependencies
- "Product people" who can't think in flows
- Leaders who demand random features
- Roadmaps built on hope
But what if product management was actually about systems?
"Thinking in Systems" blew my mind:
- PMs who don't understand system dependencies
- "Product people" who can't think in flows
- Leaders who demand random features
- Roadmaps built on hope
But what if product management was actually about systems?
"Thinking in Systems" blew my mind:
May 3, 2025 at 3:03 PM
You left engineering because you were tired of:
- PMs who don't understand system dependencies
- "Product people" who can't think in flows
- Leaders who demand random features
- Roadmaps built on hope
But what if product management was actually about systems?
"Thinking in Systems" blew my mind:
- PMs who don't understand system dependencies
- "Product people" who can't think in flows
- Leaders who demand random features
- Roadmaps built on hope
But what if product management was actually about systems?
"Thinking in Systems" blew my mind:
product manager using their 16” M4 Max Macbook Pro to open Slack
May 3, 2025 at 1:00 PM
product manager using their 16” M4 Max Macbook Pro to open Slack
Product Manager using his product sense to ignore all user feedback
May 3, 2025 at 2:37 AM
Product Manager using his product sense to ignore all user feedback
6/ Suggestions
May 2, 2025 at 4:01 PM
6/ Suggestions
5/ Experiments & ideas the founder has tried
May 2, 2025 at 4:01 PM
5/ Experiments & ideas the founder has tried
4/ Complications
May 2, 2025 at 4:01 PM
4/ Complications
3/ Key constraints
May 2, 2025 at 4:01 PM
3/ Key constraints
2/ Where the founder is right now
May 2, 2025 at 4:01 PM
2/ Where the founder is right now
there's a super useful case study in one of the r/ProductManagement threads, great for product folks who want to practice product thinking
tl;dr & some helpful summaries for you to think through: ↓
tl;dr & some helpful summaries for you to think through: ↓
May 2, 2025 at 4:01 PM
there's a super useful case study in one of the r/ProductManagement threads, great for product folks who want to practice product thinking
tl;dr & some helpful summaries for you to think through: ↓
tl;dr & some helpful summaries for you to think through: ↓
stop giving up control as a product manager.
my best ideas died in engineering debates.
i'd share an idea; they'd propose a "better way."
i'd quietly agree.
6 months later, we had a confusing product no one wanted.
escaping the ownership abdication trap changed everything:
my best ideas died in engineering debates.
i'd share an idea; they'd propose a "better way."
i'd quietly agree.
6 months later, we had a confusing product no one wanted.
escaping the ownership abdication trap changed everything:
May 2, 2025 at 2:57 PM
stop giving up control as a product manager.
my best ideas died in engineering debates.
i'd share an idea; they'd propose a "better way."
i'd quietly agree.
6 months later, we had a confusing product no one wanted.
escaping the ownership abdication trap changed everything:
my best ideas died in engineering debates.
i'd share an idea; they'd propose a "better way."
i'd quietly agree.
6 months later, we had a confusing product no one wanted.
escaping the ownership abdication trap changed everything:
technical PMs are killing their credibility in every meeting.
i spent 2 years making this exact mistake after switching from a more engineering/data background.
here's my set of practices that fixed it
this could save you years of painful trial & error ⬇️
i spent 2 years making this exact mistake after switching from a more engineering/data background.
here's my set of practices that fixed it
this could save you years of painful trial & error ⬇️
May 2, 2025 at 1:58 PM
technical PMs are killing their credibility in every meeting.
i spent 2 years making this exact mistake after switching from a more engineering/data background.
here's my set of practices that fixed it
this could save you years of painful trial & error ⬇️
i spent 2 years making this exact mistake after switching from a more engineering/data background.
here's my set of practices that fixed it
this could save you years of painful trial & error ⬇️
💎 buried in Anthropic’s GitHub is a hidden gem: Sequential Thinking MCP.
highly useful for:
- solving complex problems
- analysis needing adjustments
- unclear scope issues
link below
highly useful for:
- solving complex problems
- analysis needing adjustments
- unclear scope issues
link below
May 2, 2025 at 1:00 PM
💎 buried in Anthropic’s GitHub is a hidden gem: Sequential Thinking MCP.
highly useful for:
- solving complex problems
- analysis needing adjustments
- unclear scope issues
link below
highly useful for:
- solving complex problems
- analysis needing adjustments
- unclear scope issues
link below