A thread of resources for aspiring & new Product Managers:
(should also be useful for Eng, Design, Data Science, Mktg, Ops folks who want to get better at PM work or want to build more empathy for your PM friends ☺️)
(oh, and pls also share *your* favorite resources below)
👇🏾
1/
Product Management - Start Here by @cagan
(hard to go wrong if you start with Marty Cagan’s work)
It’s important to understand your preferred learning style and go all in on that learning style (vs. struggling / procrastinating as you force a non-preferred learning style)
Most of my regular content is for senior product folks & leaders, though I get a lot of pings from early career folks, so I'm glad folks are finding this thread useful.
Some really great resources being shared by others here. Do take a look at them.
A few additional footnotes:
Important to understand what Prod Mgmt is really. It isn't uncommon for people to spend years as a PM without understanding the essence of the role, what PM success looks like, and the main skills & mindsets. Better to understand these fundamentals early.
This mega-thread is catered to aspiring PM leaders, but the 3 Essential Senses of a PM & the concept of 10-30-50 PMs is relevant for PMs at all stages. Start here to learn more:
Some say: understand users, have a strategy, take the time to build an amazing & delightful product
Others say: just build, ship quick & often, experiment, assess user reactions, learn, repeat
Both camps have evidence.
So what’s really going on?
Like a tweet👇🏾
(A)
Neither approach is as successful as advertised.
It’s just classic survivorship bias.
The successful ones try to dissect the elements of the approach that made their product or company successful, tweet about it, write books about it. And they do this with high confidence.
(B)
It depends on the type & stage of product.
An approach that works for a late-stage product can fail miserably for an early-stage product.
An approach that works for a b2b product can fail miserably for a consumer product.
You (at a project status meeting):
Project ABC's status is Yellow
Need [X] more resources to get it back on track.
Your Manager’s Manager (YMM):
We need to zoom out first
I would like to see a doc [or slides] with our strategy, roadmap & resourcing requests for Project ABC.
👇🏾
You:
OK, I have to deal with Acme Inc this week but can get that to you by next Friday
YMM:
Hmm… we really need this sooner.
Can you share by Monday instead?
You: (🤔this must be important for YMM, so I should do what’s being asked)
OK, will do
👇🏾
[On Monday]
You: (📨in email to YMM, cc’ing your manager)
Dear YMM, here’s the document you requested in last week's status meeting. Please let me know your feedback. I am happy to meet and discuss this further so we can proceed with the revised plan for Project ABC.
Most interview frameworks (and most work environments in general) tend to favor the verbally charismatic.
Verbal charisma is IME the #1 reason that otherwise-smart companies hire leaders who end up being quite incompetent on the job (and get fired in 6-18 months).
Since a bunch of folks asked about ways to identify such cases during the interview process, here's a thread with archetypes & concrete ways to detect each one:
Besides this, one skill I've tried to build over the years is to separate the message as much as possible from the messenger.
This helps me evaluate the quality of what is said (most important) independently from how it is said (fairly important) & who says it (least important).