I've been reading a lot of great threads about the difference between "idealized" product management & "real world" product management.
as someone who contributes a fair amount of content, and interacts w/ a wide cross-section of teams, it has really gotten me thinking
1/n
2/n
It goes w/o saying, but one problem we have here is communicating about "the real world" is exceedingly hard! Even in books. It takes...words.
Much easier? 1) Generalized, high-level, good-sounding advice 2) Angst 3) Pragmatism ("apply in context","be curious")
3/n
One of my big challenges w/social media is that -- and I have the data to prove this -- the more angsty, pragmatic, or generalized the advice...the more it is consumed.
The more nuanced ... the less it is consumed.
Constant puzzle: reach or breadth?
3/n
Say you want to share some product advice to the world, and make it contextually relevant.
Either you: 1) Provide the advice, and then provide modifications/implications across a whole set of contexts 2) Clearly state your context
Both take...words.
4/n
Both are hard. Every Wed night when I sit down to write my weekly post, I swear I'm going to try to be better. And I fail. Every time.
I try to make up for it by dedicating ~50% of posts to "it is a mess" type themes.
Here's another way to look at. I asked people with a reasonable N in terms of organizations to describe 80% activities, 15% activities, and 5% activities...
What actual, specific, behaviors would we observe if someone was good at product thinking?
Specific enough that someone without a lot of tacit knowledge would be able to say “that’s happening”.
some off hand
1/n
Better Proxies for Value. We'd observe them challenge a "success metric" and ask if there was a better proxy for actual value exchange. Fewer overt vanity metrics (or at a minimum, leading indicators mapped to trailing indicators)
2/n
Consider multiple options. We'd observe them weighing a range of options to achieve the same effect (vs. simply prioritizing a list). "Well... some potential experiments might include..."
2) are attempts to frame lots of experience (e.g. based on the messy world I've seen, there are three categories of X)
And 3) pure teaching frameworks.
(1/n)
One is not better/worse, but they are different.
1. has been "tested" in context. That context is important
2. very much depends on the "observer", the collector of experiences. In some ways these are theoretical constructs.
3. needs the learning context outlined
(2/n)
Some of the most popular/helpful product blogposts of all time fit into the #2 cat. @reforge is incredible at this. They get product leaders together, and together write a post that presents a new model!
1) SME (e.g. healthcare, EMR)
and/or 2) deep persona expertise (e.g. nurses in large hospitals)
and/or 3) strong skills in a key PM skill area (e.g. analytics)
How about certifications (1/n)
IMHO, certifications can help in one of two situations:
1. A company with no product chops using something like "CSPO" to fill tons of newly opened positions because of an "agile transformation"
2. A signal you're serious...
#2 is interesting ... (2/n)
"As an SDR, I started to see how important it was to nail the product. I started to read everything I could. I took free courses. I paid for a product manager course"
something I've learned, and re-learned over and over -- at @Amplitude_HQ especially talking to so many teams.
It is vital -- absolutely vital -- to understand your product in the *broader landscape* of a customers workplace.
Why? 1/n
...when talking to a customer about your product, you will always trigger the instinct for them to be helpful and provide information about YOUR product. Which is good...
...but also a challenge.
The reality is that your product is a tiny part of their world. 2/n
"What problems are you having?"
Customer: "Um, well, [some task related to your product]"
(remembering to focus on goals)
"Oh no, what is your GOAL?"
Customer: "Um, well, [some goal related to your product]"
All good, except, again, this is a tiny part of their world. 3/n