To Be A Product Manager | Day 76
This journal helps me improve 1% every day…
Welcome to Day 76 of
To Be A Product Manager
Website, website, website… We are about to launch new website today (Chinese and mobile version, English is coming soon) Today there’s not so much time I can focus on thinking, but more on finding problems and trying to solve them as soon as possible.
As I mentioned in the last post, when you really create something from scratch, you know a bunch of bugs and problems are going yo come up when you get to the development process.
The features might not be built the way you want them, or sometimes, engineers also have their own understanding or preferences for design and aestheticism.
You cannot block their minds when they are developing the product, that’s not humanistic, or even possible.
I think each of one us should hold on to their ideas.
But I believe the key to solve the problem is
Communication
how you articulate your thoughts with reasonable points, as well as appreciated others’ unique opinions. This is the subtle art of launching a product.
And we should all work on that. I believe people are basically good and kind, we are all afraid of making other people feel bad.
Goals
- website
- website
- website
What I learn
I still remember the first couple journals I wrote. Prioritize, prioritize, prioritize. This always comes the first for product management.
When I review what I’ve done today, there’re 2 concepts coming into my mind, which I call them
Micro prioritization
Macro prioritization
Macro prioritization
I think this is most familiar type of prioritization for product managers. For each quarter, month, sprint or even every week, you should have you wown priorities, for the projects and features you should be working on.
Micro prioritization
It means anything easily to be neglected or even forgotten, like the things you need to discuss during a meeting, you should prioritize before calling every body to the meeting room.
What I learn in the past 2 days is that, while every body is providing feedbacks and suggestions for the product. There should be a guy documenting everything and prioritize them in order, then share the list with others.
This makes people understand their feedback is valuable, and also helps engineers sort out the order for bug fixing, which increases the productivity of the whole team.
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!
Warm Regards,
Zake
be so good they can’t ignore you.
