Some lessons in Product Management come from courses, books and mentors.
Others come from making mistakes you sincerely hope you never repeat.
If there's one thing experience has taught me, it's that being a good Product Manager isn't about knowing all the frameworks or having an answer to every question.
It's about developing the judgement to know what to do, what not to do and when to push back.
Here are 8 things I'd never do again:
1. Build a feature simply because the CEO requested it.
I'd first understand the problem, the intended outcome and whether there's evidence that users actually need it.
Having an idea doesn't automatically make it a priority.
2. Start execution without understanding the problem.
I'd rather spend more time understanding what we're solving than rush into building something nobody needs.
A beautifully executed solution to the wrong problem is still a failure.
3. Promise delivery timelines without consulting the engineering team.
Product Managers should not make commitments on behalf of people they haven't consulted.
I'd rather communicate a realistic timeline than make an impressive promise the team cannot keep.
4. Treat every stakeholder request as an emergency.
Not everything is urgent. Not everything is important.
I'd establish priorities, understand trade-offs and communicate them clearly.
5. Confuse being busy with making progress.
More meetings, longer documents and endless Slack conversations don't automatically translate into better products.
I'd focus on outcomes, not activity.
6. Avoid difficult conversations.
Whether it's challenging an assumption, addressing delivery concerns or pushing back on an unrealistic expectation, I'd rather have an uncomfortable conversation early than deal with a bigger problem later.
7. Take responsibility for everything but have authority over nothing.
Product Management requires collaboration, but collaboration doesn't mean becoming the dumping ground for every unresolved responsibility in the company.
I'd establish expectations, clarify ownership and communicate boundaries.
8. Launch a product or feature and immediately move on.
Shipping isn't the finish line.
I'd monitor performance, gather feedback, evaluate outcomes and understand whether what we built actually solved the intended problem.
Because releasing something and creating value are two different things.
One thing I wish more people understood about Product Management:
Your job isn't to make everyone happy. Your job is to help the team make better product decisions.
Sometimes that means saying no.
Sometimes it means questioning the founder.
Sometimes it means changing direction.
And sometimes it means admitting that your original idea was wrong.
That's part of the job.
I'd love to hear from other PMs:
What's one thing you did early in your Product Management career that you would absolutely NEVER repeat?
