7 ms·
I've done this and it fail horribly, I'm the product manager as well as the implementor. The problem is usually I choose solution which is easiest to implement
by fendy3002 5y ago
I've done this and it fail horribly, I'm the product manager as well as the implementor.
The problem is usually I choose solution which is easiest to implement and usually the scope is too tight because I need to also design the lower api and libraries.
- jrochkind1 5y agoI too feel like i've learned through experience that the product manager (whether with that title or just effectively being the one doing it) should never be the same person as the implementer/tech lead. It just doesn't work. And as an implementer/engineer, it ends up being so much less stressful when there is a product owner who you collaborate well with, but who is someone else. And you get a much more succesful product too. Even though I think I am someone who understands the customer/domain pretty well, and is good at empathizing with the user, you're just too close to the implementation to effectively product manage. In the domain I work in, I think people are used to the "head implementer" being the effective product manger (although without that title), and it takes some work to try to convince decision-makers, please, let's not do that.