r/ProductManagement • • Jan 22 '25 Helpful Bless Up

Twitter/X links are banned

2.3k Upvotes

It probably doesn't matter much because there are so few of them, and most are removed for being low quality. However, it has been done.

===============

Editing on 22 January to address the following criticisms and questions.

Why the ban?

During a speech at Trump's inauguration Elon Musk used the Nazi salute.

That wasn't a Nazi salute.

Some like the ADL have said that it was not. However, there is good reason to believe that it was, and very little reason to believe it wasn't.

  • Over the past few years, Musk has made multiple racist and anti-semitic statements and has amplified the reach of others making similar ones

  • This doesn't appear to be random arm movment of flailing. If you compare what Musk did to Nazis and others performing the salute, they're nearly identical.

  • It has been celebrated by neo-Nazis and other members of the extreme-right. These are people who are used to dog whistles and are very attune to coded messages

What's the point? / There aren't many Twitter or X posts anyway.

Simply to reduce traffic to X.

This is censorship.

Not in the traditional sense. All of the ideas that have always been allowed on here still are. You just can't post links to a particular site. If you want to quote someone or post a screenshot, that's still allowed within the usual rules around quality and relevance.

Curation of content has always been part of the role of the moderators here and it's necessary in order to create an environment in which useful and engaging discussions can occur.

Censorship is part of fascism.

This is an ironic statement given that fascism is a far-right political ideology, and what's being blocked are links to a far-right figure's company and website.

You're creating division and echo chambers.

Incorrect. As stated above, the same kinds of content will be allowed, just like before.

One can also make a very supported argument that this is what Musk has been doing with Twitter since its acquisition.

Lots of other tech leaders were at the inauguration.

If they also make it clear that they and their companies are righ-wing garbage like Musk, they will also be banned. Until then, Musk is the only one doing this openly and publicly.

The mods are left-wing. / The mods are delicate snowflakes. / Etc.

I can't comment on the others, but this doesn't accurately describe my ideaology. However, this shouldn't really matter when we're talking about Nazis and Nazi sympathizers, wherever Musk falls into that range.

This doesn't demonstrate a good product mindset.

I struggle to understand what this actually means.

This was done unilaterally. / There should have been a poll.

Sorry, but this is a benevolent dictatorship.

User feedback is one aspect of decision-making. Nearly all (probably all, but I can't remember for sure) of the rules have been established without polls.

Based on the response and voting that has been seen so far, the results would have been in favor of the ban.

You're politicizing a subreddit that is unrelated to politics.

Maybe somewhat, but calling out Nazis and their sympathizers is always the right thing to do.

This is just an emotional response.

No, I spent a while thinking about it, and have spent more time since then. I haven't been able to come up with a good argument not to on my own and haven't seen an objection yet that has made me reconsider.


r/ProductManagement • • Jun 25 '25 Gold Blast This Bless Up

8 lessons I keep seeing after working with 100s of PMs (this is a long one)

2.1k Upvotes

I’ve worked with hundreds of PMs across different industries, sometimes coaching directly, sometimes supporting other coaches or teams. PMs trying to get promoted. Some trying to get new jobs. Some stuck in execution hell, and some just trying to figure out what the hell their job even is.

Here are 8 lessons I keep coming back to. No change your life in an instant, HAX. No theory. Just stuff that actually helps you grow, make impact, and not burn out.

Each one includes something small you can do today. You prob wont do all of them, but if it's valuable pick one.

1. Visibility beats execution (nothing new here, but it's true)

You can ship every sprint and still get labeled "not strategic enough." I’ve seen it happen to PMs who absolutely crushed delivery, but nobody above them really got what they were doing or why it mattered.

You don’t get promoted for being useful. You get promoted for being visible and driving outcomes that sound important.

what to do today: take your last project and rewrite the update to focus on business impact, not tasks. “We reduced churn by 10%” hits harder than “we rebuilt the dashboard.”

2. If your calendar’s a mess, your career probably is too

Back-to-back meetings, fires, random asks from stakeholders, grooming sessions, planning calls... then it’s Friday and you’re wondering why you havent done anything that actually matters.

Most PMs don’t block time to think, so they never look strategic. They just react all week and hope someone notices how busy they are.

what to do today: block 90 min on your calendar for “actual product work.” (the strategic thinking type) Literally label it that. Then protect it like your job depends on it.

3. Nobody really knows what PMs do (not even your manager)

You’ll get called a ticket writer, a mini-CEO, a project manager, a product owner, or release manager. Whatever fits the other persons mental model. Don’t take it personally, but don’t just accept it either.

Your job is to actively shape how ppl see your role, otherwise they’ll fill in the blanks for you.

what to do today: write down 3 things ppl expect from you that aren’t really your job, and 3 things you do that no one sees. Then figure out how you’re gonna fix that perception gap.

4. Influence > being right

You can have the best data in the room and still lose if nobody trusts you or understands what you’re saying. The PMs who win are the ones who can connect with ppl, tell a clear story, and make stakeholders feel like part of the process.

What to do today: before your next meeting, ask yourself what the other person actually cares about. Not what you care about. What they do. Then lead with that. A simple thought excercise is to ask - "What do I want them to know? What do I want them to feel? What do i want them to do with the information?"

5. Most PMs dont know what game they're playing

You’re heads-down shipping features, but... why? To get promoted? Change jobs? Get out of a bad team? Just survive?

A lot of PMs drift for years with no real plan. The ones who grow are intentional. They pick a lane.

what to do today: Write down what success looks like for you 6 months from now. Then compare it to what you actually worked on last week. If it doesn’t match, that’s your signal.

6. Roadmaps are meaningless without a narrative

You can build the best roadmap in the world, but if your stakeholders don't get how it helps them, they won't care. Most roadmap reviews are just a bunch of features with no story.

what to do today: explain your roadmap to someone not in tech. If they can't repeat it back in their own words, simplify.

7. Always being available makes you look junior

If you’re jumping on every ping, joining every meeting, saying “sure I’ll handle that” on every cross-functional thread... you look reactive. Not strategic.

You cant think long-term if youre always on call.

what to do today: cancel or decline one meeting this week that’s just noise. No one’s gonna notice except you, and you’ll get an hour of your life back.

8. Perfectionism/procrastination is often just fear

That doc you’ve been tweaking for 3 weeks? That spec you keep polishing? That message you haven’t sent yet? You’re not making it better, you’re avoiding feedback.

The best PMs I’ve worked with ship before they’re ready, then iterate.

what to do today: go into your drafts, pick the thing you’ve been avoiding, and hit send. Seriously. Just send it.

I could probably come up with more, but this post is already crazy long.

Hope it helps.

Curious if any of these hit home, or if there's one you totally disagree with.


r/ProductManagement • • Feb 02 '25 Helpful Bravo

My Advice on How to Be a Terrible but Valuable PM

1.9k Upvotes

One of the cruelest lessons I’ve learned as a PM is that success comes in two forms, and they rarely align:

  1. Being a Good PM – Driving meaningful impact on the business and its KPIs.

  2. Being a Valuable PM – Ensuring leadership sees you as valuable.

In an ideal world, focusing on #1 should be enough. But in reality, #2 often determines your career trajectory and job stability, regardless of actual impact.

I’ve spent the last 9ish years as a PM across six companies of varying sizes (nothing FAANG). I have no pedigree and I'm sort of an average joe. I’ve been fired, I’ve quit, and I’ve been laid off. I’ve held multiple PM jobs at once, mostly working remotely. The longest I’ve stayed in one role was 5 years. I've never had trouble finding a job and there've been no periods of unemployment that weren't voluntary.

I used to consider myself a solid PM, but I’ve become pretty detached from the "impact" part of the job and experimented the last few years with solely focusing on the "appearing valuable" part. I typically work 15-20ish hours per week. My salaries have ranged from ~$140K to $300K per role.

Tips on Looking Valuable as a PM:

  • Stay Positive. Always highlight silver linings, no matter how bad things are. Don't say anything negative about ideas, people, or companies. Period.

  • Focus on Vision, Ignore Execution. Incremental improvements grow a business but don’t grow your profile. Talk 90% about the uncertain future, 10% about the present.

  • Never Own Failure. If a product or feature flops, don’t walk it back, just kick it down the road. Identify some hypothetical point in the future where it could be successful and get everyone on board with it.

  • Signal Busyness. Occasionally mention how slammed you are. Drop a weekend Slack message on Sunday night about how you've solved some problem and how it's great to have some quiet time to work on it.

  • Speak in Big-Picture Terms. Constantly reference “high-level priorities” and a “cohesive product vision.” Push back on tasks that require effort by questioning alignment with the long-term strategy.

  • Prioritize Customer Meetings. The bigger the customer, the better. Take every customer meeting you possibly can. Make yourself and your company synonymous in their eyes.

  • Avoid Engineering’s Day-to-Day. There’s no upside in the weeds. Praise them, but stay out of their decisions.

  • Treat your Backlog as the Baseline Reality. Don't stress it and don't justify it. Just take an afternoon, put everything in whatever order you choose. If stakeholders disagree, put the ball in their court to provide compelling reasons to change it.

  • Don’t Overstep. If engineering, UX, or marketing makes a bad call, let them own it. If asked for a decision, defer back to them.

  • Exude Confidence, Not Uncertainty. If leadership asks for an 18-month roadmap, don’t hedge—just give them one. If asked for an impact estimate, provide a number, not a range. Doubt is a career killer.

  • Seek Low-Effort, High-Visibility Wins. Organize fantasy football leagues, facilitate “post-it” brainstorming sessions, or run Friday show-and-tells.

  • Find "Resets". Eventually, this attitude is going to catch up to you. Find opportunities to press "Reset" on all the promises made and the future you've spun. New leadership, a changing boss, new technology ("AI"), a new key hire, or a promotion all work. These are the moments that let you keep up the charade.

I'm no longer losing my sanity trying to make a product successful or trying to single-handedly build a productive product culture. I've got an amazing work-life balance.

Professionally, I'm completely dead inside.


r/ProductManagement • • Jan 04 '25 Bless Up Helpful

I outperform other PMs that are smarter than me whilst working and stressing much less. Here is how I work...

1.8k Upvotes

There are so many posts about imposter syndrome, confusion, feeling lost and burned out. The common patten is to do more and care more. This positive feedback loop will only make things worse.

I am a principal IC in a Fintech Unicorn and typically work in companies with roughy 30 to 50 product managers. I pretty much always outperform other product managers by the companies agreed success criteria, whilst stressing less, doing less and having more fun. I am not smarter than them, I am way lazier.

Here are some bullets on how I like to work. It has served me and my direct reports well. If you're struggling, I hope there is something in there for you

  • I only ever agree to targets I am 90% sure I will hit within 50% of the time allotted. I will oversell the complexity of what we need to do and massively over deliver.

  • I try to only work on very fertile problem spaces that are within my circle of competence. If I am being asked to work on something outside of this, I immediately say it would be a waste of time and recommend a different PM.

  • I really really guard my time. I don't attend meetings but I ask for a summary of what was discussed. Mostly, nothing was discussed.

  • My sprints always start late. I refuse to spend dev resource on anything that I am not very confident in. Too many PM's have a huge cathartic release once a sprint plan is agreed, and then a week later stress about what to work on next. They end up with a bunch of filler tickets. Over and over I tell engineers that I cannot promise them a ticket-factory, but I can promise I will never waste their time. This is very well received.

  • Don't try to sound smart. I can tell who won't make it through probation by how many buzzwords they use. I speak simply so everyone can understand. That way, when I am being dumb it is clear and can be challenged and corrected.

  • I only ever have a rough idea of what is going to be worked on two sprints from now (at best).

  • The few things I care deeply about and never compromise on:

    • Excellent test design.

    • Absolute minimal build time

    • Spending most of my time pairing with the designer and thinking through second order impacts and reasons for every change.

    • Post-test analysis

    • Understanding the highest impact levers

  • Spend a lot of time spend playing around with other products and scanning through Mobbin.

  • I spend time making my team feel that they are driving our success. I praise everyone publicly, no matter their contribution level constantly. I send their managers positive feedback when they do something good. In turn, they work very hard and they trust me.

  • I use speach-to-text AI for 90% of coms. Why waste effort?

  • I avoid doing work outside of our scope until our targets are hit at all cost. I make sure devs do the same.

  • When I have a problem, I inform my boss immediately and that I am on it. You need freedom to do well. To get freedom you need trust which is earned through results and responding to challenges in public. If the problem snowballs, you will also be very glad they were brought in early. The problem will feel shared.

So, If you are not having fun being a PM, consider:

  • Setting goals you could actually hit

  • Focusing on impact at the expense of sounding smart, hitting artificial timelines and picking up other work

  • Praising your team

  • Doing less


r/ProductManagement • • Aug 27 '24

I just...stopped doing anything

1.4k Upvotes

Friends. I've been running an experiment. I work as a product manager in a fully remote company. All attempts to do anything that resembles product management have been undermined by executives who just want to tell teams what to build. It is a feature factory, and everyone is death marching while the company lurches along, not growing.

After one particularly disheartening day, I just decided to stop doing anything. My team is rebuilding an app that already exists (don't ask me why, I still don't understand) so the project doesn't need me. So, I just attend meetings, and don't really do anything else. It's been 2 months. Nobody has noticed.

In fact, all I've heard is how pleased everyone is with the work I've been doing. It's insane. On the one hand, it's nice not to have the stress and pressure. On the other hand, it's mind-numbing.

Anyone else experienced this?


r/ProductManagement • • Aug 09 '21

9 lessons from my 10+ years working in product (long post)

1.2k Upvotes

Here are what I consider the most important lessons I've learned over the years working in product management. Each point is described in more detail below the list and I tried to keep it as practical as possible (even including suggestions of one concrete action you can do today for each point).

  1. Always separate the problem from the solution.

  2. Most people do not understand what your job is.

  3. Learn how to adapt because real life is different from what they teach.

  4. Your team is the most important factor for success.

  5. Learn & improve from everyone & everything.

  6. Get better at communicating.

  7. Be nice to yourself.

  8. Consistency over intensity.

  9. Don't be a perfectionist.

It's a long post and you may not feel like reading it (at) all. If there's one thing that I think will make a difference it is the first point (problem vs solution).

1. Always separate the problem from the solution.

  • It's natural for us to jump to how to solve something before understanding that "something" really well. It may work for evolutionary survival but not so much for product management. Most users, clients, stakeholders, developers and even product managers often fall into this trap. It will happen on all levels - from discussing a startup idea to a portfolio strategy and even at a small feature level.

  • Assumptions are the cancer of product management. It's really hard to avoid them because our brains are hard-wired to do so. Question everything and get hold of the data when you can.

  • Talk to your customers and end-users. Talk to everyone involved in the subject you're researching. If you're not talking to your customers / end-users very often something's definitely wrong. It may be very tricky to do so in your particular situation but try to figure it out. Bonus: your life will probably become a lot more interesting.

  • Ask "dumb" and obvious questions, all the time. Don't stop asking until you know enough so that you can explain it back to a 10 year old kid. This is important for all phases and not just research.

  • Write things down - or better yet - draw them. It's much harder to bullshit yourself when things exist outside of your head.

  • For solution - define the desired outcome ahead and decide on how you will measure it (then measure it). This is SO MUCH harder IRL than you'd think. "Outcomes over features/solutions" is luckily a pretty big theme in PM these days so I decided not to expand it here. Study this if you're not already familiar to it.

  • One thing you can do today: pick something you're working on, small or large, and break it down (write or draw!) into defining the problem from the user's perspective (why is this making their task harder, e.g. need to look at two reports to make a decision) and what the outcome (not solution!) would look like (e.g. being notified with all these required data pieces at the time when I need to make the decision). Only once you're happy with this start thinking about the actual solution (e.g. new report generated in the BI portal).

2. Most people do not understand what your job is.

  • It's not just your family. It's very likely that other parts of your company - and even your team - do not have any idea what you actually do. It's a lot more common than most PMs realize. Confusion about product titles (PM, PO, BA, UX..) is just the tip of the iceberg. Most people simply do not understand what product management is and make an assumption that fits into their model, for example take you for a "specs writer", project manager, team lead, middle management, etc.

  • You have to advocate for yourself, your team and your function. A good product culture can only exist if other parts of the machine understand what you're trying to achieve and play along. As every situation is different you need to figure out what does the product function in your company look like and how you can best add value.

  • One thing you can do today: write down expectations other departments or people have from your role and what you/product needs from them (I use a template spreadsheet for this - lmk if you need it and I'll share). Bonus points if you reach out to discuss the findings together (remember assumptions?)

3. Learn how to adapt because real life is different from what they teach.

  • It's useful to read books and listen to presentations but they can't usually be applied to your situation as-is. There are no silver bullet solutions.

  • Challenge the advice you get! Does it work in B2B as well as it does in B2C? How would this apply in my highly regulated domain? What is the background of the person giving the advice?, etc. The internet is flooded with SEO content and every time I open another shallow keyword-ridden article by someone actually promoting their service or product - and bringing zero value to the reader - a small part of me dies. This is much more common in the product management domain than I would like.

  • Agile, Lean, Scrum, SAFe, etc. Unpopular opinion: it's better to have a well working waterfall process than a dysfunctional agile one (and I hate waterfall). Study frameworks and experiment with them but be wary of following them to the letter! Every good framework I've seen applied in practice has been heavily modified to work best in that given situation. I spent way too much time early in my career drawing processes on the whiteboard rather than actually experimenting with them IRL.

  • Always think what is it that you're actually trying to achieve. For example, you're working on a roadmap presentation - your goal is not to finalize the slides but rather to communicate your plan for features ("it's actually outcomes" I hear Marty shouting from the back) effectively to your audience. Try to figure out afterwards if it worked and if you were even solving the right problem to begin with (maybe they wanted to get a release plan or hear about your strategy instead)?

  • Understand where in the product journey you are: playing around with an idea that could grow from a side gig to a startup is different than innovation at an enterprise company and altogether different than trying to think of how to scale up an existing solution or ... (you get it). Books and articles often ignore this as they want to include everyone. This has always baffled me.

4. Your team is the most important factor for success.

  • The more projects I completed the more I realized the importance of having a good team. It's scary because you can't usually decide who you work with and if you can then you know how hard it is to find reliable and capable individuals who will fit into your org.

  • Communication skills and culture fit are almost always more important than technical competencies. Look also for curiosity, capability to learn quickly and just being nice to others.

  • For example, if I'm deciding between two candidates for a job (any area) and one is 10/10 in the specific skills for the job while the other is 6/10, but the latter fits better in the team then they have my vote.

  • Ultimately this comes down to a couple of things: hiring, building culture, improving how you work within and outside of your team and conflict resolution. All of these are really really hard but make sure you do not neglect thinking what you can do to improve in this area.

  • One thing you can do today (this one was hard, let me know if you have other advice!): Think of a short interactive workshop you can run with your team (we did one 1.5h long workshop the other day and it was amazing). The team will learn how to better work with each other and you may get more data points on specific issues you are already aware of.

5. Learn & improve from everyone & everything.

  • You can learn equally from good and bad situations. I was lucky enough to work with some really bright individuals and I've learned a lot from them - but I was also "lucky" to cross paths with some really difficult people and I've learned a lot from them too. Once I worked for over a year on a product where everyone was great but the product failed completely. Things are never black and white and your mindset should always be set to take away something useful out of every situation.

  • Don't be afraid to make mistakes - but learn from them. When you identify an area you'd like to improve in find a way to fail safely and quickly. I learned how to do this at my work and then transferred it to my private life too.

  • One thing you can do today: reserve a block of time weekly to work on this and do not surrender the time. Use the time to read, do a course, think about what areas you need to invest in, what changes you can try in your current work.

6. Get better at communicating.

  • It's simple (but not easy): learn how to communicate effectively. The better you will communicate with other team members, your boss, stakeholders, clients, marketing folks etc. the better outcomes you will achieve.

  • Assume (I know, no assumption, but this one is worth it) that only 20% of what you wanted to convey in any conversation is actually understood by the other person. And they will likely forget even most of that quickly. I've heard this somewhere and it stuck with me: "Tell them what you're going to tell them, then tell them and finally tell them what you've told them".

  • You will need to apply different communication styles for different people (or groups of people). Learning to do this well is as much as blessing as it is a curse - as you will get progressively frustrated with noticing bad communication patterns everywhere!

  • Write things down - ideally in shared documents! I got into the habit of regularly documenting discussions and it has helped me (and my teams) a lot. Emphasis on less is more! I will usually have one shared document for each person I regularly interact with as well as one per team and will document a couple of bullet points after each discussion we've had.

  • One thing you can do today: create a new document and write a couple of bullet points summary from your last meeting. Forget meeting minutes, just focus on two things: which conclusions were reached and which action items were agreed.

7. Be nice to yourself.

  • PM is not a cookie-cutter profession. In order to be successful you have to continuously put yourself out of your comfort zone. You will mess up a lot so go easy on yourself. Finding a good balance with this is much more important than the working vs non-working hours balance.

  • If it gets too hard figure out how to leave. I know this advice is common but much harder (or even impossible for some) to execute in real life - everyone has their own unique situation. I have however observed that most people will wait longer than it's healthy for them and they usually realize this only after they've finally moved on.

  • I find that a lot of people in tech have a feeling that they're not working on anything really important and it bothers them. Richard Feynman wrote that "no problem is too small or too trivial if we can really do something about it" in his beautiful "Do not remain nameless to yourself " letter to a former student, it's a short piece well worth the read.

  • Another unpopular opinion: luck plays a massive (usually biggest) part of any success. Learn about survivorship bias and then take any advice from any successful individual with a grain of salt.

  • Another fairy-tale that successful PM authors claim is that you have to be passionate about your product. In my experience being passionate about what you work on is a luxury that most can't afford. At the end of the day it's (usually) just a job - but do what you can to find joy in it and the more excited you can get about your product the easier it will be to drive a good outcome.

  • No homework with this one :)

8. Consistency over intensity.

  • This is more than just a motivational poster at your local gym. I would urge you to use it with any advice from this list and in general.

  • Working with groups of people is hard. Introducing change is hard. Juggling many things at the same time is hard. Do a little of it every week instead of one intense workshop every quarter.

  • One thing you can do today: schedule a recurring task/meeting for something you know you(r team) should be doing regularly and you just never find the time for it.

9. Don't be a perfectionist.

  • Just finish the damn thing. It's almost always better to "release" an unfinished thing than leave it forever in the drawer at 80% done. Release here doesn't mean ship product to customer (although it can) but basically applies to anything you're working on and means finish even when you know it could be better if you put more work into it.

  • You will learn and improve a lot more this way. There's nothing stopping you improving it in the future but don't count on it. It took me a long time to figure this out. Even if this doesn't apply to you it probably applies to someone in your team.

  • After recently complaining to a friend how hard delegating work is he told me to pull my head out of my ass and think hard of what's the worst thing that can happen. It's likely that everything will be completely fine even when someone else's output isn't completely up to my standards.

  • This Reddit post is pretty much the first piece of serious writing I published on the internet ever. If I followed my advice I would be sitting on hundreds of blog posts and a book deal by now.

  • One thing you can do today: set a fixed time and finish that document / spreadsheet / diagram (you know which one I'm talking about it) and send it to someone. It won't be perfect but it will bring a lot more value than sitting in the unfinished folder.

Finally - since this didn't fit elsewhere - take risks and stay humble.

If you're still reading - thank you and I hope you got something valuable out of it. If you have any suggestions on how to improve it please let me know. In the future I would like to include links with reading/watching material for each of these points so your suggestions would be very helpful. Thanks.

EDIT: a couple of people have reached out to me asking about the template I talked about in point 2: Most people do not understand what your job is**.** -----> I now posted the template in another Reddit post here.


r/ProductManagement • • Apr 01 '23

My Ultimate Visual Guide to the Best Books for Product Managers (OC)

Post image
1.1k Upvotes

r/ProductManagement • • Oct 31 '22

My Halloween costume at work this year was Scope Creep

Post image
1.1k Upvotes

r/ProductManagement • • Dec 21 '21

Product management is becoming cringe

944 Upvotes

Is it just me or is product management becoming a cringe field. Especially on LinkedIn and Twitter. You know the type. Generic tech bro wannabe "thought leaders" endlessly circle-jerking themselves about frameworks and strategies discussed in the latest business self-help book. Most discussions about product management are about how product management is such a "hot field" and discussing why product management is so awesome rather than discussing product strategy itself. It often strikes me as a deeply "bullshit" field in the technical sense of meaningless corporate jobs (see the book "Bullshit Jobs".) Sometimes it seems there are more product managers building products/schemes to help product managers get into the field of product management than there are actual product managers.

These "thought leaders" listen to Tim Ferris and every other productivity guru and fancy themselves the next Steve Jobs, or Marty Cagan. Yet these high-flying theories are usually just bullshit idealism that never gets actually implemented in the real world, which is much more messy and human than some idealized PM framework that I've never actually seen actually implemented except insofar as there is some hollow mechanical shell for "going through the motions."

Product management is the new "agile" (or worse, SAFE). It's often empty, meaningless hype driven by consultants and schools and the cottage industry of courses, books, and certificate programs.

Let's be real with ourselves. We are not the heroes of the narrative. We are not the CEOs.

Lest you think I am too pessimistic, we are not irrelevant. There is value in the role of the modern PM. But can we not be so cringe in thinking ourselves these deep strategists saving the company? Almost all the value of the PM comes from being a SME and a good communicator, rather than some expert on "product strategy." Marty Cagan is selling a luxury, not a day-to-day reality for most PMs.

I recognize the tone of this rant is a little harsh. And I'm being slightly tongue-in-cheek. But I feel like there is a silent majority of product managers who don't work in FAANG companies that treat PMing as just another corporate gig, not some Savior role. I would be nothing without my dev teammates, but my devs would probably get on pretty well without me. That gives me a real sense of humility I see lacking in so much PM discourse online.


r/ProductManagement • • Jul 29 '25

Steal my 1-1 format. I've been told it's awesome.

912 Upvotes

I hate it when 1-1s become only about the work. I'm a people person, I want my people happy & motivated -- this is when the trust is highest, the collaboration is smoothest, and the productivity/quality are best in class.

Here is how I do it, my team loves it, we do it in 30-45min typically.

First: 4H's check in:

  • Outside of work: How's your Home/Health? Is anything stopping you from bringing your best to work?

  • Inside of work: How are your Happiness/Happenings? Is the quality and amount of work right for you? Are your goals moving forward enough?

Why this works: Sometimes life happens, it's great when you know that so you can adjust expectations and create a human-first work environment.

Next: Top Topics:

  • Pick 2-3 things that are critical to discuss and you need feedback/input about.

    • "Let's set our agenda. Today I'd like to dig into {TOPIC 1} and {TOPIC 2} with you, what can help you the most today, any topics on your side?"

Why this works: Doesn't require a ton of prep, keeps the conversation focused on what you both want to get out of it.

Last: Wrap up:

  • Always leave with next steps that set a clear expectation:

    • Who

    • does what

    • by when

  • Red flag if you have more than 5, tone it down.

*Edit: a few mentioned valid points I want to make sure get seen…

  • What if you don’t want to share personal info in any capacity bc you don’t trust the manager?

Do not share info if you don’t feel safe. Just tell them all is good. Find safe spaces to share instead.

  • What if you as a manager don’t want to ask your team anything personal?

In that case, just focus on asking if there’s anything that will impact work instead of asking, is your personal life impacting anything at work. I like to ask about their 🔋 battery levels. Anything below 30% is a red flag.🚩

  • What do you do if your person says that they are not OK?

Accept that people who are not doing well are going to underperform anyway, so you might as well align the work to where they will perform better and win trust and rapport With your humanity. Here are my steps to stop expecting optimal performance and adapt to the person’s context…

  1. Reduce workload: either kill projects or find others to balance the work the person is not doing. This is something to do immediately when someone says they are in the red and can’t function well.

  2. Easy mode on: orient work towards things they like to do and are naturally very proficient at. This is the worst time to stretch them.

  3. Set the rules: some people will take advantage of your empathy, so make sure they know that this context is not permanent and the employee still has to deliver value long term. Be clear on what the min-viable performance is for the role & level. If the long term context prevents this, then you will be happy to adapt the role/level to one that fits their life better; know what those options are before this convo.

Don’t do all 3 at once, and do #3 if there is a real risk that the person can’t do their job long term.

Commenters also mentioned offering other support methods, leave of absence and other solutions that were great.

What does your 1-1 agenda look like?


r/ProductManagement • • Apr 15 '26

Aakash Gupta tried to justify his false claims, gets called out again

Post image
903 Upvotes

r/ProductManagement • • Apr 19 '21

This is so common!

Post image
895 Upvotes

r/ProductManagement • • Aug 16 '24 The Best Take My Silver

My complete application & submission at a director role for Miro in 2021

877 Upvotes

Hi, my name is Leah,
and I applied in 2021 for a director role at Miro, here's all the details and how I would evaluate myself in 2021

Edit Addition: I did not expect that reception in here. Please do not consider this submission the standard or even a good submission for that Job. As some commenters have already expanded this was weak especially at the end and I agree. Unfortunately I cannot recall exactly what i did say or whether I expanded a lot of context, it was important to me to not alter this now so consider this is as a realistic submission exactly as it was back then. Including it's weaknesses

Context

(I made a 25-minute video on the complete Miro Application process for Director of Product (for the Whiteboard) explaining in detail the task and my submission. You can find it easily on the 'ProducTea' Channel for more details)

Three years ago, I was approached by Miro (at the time ~1500 people), because they were looking for a Director of Product for their flagship, the whiteboard. This is the process that got me to an offer.

I was working at Smallpdf at the time leading the core product and happily listened to what they wanted me to do since I love the problem they were solving.

The Strategy challenge:

- "How to get from 3mio weekly active users to 25mio weekly active users in 4 years with the Whiteboard."

I had 15 minutes to present something by Loom. This was all the info I had; I spent about 4 hours on the exercise before I submitted my answer, which led to subsequent interviews with the CPO at the time.

The following screens are from the Miro board I used to present my homework. I don't remember the exact details of everything, but I try to recall it to the best of my abilities.

Structure

Market segmentation

The first step is to go to Google or your favorite LLM and get an overview of the market. There’s really no more excuse not to do that, especially with AI tooling making it so easy for you.

The Compound Annual Growth rate (CAGR) is not that important, but you pick a market that is appropriate for the company you’re applying for.

For instance, since I applied here for a director of product, it would be wrong to focus on an extreme niche market inside whiteboarding that is just way too small. (For instance, Whiteboarding in a corporate environment in Germany)

You can alternatively also ask this back before you solve the challenge with an assumption: “Before I start diving into this, I was thinking about framing the challenge around the market of ‘blabla’, is that ok?”

That gives you confirmation that you’re on the right track without too much effort.Competitor Sweep

Understand who the main competitors are. Again, this is simple with LLMs, but I would do one thing differently in a submission at this level:

A use case competitor for Miro would be, for instance, a physical meeting where people meet together and draw on a physical piece of paper to achieve the same outcome.

Direct product competitors are still interesting to understand, but in that case, we focus our acquisition efforts on how to move professionals from one tool to another one where differentiators around quality and expanded value and price usually matter much more.

What was good from this was that I looked into the Wedge Market (how to get your foot into the door) and that I made assumptions on how this market would develop with a conviction that going upmarket is the thing to do for Miro, in retrospect that bet was correct. (but not well explained)

The world map at the top left looks cool and is totally useless for anything.

The actual competitor listing, though, was thin and not sufficient. I would not hire a director on the basis of this with what I know today.

ICP Assumptions

Make Assumptions on ICPs for Miro, in a product-led business do it on Use Case rather than firmographics. What is someone doing rather than how does the company look like they are in.

The more sales-led the business (or your area of influence will be), the more you focus on firmographics. For instance, if the expectation is to support a sales organization with what you’re building in your product, then ignoring firmographics shows that you lack experience in understanding how Sales work. At a director level, it is reasonable to expect that you know how that works.

It’s nice that you solve problems, but if the account sizes are not above what they want to sell, you just disqualify yourself.

Some jarring claims in here especially around churn and overall not enough meat on the ICPs. Highlighting the use cases was good and I still would do that today. MIxed feelings :D

Big Bets & Short term bets & Acquisition

The conclusions on these I would still sign today, and in retrospect, I'd wager I was correct. The whiteboard industry hasn't fundamentally changed all that much since then, and innovation seems to be stuck. I also know now more than ever that changing interfaces and testing hypotheses in big companies like these are extremely jarring if you go against learned behavior.

Try giving a tool of that size a face lift without wrecking your carefully optimized revenue. It's extremely stressful and difficult at the same time for any product leader.

In this section I dove into more conclusions and some recommendations. In general mark where you have ideas from like I did here, no one expects you to know everything. I still use Outcome driven innovation till today.

The bet at the end that they should go horizontal is not only a bold claim that doesn't follow from the assumptions before, but it's, above all, also completely wrong. Verticalization would have been the correct play, and this was also known from the available data back then. Not sure what I was thinking there. The biggest weak point in the entire presentation.

Levers & Altitude Maps

People jump way too fast into their solutions when they solve exercises. The first 3 points were all about setting the stage and describing what your solution will be built on.

This is important for an obvious and less obvious reason:

  1. It shows that you did your research and spent time on the company and its solution.

  2. If you make mistakes in your conclusions (and you most likely will) it is clear why you arrived at that point.

This happened to me when I applied for a Head of Product role in a high-tech company in an exercise in an embarrassing way. I misread a challenge completely and didn’t catch my mistake until I presented the case because someone told me that my assumptions are wrong after investing 4 hours of work into it.

But because I outlined my assumptions in detail and what they meant the fail was not as heavily damaging my presentation. I was able to at least showcase what I did with the information and they didn’t hold it against me in the end.

It happens.

For instance:

I still use this structure to this day. It shows that I know about OKR’s, use KRs that are outcome driven and that I separate the deliverables from the rest.

An altitude map is a powerful tool to show how you think the company works. This is an outcome from your market research, the ICP’s use cases etc.

My Altitude map:

Oh Nelly, too many colours. What did i do???

The principle is still ok but this altitude map is too complicated for a director role. A simpler one would have helped as well. I tried to be overly specific here which was also informed by my role at Smallpdf of course where I was heavily in the operative details at the time.

I leaned too heavy into this one

Less would have been more here, but overall, it’s powerful to show how you think things are connected and what YOU would influence to move this metric.

That way, you can also acknowledge that there are other silos in the company affecting these metrics in a meaningful way and not just you. A good trait for a product leader to have.

This is something that I didn’t do well in that submission.

As a product leader, you’re a cross-functional leader, and opportunities that are just living in the product are usually not as powerful as those that you can influence across the silos.

The process to my suggestions is still something I use a lot, the IPA Framework where we try to evaluate whether something is Important, has potential to be improved and also have authority over to change is a neat trick that always works no matter the seniority.

The final submissions were some OKR examples. While they are ok they are too fuzzy and high level, but show that I at least knew how to structure such a process.

There’s one more thing that I would include today as a product leader at scale and that’s how to build teams. I did not submit anything about my operating model, how I structure teams, or what my convictions are.

This came with experience, and I have very specific rules I do not break, such as team size, the role of PMs / EMs, how they fit in at different scales etc.

I’ve written about these at length in my guides, but I feel like it’s important for you to show how you think about an organization and how to structure/scale your teams. As I started to manage and advise bigger corporations, I noticed that the weakness happens very often at this particular layer.

My experience in solving this problem is just as much a part of the answer in how to scale a business as is the product strategy itself.

Overall my submission was too much from the perspective of a principal Product Manager and too theoretical.

And that’s how I applied for a Director role at Miro, I received an offer back then after talking with the CPO Varun a couple times which I rejected because the comp didn't match what I wanted, and they wanted me to move to the Berlin office which did not align with my life plans. In fairness I also think it was mutual since I gave off defensive vibes when it came to their design challenges.

I had fundamental disagreements about the operative involvement of how much a Director should be involved in the design process (plus I felt I sucked at their design challenge) of the product so we decided to not get together.


r/ProductManagement • • Apr 14 '22

Whenever someone asks me what it's like to work in Product Management.... Spoiler

865 Upvotes

r/ProductManagement • • Apr 13 '26

PM coach spreads interview fearmongering, Google director calls it out

Thumbnail
gallery
857 Upvotes

r/ProductManagement • • Apr 19 '26 Bravo

Tools & Process How I use Claude Code as a Product Manager

Post image
846 Upvotes

TL;DR: I’m a PM who somehow ended up spending most of my day in a terminal and VS Code — and I don’t hate it. A few months with Claude Code turned into a full personal AI work system: connected to databases, Slack, Notion, Gmail, Metabase via MCP servers. I’m now running simulations and data pipelines I genuinely couldn’t have done before, with no CS background. The real unlock was what I built around the AI — a custom memory system, a skill library, and a /akash skill trained on my own thinking style that gives me a second opinion that actually sounds like me. Almost didn’t start because it felt too technical. Once the first real workflow clicked, I just kept going.

Something hit me recently. More than half of my working day now happens in a terminal and VS Code. I'm a Product Manager. That's not supposed to be what my days look like.

But I've been using Claude Code for a few months now and things have kind of drifted in that direction, and honestly I don't mind it anymore. What started as me trying to get some data analysis done turned into building an entire work setup: workflows connected to databases, Notion, Slack, Gmail, Granola, Metabase. There's something called MCP servers that lets you plug all of this into one place, and once you set it up it starts to feel like the tools are actually built around how you work rather than the other way around.

I've been doing data science work that I genuinely wouldn't have been able to do before this. Simulations, analysis pipelines, crunching operations data across hundreds of thousands of records. I don't have a CS background, never properly learned to code. But I've been close enough to technical work for long enough to understand what needs to happen, and Claude Code became the bridge between understanding something and actually being able to do it.

What I think actually makes it useful is what you build around the AI, not just the AI itself. I have a custom memory system now where each session saves what worked, what went wrong, what decisions were made. I created something I call /session-learnings that goes through the whole conversation and stores everything into the project's folder. Each project has its own context and history so the next session picks up where the last one left off. I have hooks that fire when I'm giving feedback or catching something wrong, so corrections actually carry forward instead of getting lost. Git tracks everything.

I also have a skill library at this point. Skills for pulling data from our databases, for building dashboards, for writing analysis documents that go to leadership. Some of them run agents in parallel, splitting a problem into pieces and working on each simultaneously, then combining the results. It sounds like a lot to set up but you just need to get started and work with Claude Code to build what works for you.

The one I keep thinking about is something I call /akash. It's a skill I've been slowly training on my own way of thinking. My analysis framework, how I structure decisions, how I frame things for different audiences. When I'm about to finalize something, I sometimes run it through /akash first, or just ask it what would I do here. It's a bit of a strange thing to describe but it works out to something like having a second opinion from someone who has read everything you've written and paid attention to all of it.

I almost didn't start any of this. I kept convincing myself that Claude Code was too technical, that it was built for engineers and I'd spend more time confused than productive. I was using ChatGPT for most things and it was fine for writing and quick questions, but it had a ceiling. It couldn't connect to anything real, didn't know my context, and every conversation started fresh. I kept running into things I wanted to do that it just couldn't do.

Eventually I got over the hesitation and tried Claude Code properly. Once the first real thing worked, a workflow that actually pulled from production data and gave me something I could use, I just kept going.

I want to write about what I've built and how it happened, for people in similar roles who are wondering whether any of this is actually worth the time. Not because I have it all figured out, but because I spent a while looking for this kind of writing and mostly couldn't find it.


r/ProductManagement • • May 16 '25

Expectations of PMs in today's market

Post image
831 Upvotes

Just saw this post on LinkedIn and interested to get people's thoughts on it. As a PM with 12 years experience I read this and laughed. What's in your prompt library? Give me a break. But there are a lot of people agreeing with the sentiment of the post and it got me thinking about this kind of stuff. I'm a PM with a computer science background but I haven't written a line of code in years. My job is strategic and user-focused I'm not spending time writing code or automating my role because I don't do monotonous stuff that needs automating. Also this crap about passion projects, with what time? I work 50 hours per week and the rest of my time is for me, not spending more time in front of the computer playing entrepreneur.

I have started using AI tools mainly for things like prototyping or just condensing my thoughts into slides etc. but that's not the kind of thing this guy is referring to here. Are PMs now starting to do all this kind of thing and I'm deluding myself in how the role is maturing? Or does this guy belong on LinkedIn Lunatics?

Genuinely interested in getting actual PMs thoughts on this.


r/ProductManagement • • Jul 10 '25

I messed up my Google PM Vibe Coding Interview

767 Upvotes

I had my 2nd round of Google PM interview yesterday after doing well in my first round and was totally blindsided by the format. I had no clue there would be a vibe coding interview—I was expecting a traditional PM interview, but that didn’t happen.

During the interview, I ended up being very unstructured. Having built AI applications at my own startup, I know the pitfalls of every tool out there, and in these situations, the main bottleneck is the backend. So, I focused all my energy on the backend during the interview.

What I should have done was approach it like a product design interview: prepare a small PRD, use that to create a prompt, and then maybe run it in something like Firebase Studio, Lovable, or V0. Instead, I jumped into building my Langchain backend agent first and completely messed up the code for tool calling in Langchain. I was stressed and just blanked on the exact implementation.

My biggest regret is that, if I’d even had the slightest clue about the format, I would have come in with a structure prepared. I just didn’t manage my 45 minutes well. The knowledge was there, but the execution was honestly pathetic. Not sure what else to say—I guess I just needed to share.

Deep down, what’s making me feel worse is that I don’t have too many opportunities—if I mess up the ones that come, it feels like I’m done for, especially since there are limited opportunities in India for AI jobs.

Edit 1: Another reason for posting here is anyone who is planning on interviewing for a similar role knows there could be vibe coding interviews. In all my research I didn't find any mentions of a vibe coding interview, so hopefully this knowledge will help someone else in the future.

Edit 2: I was interviewing for an L5 PM role (the JD mentions strong focus on AI/ML) so it is an AI PM role.
Also the aim of the post has not been to garner sympathy (although I appreciate the positive and supportive comments), my aim was to solely narrate what the interview experience was like and what I could have done better.


r/ProductManagement • • Oct 29 '24

Any ideas why the Product People of <insert any steaming service> think this is a good idea?

Post image
767 Upvotes

r/ProductManagement • • Nov 14 '23

I used to be terrified of meeting with execs. This is my best advice for PMs.

Post image
743 Upvotes

r/ProductManagement • • May 22 '26

I am so tired of this bs

Post image
734 Upvotes

It’s baffling how out of touch these people are.
Oh you just got laid off because zuck’s new strategy is to use employees as training data generators for his coding models and you’re not an engineer?
Go pay for Lovable using this handy sponsored link.


r/ProductManagement • • May 22 '25

The unspoken rule of career growth that no one talks about.

722 Upvotes

I’ve been working in product for about six years now, currently leading a couple of squads at a fintech focused on payments. Most of my days are packed with meetings, trying to balance short-term delivery with longer-term planning, putting out the occasional fire with engineering, and making sure legal doesn’t hate us. You know, typical PM chaos.

There’s something I wish I’d learned earlier in my career: you don’t get promoted because you’re doing your current job well. You get promoted because you’ve already started doing the next job.

When I was a mid-level PM, I thought if I just kept executing cleanly and kept things on track, someone would eventually say, “You’re ready for senior.” But that moment never really came. I got good feedback, sure, but nothing changed for a long time.

What actually moved things forward was when I started acting differently. Not because I was told to, but because I started noticing problems no one else was fixing. I began flagging misalignment between teams and working across squads to fix it. I sat down with finance to understand the impact of our pricing model beyond just churn numbers. I helped newer PMs get onboarded and navigate our messy internal systems, mostly because I remembered how confusing it was for me when I started. I started thinking more about outcomes than outputs and challenged priorities when they didn’t make sense, even if that meant some awkward conversations with leadership.

Eventually, my manager said something like, “You’re kind of already doing the senior PM job,” and the title came not long after. But by that point, I’d been working at that level for months.

The same thing happened when I started moving toward leadership. No one gave me a formal nudge. I just started doing the work an d helpin other PMs think through problems, organizing knowledge that was scattered, bringing visibility to issues across squads that weren’t getting enough attention. The title came later.

So if you’re early in your PM career or even mid-level and wondering when your “next step” is coming, this is what I’d say: don’t wait. Promotions tend to come after you’ve already made yourself undeniable. Do the job before you have the title. That’s how people start seeing you as someone who’s ready. And once they do, it becomes hard for them to ignore it.


r/ProductManagement • • Oct 03 '22

Tools & Process Never stop listening to your users

Post image
704 Upvotes

r/ProductManagement • • Jul 26 '21

[Funny] What does a product manager actually do?

686 Upvotes