#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.
This expectation makes you a better PM for many reasons. Here are two:
- Because you expect things to not go as planned, you're less upset when it actually happens
- Because you expect things to not go as planned, you're less upset when it actually happens
- You can quickly work with your engineering team to pivot requirements if necessary. Changing scope won't always be the right answer, but being flexible makes you a great PM to work with.
To be clear, I'm not saying you shouldn't put effort into your business requirements or try your best.
But I am saying not to expect perfection. No matter how perfectly you execute your job as a product manager or collaborate well with engineers, software is unpredictable.
It's better to be prepared to solve inevitable issues that arise, than be caught off guard when things don't work out as planned.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
