Much of the perfectionism struggle of #productmanagers stems from how the organization's culture handles change and uncertainty, and how technical company leaders are.
It's more common than not that management and company leaders lack experience in software and even fundamental technical literacy.
They don't understand that software is unpredictable and that timelines and roadmaps can only ever be rough estimates.
When management demands detailed new plans and review meetings every time things don't go according to plan, it makes product managers want to nail everything down super early and not tolerate unknowns.
If tech leaders want to cultivate a culture that tolerates change and uncertainty, first understand that the best plans and timelines allow room for things to go wrong.. because reality check: 90% of the time things *will not go as planned*.
Also take a look at the systems put in place.
Humans are extremely adaptable and most of our collective behaviors, successes, and failures are a direct result of which behaviors a system rewards and which it punishes.
#productmanagers It doesn't matter how much effort you put into crafting your business requirements. Or if you brought engineers into the conversation early on during product ideation.
The very nature of software is unpredictability. At some point, sh*t will hit the fan, or at the very least, something will not go according to plan.
The best product managers know this intimately. Not only do they *not* expect perfection, they *expect things to go wrong* at some point in the software development process.
#productmanagers, it's normal to be afraid of asking "stupid" questions during engineering meetings if you're not confident in your technical skills. You're far from the only one.
I got asked via my newsletter about the traits of the best and worst #productmanagers I've worked with..
.. and man, this question really took me on a walk down memory lane.
I immediately had flashbacks of my time at Amazon as an engineer, working with some of the most talented product managers I’ve ever worked with… and ironically, also some of the most frustrating.
What separated them? Three things immediately come to mind:
- Willingness to improve your technical skills
- Ability to bridge the pm<->engineering communication gap
- Having an “enabling” vs. “telling” mindset
Common struggle from #productmanagers I coach:
Q: How do I go about user stories? What do engineers want to see from them?
Pro-tip I teach them:
Write broad epic user stories first.. then break them down into functional user stories.
First, write broad epic user stories to..
- Communicate customer problem & get team alignment
- Encourage coming up w/ creative solutions for problem
❗Do ⬆️ early on in your reqs research/documenting and use epic user stories as a way to engage devs EARLY in the product roadmap
..then break them down into more specific functional user stories to..
- Help engineers understand the details of the product solution
- Helps engineers start thinking through what technical implementation details