To Be A Product Manager | Day 81
This journal helps me improve 1% every day…
Welcome to Day 81 of
To Be A Product Manager
Yesterday is terrible, today is not. 😎
Zero meeting, quiet office, deep focus. All things make today a wonderful day for getting shit done.
In the morning, we fixed the wording problems we got from American team and officially launched our English version website. But after that, my mind was a little paralyzed.
There’re so many tasks need to be done, and I didn’t know where to start. I believe every recent graduate has similar feeling when they just entered their career.
What I did trying to solve this problem is that, I looked through all the tasks I have to finish this week, and prioritized them with the order.
Then wrote down the tasks I think I could finish today on the sticky note, which are the 4 goals you see below. Besides, I also fill them with specific time slots, which saves me time on making decisions.
I didn’t get too much disruptions throughout the day, and that makes me a happy man and get the shit done.
- Product planning for next sprint (10:00AM-11:30AM)
- Z CAM test (11:30AM-12:00PM, 2:00PM-3:00PM)
- Review of website project (3:00PM-5:00PM)
- Videos encoding follow up (5:00PM)
What I Learn
In the afternoon, I was trying to write a document reflecting on the product development process regarding the website we created in the past 2 months.
And when I really went through everything we planned, every discussion we had and every document we wrote, yes there’re plenty of mistakes we made, which adding up could save us at least a week.
Here’re 6 main lessons learned:
1. Have a clear goal
So I started the project with the copywriting from HR and Operations teams. We made changes to the wording many times, but eventually gave up, because we don’t think it matches with our website need. I lost almost a week discussing about this.
2. Set up key point for every process
The copywriting should be confirmed before it moved to the design and development process. If not, changing the copywriting 4 times a day are going to drive them crazy. They cannot do anything before launch.
3. Make specific development estimation and plan
Our original plan is make our website responsive and change with the size of the screen. But engineering team changed the plan during the development process, which is not a good news for design team.
4. Be over communicated
It seems like it’s fairly difficult to get designers and engineers work together. If not over communicated, the realization of product design might get twisted a bit.
5. Make plan and share the plan before product testing
Testing engineer should draft a plan for testing, and product team should also get evolved. Otherwise, there may be things that don’t take into considerations.
6. Active closed beta test
Before launching your product, make sure have a closed beta test in your office, and see how people react to the design, features and more.
My name is Zake Zhang, a newbie VR product manager based in Shenzhen, China. I’m thinking what if I write daily product journal for 1,000 days?
Thanks for reading and let’s keep on hacking!
be so good they can’t ignore you.