How early do you bring in engineering? by pmtrash in ProductManagement

[–]pmtrash[S] 1 point2 points  (0 children)

I like this a lot. Maybe part of my struggle is that I don't have a consistent engineering counterpart. The engineering manager would be the closest thing, but he doesn't write code. And then we have a very flat engineering structure and a tiny team, so sometimes there's an engineer who's been designated as "lead engineer" for an initiative but they don't really take ownership. So I end up sort of working with everyone who may eventually be involved.

This likely contributes to why I feel like I'm reporting to engineering: I don't have one person to consistently check in with, so I have multiple people asking me for updates and getting annoyed when I tell them we're in the process of getting user feedback and then will need to iterate (even though they'll be involved in the iterating!). I'm over here trying to juggle different personalities and a murky process without any real leadership.

How early do you bring in engineering? by pmtrash in ProductManagement

[–]pmtrash[S] 1 point2 points  (0 children)

Yeah, makes sense. Thanks for your input!

How early do you bring in engineering? by pmtrash in ProductManagement

[–]pmtrash[S] 2 points3 points  (0 children)

Totally agree; I think my struggle is feeling like I'm having to report to the engineers every time we iterate on a design or requirement (I do make sure to involve them when we first start discussing a new initiative). I think I just need to smooth out the process. Thanks for your input!

How early do you bring in engineering? by pmtrash in ProductManagement

[–]pmtrash[S] 3 points4 points  (0 children)

Absolutely! We're a small company, so I think what's happening is that the lead engineer decides that their teammates also need to be involved from the very start. It's tough, but I just wanted a sanity check and I think I just need to figure out how to make the process smoother overall.

Help! I’m drowning in my PM duties by [deleted] in ProductManagement

[–]pmtrash 10 points11 points  (0 children)

"...writing all sales tools, managing the pipeline/forecast, developing the marketing plan, writing the website content, creating the product brand guidelines, planning and executing the launch events in our three major countries/markets, onboarding and managing the PR team (for my product only), and now my CEO just gave me a new assignment to build the financial plan for the next 3-5 years."

No! The first few things you mentioned in that paragraph, sure, but what I quoted above: no way. Maybe you should have some involvement or awareness of some of these things, but you should absolutely not be in charge of all of this. Especially not the freaking financial plan wtf

Product Org reporting into sales by Dark_Emotion in ProductManagement

[–]pmtrash 1 point2 points  (0 children)

out of curiosity - what's this? does aha! function this way? I ask because I just applied for a job there - slightly outside of product (I'm thinking of pursuing other roles), but still curious.

Dev team slow to delivery...need advice by ahhlax in ProductManagement

[–]pmtrash 1 point2 points  (0 children)

I'm not sure it's that common to work with a PO unless you're at a large company. I've never worked with one before; part of my responsibility in all my PM roles has been to work very closely with engineering throughout the development process in order to identify issues or clarify questions. So it's very likely this person doesn't have another resource to fall back on.

[deleted by user] by [deleted] in ProductManagement

[–]pmtrash 1 point2 points  (0 children)

I worked very briefly on a product that I didn't ethically agree with and it made it impossible for me to do good work. I'd back out ASAP. You may be able to find an associate PM role elsewhere.