4 ms·
It depends on the product, but probably not. If it's a very technical product where the customer is also technical then yes. If it's a user-centric product then
by crdoconnor 9y ago
It depends on the product, but probably not. If it's a very technical product where the customer is also technical then yes. If it's a user-centric product then I'd much rather they just had domain experience (and maybe UX skills).
The best PM I ever had was non technical, had no UX but had significant domain knowledge, and was pretty clear on the limits of his knowledge.
The worst PMs I've worked with are the ones that had a little bit of technical knowledge - just enough to be dangerous - and tried to direct the team to implement a half-baked solution where, more often than not, the actual problem they were trying to solve was shrouded in mystery.
- Myrmornis 9y agoYes, it's that last scenario that I particularly have in mind. PMs are typically led to believe that they should acquire some technical understanding and furthermore that they will be better respected if they do. This leads, as you say, to poorly designed solutions. I'm not personally convinced that requirements-gathering is an inappropriate activity for an IC engineer.