Learning to be a Product Manager | Day 10

Finally hitting two-digit for this little journal project, hooray!

Monday is always intense and today is no exception.

Basically I was still running those routine and extra data to review our product’s performance for last week. Besides, I also helped our test engineer to ensure the scope of our new product. My mentor also sent me a template of patent file, and I should apply my thoughts to fit this template. It’s due before this weekend, so I’ve still got some time to work on it.


Lesson Learned:

  1. Keep good and neat documentations, especially those that are highly likely to be viewed or used again. Don’t ever attempt to sneak through it. Today the biggest trouble I had is having difficulty quickly locating the data link and easily modifying the parameters inside to satisfy my needs. I’ve prepared them ahead of time last week, but they’re poorly organized and hard to modify, so it seems it doesn’t help as much as I expected it to. I felt frustrated when my mentor wanted to modify it but it was time-consuming for her to understand my code. It’s like I’ve done something already but I failed to ship it. And it would appear that I haven’t done it at all, especially to people who don’t know or who just don’t care what I’ve done behind it. It sucks. It reminded me once again the importance of shipping results, because nobody’s gonna hear you brag about how hard you’ve worked on it. Show them the results, save other people’s time. And in the long run, it’s also saving my time as well.
  2. Ask questions and make sure everything’s right and ready before you dive into it, when it comes to areas you’re not familiar with. Today I wasted a lot of time checking my code logic to see if anything’s wrong, but it turned out that my logic was right, it’s just that the data forms are different so they mean different things. It’s because I haven’t communicated with our back-end engineer beforehand, but took it for granted, and it turned out to be the opposite. For this problem, I learned once again the point of communication. Communicate, communicate, communicate. It often costs more to find a mistake in the process and start adjusting than you spend some time to figure out everything firsthand.
  3. Experience values a lot. As a rookie, all you can do is try your best within your ability, and those that require a lot of experience are sometimes beyond your control. When things are going not that smoothly, learn to digest this feeling when you feel upset. Please don’t complain. Or at least try to restrain your desire to complain every time you feel the urge, and improve it little by little. Complaining ain’t gonna help even a bit, and it reveals your weakness in the most vulnerable way. Unarm your ego, it’s no big deal. You should have the confidence that if you follow these steps every day, you’ll be one of those experienced one day. Just give yourself sometime and be patient.

It really takes pain and effort to learn and be great. But I’ll always be on the way to pursue greatness. Cheers!

Like what you read? Give Cherry Tan a round of applause.

From a quick cheer to a standing ovation, clap to show how much you enjoyed this story.