George from 🕹prodmgmt.world Profile picture
Nov 7 12 tweets 3 min read Read on X
Every PM advice article preaches the same meeting prep gospel:

- Create structured agendas
- Define clear outcomes
- Prepare talking points
- Document decisions

Meanwhile, 95% of PMs are clicking "Join meeting" with 30 seconds to spare

1/12
There was a Reddit thread asking about meeting prep tools revealed everything

Top answer with 14 upvotes: "Brain, mostly. Pen, when necessary. The most important tool though is the toilet."

Another senior PM: "My mouse to click Join meeting. Anything beyond that I don't have the ROI to bother"

We're all living this lie

2/12
The meeting prep theater goes like this:

Monday: Create elaborate Notion template for meeting preparation
Tuesday: Fill it out once, feel productive
Wednesday: Skip it, meeting goes fine
Thursday: Abandon template
Friday: Back to sticky notes

Every. Single. Time.

3/12
What actually happens before meetings:

3 minutes before: Quick Slack to ask "what are we discussing again?"
2 minutes: Scan last email thread for context
1 minute: Open relevant doc
30 seconds: Test audio
0 seconds: Turn on camera, act prepared

And the meeting usually goes fine

4/12
The psychology behind meeting prep frameworks is fascinating

We create complexity to feel professional
We document things nobody will read
We prepare for scenarios that won't happen
We template conversations that need to be organic

All because admitting we wing it feels unprofessional

5/12
I've sat through hundreds of "well-prepared" meetings

The ones with 10-slide pre-reads nobody read
The ones with elaborate RACI matrices
The ones with minute-by-minute agendas

They weren't more productive than the ones where we just... talked

6/12
Your stakeholders aren't studying your agenda

They're also joining with 30 seconds to spare
They haven't read your pre-read
They forgot what this meeting is about
They're hoping you'll remind them why we're here

The whole thing is collaborative improvisation

7/12
The framework that senior PM shared on Reddit is actually brilliant:

Just track:
- What we're discussing (one line)
- Who owns it
- What outcome we need

That's it. Everything else is performance anxiety disguised as preparation.

8/12
Most meeting prep "tools" solve the wrong problem

They optimize for documentation, not conversation
They add friction to human connection
They create artifacts nobody references
They make simple things complicated

When what we really need is clarity of intent

9/12
Here's what works:

Know your one key outcome
Have your one burning question
Bring your one important context

Everything else emerges from genuine conversation

The best meetings aren't scripted, they're responsive

10/12
This is why product managers burn out on process

We're told to prepare perfectly for everything
Document thoroughly
Plan meticulously
Structure completely

When 80% of our value comes from showing up and using our judgment in the moment

11/12
If you're exhausted by meeting prep expectations, I built something different

AI prompts that skip the theater and get to the point:
- Quick context gathering (30 seconds)
- Key questions to ask (not scripted)
- Outcome clarity (one sentence)

Grab here:

12/12prodmgmt.world/products/ai-pr…

• • •

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

Nov 4
The biggest differentiator between good and average PMs in the AI era is the same as every other era.

They solve real problems instead of looking for places to jam AI into products.
1/ Everyone's obsessing over "AI literacy" and "prompt engineering skills."

Meanwhile the best PMs are still doing what they've always done:

Finding painful problems worth solving, understanding why they hurt, building things people actually want.

AI is just another tool in the toolkit.
2/ Average PMs are spending hours crafting LinkedIn posts about being "AI-first" and "AI-native."

Good PMs are using AI to ship faster, then moving on to the next real problem.

The gap between these two groups keeps widening.
Read 8 tweets
Oct 30
Stop doing these 'best practices' in as a Product Manager:

- Backlog grooming
- Writing JIRA tickets
- Leading stand-ups
- Playing scrum master

A thread on what to do instead (from someone who learned the hard way) 🎞️
1/ Stop running the daily standup

"But who'll run it if I don't?"
Startup: Your tech lead/senior eng
BigCo: Team lead/EM

Why? Every minute you spend running process is a minute not spent on:

- Finding highest-impact problems
- Aligning stakeholders on vision
- Uncovering hidden assumptions

Leaders: Coach PMs to attend but not lead.
2/ Stop being the team's secretary

Common trap: Becoming the human JIRA

- Taking all the notes
- Updating all the tickets
- Chasing every status

Startup: Let engineers own their tasks
BigCo: That's what delivery managers are for

Leaders: If your PM is doing this, your org has unclear roles.
Read 11 tweets
Oct 29
I spent 3 years working with an engineering team that openly despised product managers.

Every interaction felt like negotiating with someone who wanted me to fail.

Here's what that toxic dynamic taught me about when to fight and when to walk away:

1/17
The warning signs were there from day one:

- Requirements were never "detailed enough" but they wouldn't explain what they needed
- Status updates? "You're the PM, you should know"
- Questions? "Stop wasting our time"
- Meetings? Either I was micromanaging or not involved enough

2/17
The worst part wasn't the hostility.

It was watching myself become smaller. Apologizing for existing. Walking on eggshells around people who were supposed to be partners.

I started dreading Monday mornings. My confidence evaporated. I questioned if I belonged in product at all.

3/17
Read 17 tweets
Oct 12
a senior PM i worked with was stuck at her level for 4 years.

great execution. strong metrics. glowing reviews.

then i asked her one question that changed everything:

"what story are you telling yourself about who you are?"

the answer revealed why 80% of PMs plateau 🧵
1/ she said: "i'm a high agency PM who gets things done no matter what."

"and how's that working for you?"

"great! my team knows i'll always deliver."

"then why haven't you been promoted?"

silence.
2/ every PM tells themselves a story about their identity.

these stories feel empowering but actually become cages:

"i'm the execution machine"
"i'm the data-driven one"
"i'm the customer advocate"

each label limits what you allow yourself to become.
Read 12 tweets
Oct 11
Junior PMs watch scapegoating destroy their teams and think they're powerless to stop it.

Half true.

You can't fix your org's mimetic dynamics. But you control more than you think.

7 specific moves that work when you have no authority: ↓ Image
1. Control your language in written updates

When you write status updates or post-mortems, use "we decided X" not "Person Y did X."

Bad: "Engineering skipped tests to hit the deadline."

Good: "We chose speed over testing given the customer commitment."

Same information. Zero blame. The difference matters when leadership looks for someone to sacrifice.
2. Control your response when someone is being blamed in a meeting

You can't stop senior leaders from pointing fingers. But you can redirect.

When someone says "Design dropped the ball," interject with a process question:

"What in our process let this through?"

"What decision point should we revisit?"

Shift from person to system. Half the time, the group follows your lead because they're relieved someone broke the pattern.
Read 13 tweets
Oct 10
You don't avoid the chaos. You filter it.

Most PMs drown in context from devs, design, stakeholders, and user feedback that changes every 4 hours.

Your brain can't hold this. Stop pretending.

The filtering system that actually works: 🧵
1/ Every junior PM thinks they need to process everything.

Track every Slack thread. Attend every meeting. Read every doc. Respond to every ping.

Reality: 90% of "urgent" context has a 4-hour half-life.

You need better filters, not less chaos.
2/ Most PMs batch emails. Elite PMs batch context.

First hour: Strategic inputs (roadmap, vision, major decisions)
Mid-morning: Dev blockers and design reviews
Early afternoon: Tactical inputs (bugs, features, quick wins)
Late afternoon: Stakeholder updates
End of day: FYI inputs (updates, announcements)

Context switching kills. Batching saves.
Read 6 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!

:(