Advice to a new TPM? What are some common mistakes new TPMs make?

Answer

4 Answers

Technical Product Management

Vasanth Arunachalam

Meta Director, Technical Program Management | Formerly Microsoft • 4y

I talked about my take on desirable qualities in one of my previous responses, so I’ll focus on the common mistakes I’ve personally made in my career in the past, that hopefully will help others avoid those pitfalls. Mistaking motion/effort for progress (This is also one of Meta’s posters on the wall in our campuses) Rushing to prove my value (whenever I switched roles or teams). Not being able to articulate the “So what” well. Eg: I’ve launched this shiny new feature, so what? Assuming everyone ...Read More

3,687 Views
Deepak Mukunthu

Salesforce Senior Director of Product, Agentforce AI Platform • 3y

Based on my experience, here are some common mistakes I've seen new TPMs make: Focusing too much on features and not enough on customer needs: It's easy to get caught up in building new features, but it's important to remember that the features you build should ultimately solve customer problems. Not prioritizing effectively: New TPMs may struggle with prioritizing effectively, leading to delays or features that don't deliver the desired impact. Lack of communication: Not communicating effective ...Read More

1,407 Views
Devika Nair

Oracle Director of Product Management • 3mo
The biggest mistake would be to solution things before listening. Listening is key to success.
- Listen to your customers to identify what they want.
- Share your requirements with team members, engineering partners, leadership. Listen to them and identify what needs to be done clearly.
Once that is clear, map to your strategy and goals to see whether its the right investment for your product
369 Views
Milena Krasteva

Walmart Sr Director II, Product Management - Marketing Technology • 4y

Many common mistakes stem from haste without deep knowledge and mindless GSDing. Not thinking through the problem statement fully or not knowing enough about the domain and becoming married to 1 solution - often yours. Taking it personally when told that something is missing from your solution Resisting talking to users or stakeholders who are likely to disagree with the solution you have picked Picking a solution because an exec imagined it is the right one is not necessarily the right thing ei ...Read More

358 Views