Early in the #product lifecycle, collecting feedback is of great value in shaping future strategy.
More often than not, PMs talk to customers in pursuit of affirmation, or acknowledgment falling into our good ol' Confirmation Bias.
The Confirmation bias stems from ego, we hate to be proven wrong, so we intentionally try to avoid feedback that distorts our carefully self crafted image of our dear products. There is a nice name for this, it's called the "Ostrich Effect".
To counter that, we need to step on Ego. leave it at the door and charge in pursuit of the truth not our version of it, but a neutral truth, even if it's ugly and contradictory to our initial hypothesis.
Product managers are truth detectives 🕵️
Another helpful tool is to look for disagreements on your initial hypothesis, i.e., play the devil's advocate if customers show initial interest in your product (once you are at a good place to pitch it).
This can help ensure the authenticity of the feedback you're getting.
Giving in to ego does more harm than good and leads to needless investments, ones that would have otherwise been useful in solving "true" authenticated problems.
The gist of it is to:
➡️ Lock away ego
➡️ Ask insightful questions
➡️ Look for Disagreements
➡️ Seek the truth
If you liked this content make sure to follow for more, we are just starting 🙌
• • •
Missing some Tweet in this thread? You can try to
force a refresh
Product management can be a lonely occupation, we self navigate most of the time, without feedback or coaching it can lead to false sense of righteousness.
It does not have to be this way though, today there are great communities that teach and preach product.
Three bricklayers are asked: “What are you doing?”
➡️ The first says, “I am laying bricks.”
➡️ The second says, “I am building a wall.”
➡️ And the third says, “I am building the house of God.”
Ruinous Empathy might seem like the right thing to do but is short sighted and cause harm in the long term. Keep the empathy, drop the "ruinous" part by communicating feedback effectively, listening to understand not to speak back, this is not about you.
Eventual convergence is enough, nothing has to be perfect, we are humans after all. Misfortunes will happen, but so will learnings and comradery.
With edge-triggering, the system would react to every event be it major or minor by issuing detailed instructions on how to reach a state. With level-triggering, the "how" is not really relevant, what matters is that the desired state is reached matching the conditions specified.