# The New PM's Guide to Qu...
! [ rw-book-cover] (https://pbs.twimg.com/profile_images/1602541464851980288/Stnr4-Bl.png)
URL: https://twitter.com/nurijanian/status/1867932556995502397
Author: @nurijanian on Twitter
## AI-Generated Summary
None
## Highlights
> The New PM's Guide to Quick Wins That Actually Last
> Most "quick win" tips for new PMs are useless.
> "Fix bugs!"
> "Get low-hanging fruit!"
> "Prove immediate impact!"
> After coaching numerous PMs, here's what truly builds lasting impact in your first 90 days: ([View Tweet](https://twitter.com/nurijanian/status/1867932556995502397))
> 1/ The Quick Win Paradox
> Your first 90 days aren't about quick wins.
> They're about quick INSIGHTS that lead to lasting wins.
> Bad quick wins:
> • Random bug fixes
> • Vanity metrics jumps
> • Low-value features
> Good quick wins:
> • Insight velocity
> • Relationship capital
> • Decision clarity ([View Tweet](https://twitter.com/nurijanian/status/1867932569096118315))
> 2/ The Intelligence Gathering Phase (Days 1-30)
> Don't rush to ship anything.
> Instead, become an intelligence engine:
> • Listen or join as many customer calls as possible
> • Review all support tickets
> • Map stuck decisions and bottlenecks
> Document everything. ([View Tweet](https://twitter.com/nurijanian/status/1867932581343502807))
> 3/ The Pattern Recognition Framework
> Create 4 lists:
> Customer Patterns:
> • Common complaints
> • Workarounds
> • Requested features
> Team Patterns:
> • Recurring blockers
> • Missing processes
> • Communication gaps
> Market Patterns:
> • Competitor moves
> • Industry trends
> • Missed opportunities
> Technical Patterns:
> • System limitations
> • Technical debt
> • Infrastructure gaps ([View Tweet](https://twitter.com/nurijanian/status/1867932593343365459))
> 4/ The Impact Matrix
> Plot potential quick wins on two axes:
> • Speed to implement
> • Duration of impact
> Avoid:
> Fast + Short-term = Sugar high
> Slow + Short-term = Resource drain
> Target:
> Fast + Long-term = Golden wins
> Slow + Long-term = Strategic bets ([View Tweet](https://twitter.com/nurijanian/status/1867932605552939265))
> 5/ The Golden Win Characteristics
> Must have ALL:
> • <2 weeks to implement
> • Touches real user pain
> • Improves team efficiency
> • Creates lasting change
> • Reveals deeper insights
> Example:
> Adding mandatory categorization to support tickets
> • Fast to implement
> • Helps users get faster support
> • Makes support team efficient
> • Provides ongoing insights
> • Reveals product gap patterns ([View Tweet](https://twitter.com/nurijanian/status/1867932617531899943))
> 6/ The Relationship Map
> Plot key stakeholders on:
> • Decision power
> • Pain level
> • Potential alliance
> Target quick wins that:
> • Solve real stakeholder pain
> • Build lasting relationships
> • Create future champions ([View Tweet](https://twitter.com/nurijanian/status/1867932629393355160))
> I've collected frameworks for this in https://t.co/wjJ6fGNr2E.
> All you have to do is hit that link and start adding techniques and ideas into your plan.
> Let me know if you need help.
> Now, let's address these real fears: ([View Tweet](https://twitter.com/nurijanian/status/1867932641212940301))
> 7/ Commons Fears
> "I don't have authority to make meaningful changes"
> Truth: Authority comes from insights, not position.
> Start with:
> • Document current state clearly
> • Show impact of problems numerically
> • Propose simple, specific solutions
> • Ask for limited experiments
> Example:
> "Our support team spends 40% of time re-categorizing tickets. A 2-day fix could save 15 hours/week. Can we try it for one week?" ([View Tweet](https://twitter.com/nurijanian/status/1867932653233770899))
> 8/ "Everything important seems too risky"
> Reframe risk:
> • Small changes compound
> • Quick wins build trust
> • Trust enables bigger moves
> Start with:
> • Document current process
> • Suggest small improvement
> • Show clear success metrics
> • Create feedback loop
> You're not risking the product.
> You're experimenting with improvements. ([View Tweet](https://twitter.com/nurijanian/status/1867932665191731504))
> 9/ "Senior stakeholders won't take me seriously"
> The credibility builder:
> • Speak in metrics
> • Show your work
> • Admit uncertainty
> • Follow through reliably
> Instead of:
> "I think we should improve the support process"
> Try:
> "I analyzed our support data. Here are three facts that suggest a clear opportunity..." ([View Tweet](https://twitter.com/nurijanian/status/1867932677191635122))
> 10/ "I might mess up and ruin my career"
> Reality check: Most new PMs get stuck, not fired.
> The safety framework:
> • Document current state
> • Propose reversible changes
> • Set clear success metrics
> • Build feedback loops
> • Create escape hatches ([View Tweet](https://twitter.com/nurijanian/status/1867932689044816246))
> 11/ The Learning Loop
> Every quick win should teach you about:
> • User behavior
> • Team dynamics
> • System constraints
> • Market realities
> If it doesn't generate insights, it's just busy work. ([View Tweet](https://twitter.com/nurijanian/status/1867932700818169868))
> 12/ The Execution Framework
> Week 1-2:
> • Map current state
> • Identify patterns
> • Build relationship map
> • List potential wins
> Week 3-4:
> • Prioritize opportunities
> • Validate with stakeholders
> • Plan first experiment
> • Set success metrics
> Week 5-6:
> • Execute first win
> • Document learnings
> • Share insights broadly
> • Plan next move ([View Tweet](https://twitter.com/nurijanian/status/1867932712893579760))
> 13/ Signs You're Doing It Right
> • Teams come to you with data
> • Stakeholders ask your opinion
> • Engineers share constraints early
> • Quick wins spark deeper discussions
> • Insights compound over time ([View Tweet](https://twitter.com/nurijanian/status/1867932724776042727))
> 14/ When To Break These Rules
> • Critical system issues
> • Major market shifts
> • Team crisis moments
> • Compliance requirements
> These merit different approaches. ([View Tweet](https://twitter.com/nurijanian/status/1867932736545231225))
> What's the point of quick wins?
> Break the PM cycle: Fear → Safe Moves → No Impact → Less Confidence → More Fear
> Ask: "Avoiding mistakes or pursuing insights?"
> Always pursue insights.
> For more, follow [nurijanian](https://twitter.com/nurijanian) ([View Tweet](https://twitter.com/nurijanian/status/1867932748310352008))