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.
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.
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.
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
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