17

The role of a Product Manager is just a decade or two old. Most organisations, including FAANG, are still figuring out what are the primary responsibilities of a PM.

A vast majority I know, including my dumbass, is struggling to keep things floating while in the role. Learning on the job is one of the only and most effective way to do so.

No wonder, imposter syndrome is so common in this group.

One of the main tasks is to make decisions. Important and impactful ones. The role came into existence to take the decision making load off our engineering friends while building any product.

This shit comes with huge responsibility.

BUT, not everyone understand this. In India, being a developer was a cool thing until 2018 and so everyone rushed into the role. Now somehow everyone started thinking being a Product Manager is cool because all you have to do is sit and shoot orders and things will happen magically.

I get reached out by so many folks every month asking for guidance and when I ask them what a PM does or why they want to be a PM, the narrative is more or less same.

Very few actually understand how taxing the role is or the challenges that we face while performing the job.

WHY THE FUCK ARE PEOPLE SO IGNORANT AND DUMB?

And in another news, my first week at new job was super amazing. Loved every bit of it. People are smart, processes are neat, things are structured, and lots and lots to learn for me.

How are you guys doing? Been a while that we spoke.

Official declaration: I am the dumbest person I know.

Comments
  • 5
    Because they see what seems to them to be an easy job with easy money, who wouldn't want that.
    Eyyyyyy, yay for the new job being amazing we love to see it :D :D :D
    I'm doing great!
    Official declaration: You're NOT the dumbest person I know.
    Have a nice day ^^
  • 7
    For Fuck Sake ppl.

    PM has to represent the client to the dev team. Has to have great ppl skills. Has to know time manaagment. Has to have UX knowledege. Must be on call to clarify details. Has to write good Requirments.
    Above all - must understand that most of his time is to remove overhead, and obstacles for the devs to do thier job.
  • 4
    @SoldierOfCode Yes, that is the point. It is not an easy job :P

    Thanks bro for the wishes :)

    Hahaha I am just learning and figuring things out like many others.

    @magicMirror Well defined. I totally agree.
  • 1
    @Floydimus I can only agree with @magicMirror.

    Out PM primarily sync with business and handles priorities and is a gateway for anyone who wants to talk to the team to avoid to much random meetings chopping up the day.

    But with an IT department of almost 80 all focused on building for our retail business its a lot of synchronization between teams and business areas and much more ideas than time.

    For actual technical decisions there are enterprise UX and Team UX that ensures consistent experience.
  • 0
    Their jobs is creating department wide meetings every couple days.
  • 0
    @Voxera What's your point?
  • 1
    @Floydimus that a good PM has a lot to do and is s big help but a bad one can drag the team down.
  • 0
    @Voxera
    >that a good PM has a lot to do and is s big help

    How many good PMs do you know or have worked with?
  • 1
    @Floydimus 3 so far, and that the only 3 I have worked with.

    I probably just been lucky ;)
  • 0
    @Voxera you have worked with 3 and all turned out to be good then surely its luck 🙃
Add Comment