People who care deeply about putting things in the best light will seek out information that confirms that.
People who care about fixing things that are broken, will seek out information that confirms that.
3/n
Companies tend to draw from the same channels, and speak to the same customers over and over.
The same customers who complain the loudest.
The same "rock stars" who are the poster-children for the product.
4/n
We gravitate to salient and easy-to-consume information. The painful stuff is salient. The amazing stuff is salient.
Both are easier to process than the more nuanced, complex, messy stuff. Fixing and hyping is easy. Solving harder problems is...hard.
5/n
It can be very hard to tap into what things were like before customers started using your product. For you (the team) AND for them.
We might underestimate the sheer impact of the product because of this.
6/n
We have a bad habit of blaming the customer, an “edge case”, a “small sample”, or a “fluke” when we get discomforting information. And applauding our product when we get confirming information.
Except if we're biased to blaming the product :)
Gotta De-bias. Stop blaming.
7/n
Humans are very adaptable. When they *must* use your product they'll invent all sorts of workarounds and/or just ignore broken things. They a habituate
Oddly, it seems that some team members follow suit and can’t see what’s broken. While others can’t unsee all the UX debt
8/n
We rationalize past decisions all the time.
"All of the product debt was taken on for completely rational reasons and we wouldn't be a $Nbn company today if we had tried to make everything PERFECT"
9/n
And we may over-estimate the importance of the product being an 8-10 vs. a 6-8 in the grand scheme of things. At least from a business angle.
Think of all the companies printing $$ with godawful products.
If that's your goal ($) well...
10/n
Is there any objective truth?
The truth is that these statements can be contextually true, but both obscure the issue. The silent, messy majority.
Neither hype nor brazen critique are helpful.
Detailed, skilled, cohort-based, representative research does <end>
• • •
Missing some Tweet in this thread? You can try to
force a refresh
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
when you've found your team prematurely converging -- jumping to specifics too early -- what were some contributing factors?
...this is a weird one, but often it seems to happen when the bulk of the team is tied up with something, and a smaller group -- e.g. designer and PM -- are under pressure to "tee up" the next thing
...when the team lacks psychological safety? people just want to get it over with, so they just go with whatever seems like a reasonable deal to make the need to collaborate go away