|
|
|
|
|
|
by nip
922 days ago
|
|
|
I believe OP meant « implementation » with « how ». You want a PM that knows the product (really) well and brings new work to the developers in the form of well documented problems, not solutions. You don’t want your PM to get involved in the technical details. |
|
|
> not solutions
Often yes, solutions. When you're still in the "what are we building" phase you want a good PM deeply involved in the process. I think you may have implied that, but solution creation happens before code gets written.
You also sometimes want a PM to get involved in technical tradeoffs when they impact the user experience. I've found that this happens more often with a technical product (API capability or SDK interface) than a UI screen, but it comes up. When your PM is the expert in your userbase and how they expect to use something, they need to be involved a lot.