Think of it as anything you build: feature, functionality, or product, you are basically trying to change the behavior of your customer. When doing that—questioning how they behave, why they do it, what their motivation is, is crucial.

user research, understanding their needs and their psyche makes the biggest difference.

what the user is trying to achieve with your company’s product or service.

Timelines are always very important, but what you really do is look at the overall shipping goal and work backward from there. That will also help with deprioritizing items which may not be needed in the first iteration of the launch.

if you can figure out that your product will change the user behavior and you can predict it without an ML model—then you’ve nailed it.

Think of how you can solve user problems and change their behavior. That is the most important thing for a PM—not a few features, not JIRA tickets, not projects, but the ultimate outcome you drive for the user.

Participate in different open discussions, get a product mentor, watch webinars, and learn how you can identify metrics that really matter. I would suggest you read Measure What Matters by John Doerr.