Ask Lemmy
A Fediverse community for open-ended, thought provoking questions
Please don't post about US Politics. If you need to do this, try [email protected]
Rules: (interactive)
1) Be nice and; have fun
Doxxing, trolling, sealioning, racism, and toxicity are not welcomed in AskLemmy. Remember what your mother said: if you can't say something nice, don't say anything at all. In addition, the site-wide Lemmy.world terms of service also apply here. Please familiarize yourself with them
2) All posts must end with a '?'
This is sort of like Jeopardy. Please phrase all post titles in the form of a proper question ending with ?
3) No spam
Please do not flood the community with nonsense. Actual suspected spammers will be banned on site. No astroturfing.
4) NSFW is okay, within reason
Just remember to tag posts with either a content warning or a [NSFW] tag. Overtly sexual posts are not allowed, please direct them to either [email protected] or [email protected].
NSFW comments should be restricted to posts tagged [NSFW].
5) This is not a support community.
It is not a place for 'how do I?', type questions.
If you have any questions regarding the site itself or would like to report a community, please direct them to Lemmy.world Support or email [email protected]. For other questions check our partnered communities list, or use the search function.
Reminder: The terms of service apply here too.
Partnered Communities:
Logo design credit goes to: tubbadu
view the rest of the comments
Not really, but that’s largely because what I consider to be my area of expertise is extremely niche. I am a Lead Product Manager for an internal software. I started out as an IT business analyst for the software literally as soon as it started development out of the proof-of-concept phase. Two years in, I got promoted to Product Manager. Five more years and I’ve had 2 more promotions, growing to the Lead role I have now.
There is only one person at my company whose knowledge of the application rivals my own, and he started out in QA at the same time, then backfilled my BA role when I moved to Product. I know that application inside and out; its upstream dependencies, its users, its place in our business and our technical architecture, etc. And that’s because I’ve had a hand in building it since the beginning.
People I’ve never even met think of my name as synonymous with the software. I am literally the expert on it. My tool touches almost every part of our business and ultimately makes the day-to-day jobs of over 60k people easier. I constantly learn from working on it, and in seven years it has never been boring.
However, I am no longer the only PM for it. I manage a team of 3, and I empower them to run as autonomously as possible. Every year I am less of an expert because it has outgrown what one person can maintain in their head. I use my knowledge to build up my team, and they are becoming powerhouses in their own right. I am proud when I don’t know something in my app, because it means one of my staff owned that feature so wholly that I didn’t need to be closely involved.
Now, what of this knowledge is applicable to a broader industry? I honestly don’t know, and that sometimes freaks me out a bit. I think of Product Management as my vocation, and yet I’ve only ever done it on one team, one product. I take a course every couple years, but otherwise am not super up on generic Product Management skills/trends. However, multiple people who have broader backgrounds working with Product Managers than I do have called me the best PM they’ve ever worked with, so presumably I’ve gotten something right.
Not really an answer to the question as you intended it, I’m sure. But I do think about my role and my expertise in it a lot. And I really love it.
You sound like a truly awesome PM. I hope I get to work with someone like you one day.
Aww, thank you! Having a great team all around (PMs, devs, designers) is a big part of what makes it so great and so fun. I am lucky to have all of them. I also hope you get to work with an awesome PM. The PM can really make work hell for developers if they’re bad.
I thought of myself as a shield for my developers until I learned the industry term is “shit umbrella.” And yup, that’s exactly what I try to be for them! Pass through all the good things and reframe the crap I hear into something we can improve.