3 ms·
Early in my tenure running a Product team I decided that one of my goals would be for PM/Design and Engineering to be as close as possible. I would literally sa
by hackitup7 4y ago
Early in my tenure running a Product team I decided that one of my goals would be for PM/Design and Engineering to be as close as possible. I would literally say that I wanted them to view one another as brothers/sisters, and tried to set the example that we would go to bat for engineering (and expect the same) in almost all cases. I think it was probably one of the best organizational decisions I ever made.
- mrcwinn 4y agoI'm a Chief Product Officer at the moment with both experience around product design, UX/UXR, product management — but also a very deep software engineering background. I certainly have some blind spots, but it's a real advantage to be able to communicate a cohesive narrative and build "one" team (with lots of fantastic disciplines and even, at times, some intentional silo'ing). I can describe the why behind our prioritization, but also keep in view the strategic engineering investments we'll make to support our product vision over the long-term. Will it scale forever? Who knows. But I absolutely believe in fully-integrated product teams. You can really ship some amazing work when you get it right.
- ipaddr 4y agoI have seen cases where pm is close to developers or close to the business leaders. Sometimes too close to either group excludes the other. A balanced pm is preferred.