1. Thinking "effort" = development time
Let's say you revamp a core flow in your product e.g. Sending an email campaign in marketing tool.
Development is just part of the cost.
Creating new training, redoing videos, updating product tours, changing tooltips etc. add a great deal of overhead that can change their status in your prioritization framework.
2. Succumbing to the Hippo
Hippo = highest paid professional opinion, usually the man who pays the bills.
Don't get me wrong. The Hippo knows a lot. However, one person's opinion is as strong as their weakest assumption.
3. Forgetting to contextualize data
Noticing a declining trend but not investigating the "Why" and thus, prioritizing a fix for the symptom, rather than the root cause.
4. Thinking I'm the customer
Making a gut-based decision without even researching the customer's viewpoint to save time.
5. Allowing starvation
Letting certain important but low priority items like tech debt collect dust in the backlog for several months with no action in sight.
As a Product Manager, you might be asked a lot of questions during an interview. One of them includes technical questions. Here are 4 types of technical questions that you might come across.