29) One of the most rewarding experiences in product management is being able to take more junior PMs under your wing and getting involved with their work. That way you can take credit for all their good ideas and blame them when things go wrong.
-
Show this thread
-
30) When you’re not sure if a feature is valuable, sometimes it’s a good idea to turn it off and see how it impacts the numbers. This is risky, though, so it might be better to just give it to your least favorite dev to maintain forever as a side project.
1 reply 1 retweet 11 likesShow this thread -
31) Be sure to capture any idea that anyone gives you in a JIRA ticket so that you can say you’re evaluating it and move that much more quickly toward calling the backlog “overwhelmingly full of bad ideas”, declare bankruptcy, and archive the whole thing
1 reply 0 retweets 15 likesShow this thread -
32) You’ll want to practice getting very good at articulating your ideas in written form and anticipating objections. Put them all into a long word document and print it out, so you have something to cuddle as you cry alone in your bed at night because no one ever reads them.
1 reply 0 retweets 13 likesShow this thread -
33) Pick up a little JavaScript on the weekends. It’s basically the same as Java and you’ll be totally qualified to weigh in on big architectural decisions for your technical platform. If anyone questions your expertise you can punish them by putting them on bug duty for a bit
1 reply 0 retweets 14 likesShow this thread -
34) Be sure to second-guess all the estimates your devs give you. They’re often wrong. The ideal way to do this is add up all the time they think a feature will take, cut off 20%, and then pick an arbitrary date for delivery because sales promised a customer it’d be ready by then
2 replies 4 retweets 25 likesShow this thread -
35) When you’re evaluating new features against each other for prioritization, there’s an easy formula you can use to gauge which one should be built first: (total dollars someone else said it could make * amount the CEO is excited about it) Be sure to have your scapegoat ready
1 reply 0 retweets 10 likesShow this thread -
36) Other product managers at the company aren’t your competition! If you piss them all off, you’re not going to have ANYONE who wants to hang out with you at the bar and cry after work.
2 replies 0 retweets 12 likesShow this thread -
37) Product managers are seen as leaders, and so it’s important to model vulnerability and authenticity! Only do this in ways that make you LOOK authentic and vulnerable though, because none of your leaders are actually being vulnerable or authentic with you either
1 reply 0 retweets 12 likesShow this thread -
38) It’s so important to always start your day by looking through user feedback, because this is the time of day when people are statistically most likely to drop by your desk unannounced and you need to look like you’re paying attention to that
2 replies 1 retweet 18 likesShow this thread
Damn I thought I was evil as a PM. I was a saint by this playbook.
-
-
Replying to @vgr
I always tell my PMs that they have to understand how to be evil if they want to choose to avoid it
0 replies 0 retweets 0 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.