George from 🕹prodmgmt.world Profile picture
Aug 17 20 tweets 4 min read Read on X
After studying high-performing PMs for years, I noticed something strange:

The most impactful product managers often do LESS than their peers.

They write shorter docs. Hold fewer meetings. Create simpler processes.

They've mastered making impact look effortless.

Here's how:
I spent my first 3 years as a PM writing 30-page PRDs no one read and creating complex processes no one followed.

I thought "good product work = hard product work."

But what if the opposite is true? What if making it harder actually reduces your impact?
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.Image
Principle 1: Define exactly what "done" looks like.

Vague goals = endless work.

Bad: "Create a comprehensive product strategy"
Good: "A 1-page strategy document with 3 clear objectives, approved by leadership by Friday"

What's your current "done" definition?
Principle 2: Take the minimum viable action.

Steve Jobs walked to a whiteboard and drew a rectangle.

"Here's the new application. You drag your video into the window. Then click BURN. That's it."

What's the simplest version of your current project?
Principle 3: Start from zero, not from complexity.

Most PMs start with everything possible, then try to cut back.

Elite PMs start with nothing, then add only what's essential.

"What's the minimum number of steps required for completion?"
Principle 4: Embrace the "zero draft" approach.

Don't start by trying to write the perfect PRD.

Start by writing a terrible one. The "zero draft" - so bad it doesn't even count as a first draft.

This breaks the paralysis of perfectionism.
Principle 5: Establish upper AND lower bounds.

"Never less than X, never more than Y"

Example:
- Never less than 3 customer conversations per week
- Never more than 15 customer conversations per week

What's your sustainable pace?
I get it. You're thinking: "Our product is complex, so our processes need to be complex too!"

I thought the same until I noticed something:
The most complex products often have the simplest PM processes behind them.

Complexity requires clarity, not more complexity.
"But my stakeholders expect comprehensive documentation!"

Reality: They want their needs met, not documentation for documentation's sake.

Try this: Next time, deliver a 1-page summary instead of a 20-page PRD. See what actually happens.
Most PM work produces linear results:
- Documentation = one-time output
- Meetings = time in, decisions out
- Daily stand-ups = daily updates

But elite PMs focus on residual results - effort that compounds over time.
Examples of residual PM work:
- Creating decision frameworks teams can use autonomously
- Building dashboards that provide ongoing insight
- Documenting principles (not just procedures)
- Teaching others to facilitate their own meetings

Small effort, ongoing returns.
The question that transformed my PM career:

"Is this a lever or a boulder?"

Levers: Small effort, big impact
Boulders: Big effort, small impact

I now spend 80% of my time looking for levers, not pushing boulders.
Finding leverage in product work is all about having the right frameworks at your fingertips.

I've found

helpful for this - curated frameworks so I'm not reinventing wheels.

What are your go-to resources for leveraging your impact?prodmgmt.world/products/produ…
Speaking of leverage, I've discovered having pre-tested AI prompts for common PM tasks significantly reduces cognitive load.

AI Prompts for Product Work has some great templates for routine PM tasks.



Work smarter, not harder.prodmgmt.world/products/ai-pr…
Personal example:

I replaced our 30-minute sprint planning meetings with a simple async template.

Team now spends 10 minutes individually, outcomes improved, and I got back 20+ hours per month.

Small changes, massive returns.
One simple change I encourage every PM to try:

Before your next meeting, ask: "Could this be an email?"

Before creating a doc, ask: "Could this be a single slide?"

Before building a feature, ask: "Could we do half of this and still get 90% of the value?"
Your challenge this week:

Pick ONE thing in your product process that feels unnecessarily hard.

Ask: "What if this could be easy?"

Then try the easiest possible approach.
"Effortless" by @GregoryMcKeown wasn't written specifically for PMs, but it should have been.

It's transformed how I approach product work, and I can't recommend it enough.
Remember: Making things look effortless doesn't mean you're not working hard.

It means you're working smart.

Elite PMs aren't defined by how many hours they put in or pages they write.

They're defined by the impact they create relative to the effort they expend.

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with George from 🕹prodmgmt.world

George from 🕹prodmgmt.world Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @nurijanian

Aug 16
99% of PMs complain about their managers.

1% of PMs turn their manager into a career accelerator.

The 1% stopped "managing up" and started creating mutual leverage.

Here's the exact playbook ↓
Your manager spends 2-3 hours/week thinking about your work.
You spend 40+ hours executing it.

This 20:1 asymmetry creates most PM-manager tensions.

The solution isn't more meetings or better updates.
It's creating *mutual leverage*.
Stop thinking "How do I manage my manager?"
Start thinking "How do we multiply each other's impact?"

When PMs make this shift:
• Autonomy increases
• Micromanagement disappears
• Career velocity accelerates

Let me show you the system.
Read 15 tweets
Aug 14
78% of organizations now use AI in at least one business function (McKinsey 2024).

But most product leaders are still using it for basic tasks like writing PRDs.

Here's how to leverage AI for strategic advantage (with actual prompts that work): 🧵
McKinsey found only 1% of companies believe they're at AI maturity.

Meanwhile, 43% of professionals use AI tools without telling their bosses (2024 survey).

The gap? Most PMs don't know HOW to prompt AI for strategic work vs. documentation.
From my AI prompt collection - Transform competitive analysis:

"Analyze the spreadsheet thoroughly. Pay attention to:
- Features unique to your company
- Areas where you outperform competitors
- Gaps in market not addressed by competitors"

Real PMs report 40% productivity gains with strategic prompting.
Read 7 tweets
Aug 13
The real impact of AI on PM work:

PRDs: 8 hours → 45 minutes
Interview analysis: Full day → 30 minutes
Strategy decks: 2 days → 3 hours
Requirements docs: 5 meetings → 1 async session

Here's exactly how the workflow changes 🧵
BEFORE AI:
- Monday: Gather scattered inputs (2 hrs)
- Tuesday: Blank page to first draft (3 hrs)
- Wednesday: Stakeholder feedback rounds (2 hrs)
- Thursday: Endless revisions (1+ hr)
- Friday: "Actually, can we add..." (∞)

WITH AI:
- Dump all context into structured prompt (5 min)
- Review generated draft (20 min)
- Customize for specific needs (20 min)
- Ship
The old way:
- 10 interviews = 10 hours recording
- Manual transcription = 3+ hours
- Finding patterns = 4 hours staring at notes
- Writing insights = 2 hours
- Total: 19 hours across 2 weeks

The AI way:
- Recording time unchanged (10 hrs)
- Auto-transcription (instant)
- Pattern extraction (30 min)
- Insights with supporting quotes (automated)
- Total: 10.5 hours in a few days
Read 9 tweets
Aug 13
The "simple 2-week integration" that becomes a 6-month death march.

Every PM knows this nightmare.

Here's why it happens—and how to prevent it before writing a single line of code 🧵
It always starts the same:

Week 1: "Just need to add SSO login"
Week 3: "Actually, we need custom roles"
Week 5: "Oh, and multi-tenancy"
Week 8: "Can we also sync with their legacy system?"

Classic scope creep in action.
By month 3, the typical "simple" project has:
- 10+ microservices touched
- 4+ teams involved
- 0 clear requirements
- Multiple stressed PMs

Leadership: "Why is this taking so long?"

Because nobody defined "this" properly.
Read 9 tweets
Aug 11
PMs: When a customer says “I want CSV export,” and you just write it down, you’re wasting the interview.

Here’s how to flip lazy feature requests into goldmine insights.

It took me 5 years of painful interviews to learn this. You’ll get it in 1 minute. Image
1/ The proper response is to probe the underlying need:

"What would CSV export allow you to do?"
"How are you handling this today?"
"Talk me through the last time this came up"

I've added prompts to AI Prompts for Product Work to help PMs dig deeper: 👉 ($15) 🛍️prodmgmt.world/products/ai-pr…Image
2/ Fascinating insight from The Mom Test:

The world's most dangerous response in customer interviews is:

"I would definitely buy that"

It sounds concrete but is actually a completely valueless signal. Instead, push for commitment today.
Read 6 tweets
Aug 4
PMs: 60-hour weeks ≠ impact.

I wasted 2 years on work that looked productive but stalled my career. Elite PMs do the opposite.

Avoid these 6 fake productivity traps. Took me 2 years to spot, you’ll get them in 2 mins. 🧵 Image
1/ Writing detailed PRDs that nobody reads

I spent weeks crafting 20-page documents with perfect formatting.

Reality: Engineers skipped to the acceptance criteria. Stakeholders never opened them.

What to do instead: Start with a 1-page problem statement. Add details only when someone asks specific questions.
2/ Attending status update meetings

I thought being in every meeting made me seem essential.

Reality: Most meetings are information theater. You're not contributing, just consuming.

What to do instead: Ask "Is this for decision-making or just updates?" If updates, request async summaries instead.
Read 12 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Don't want to be a Premium member but still want to support us?

Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal

Or Donate anonymously using crypto!

Ethereum

0xfe58350B80634f60Fa6Dc149a72b4DFbc17D341E copy

Bitcoin

3ATGMxNzCUFzxpMCHL5sWSt4DVtS8UqXpi copy

Thank you for your support!

Follow Us!

:(