Blog Uncle Cat’s blog
preface
Years ago department one-time purchase of a batch of books, I knew I should be assigned to read some books to management class, but I didn’t think beauty led directly gave me this book quickly turned product managers, in fact I’m a little resistance at the beginning, because I don’t want to give up my technology core industry, I prefer to study Java source code of all kinds of framework, Write open source projects. (AFTER all, I do a lot of walking on Github, but recently I’ve been uploading articles.)
The beautiful leader hoped that I could digest the book quickly and expand my functions slowly, which was something THAT I needed to get used to. However, I digested the book in the first working week of the New Year and took time to write a review on the weekend.
For example, I was used to writing and drawing in the book. I did not have systematic note-taking tools, nor did I practice some knowledge in the book, nor did I make brain maps (mind maps) for the book catalogue frame.
Therefore, in 2019, in addition to reading books, I also plan to read basic technical books, in-depth study of multi-threading and middleware, so I also set a small goal for myself, after reading, I will write my impressions, and draw brain maps for each book.
As it was the first time to draw and record, I also drew according to the catalog and knowledge points summarized by myself.
Next, I will review and summarize the brain map recorded by myself, and write down my own growth and expansion ideas for the whole book without referring to the knowledge points in the book.
Chapter 1 Summary
In this paper, the author describes his thoughts, experience and process of guiding students’ transition in a life-oriented and relaxed context. In the end, the author summarizes 21 suggestions on drainage according to his own situation.
Through the brain figure, you can see what are the author’s impression for the product manager, the author itself is do operation was born, but there is no systematic study in the transformation, the process of self-study, via the Internet too much focus on master product manager (PM, same below) technology, such as Axure, prototype, etc., in PM related types of books to read, However, books do not match the people who are suitable for them, which causes a stumbling block for their career change and so on. Besides, the author wrote some product analysis and competitive product analysis on the Internet and got some interview opportunities related to PM.
After reading the whole chapter, what I remember most is competitive product analysis. Just as the author said, good competitive product analysis can shorten the distance between you and the CEO. I am also eager to try, because I often publish articles in the community, so I also plan to write a competitive product analysis report related to the community. The other points were also what I thought at the beginning. After all, I was also a mechanical engineer who switched to Java technology development, and I also had some self-taught experience at that time.
Chapter II Summary
The author of this chapter gives some advice, which is actually a very light-hearted book, and suggests that you take the time to read it, just to understand what a product manager really does.
Emphasis is how to quickly turned, first the author hope the readers can match itself is in line with the PM this kind of work, at the same time, insist to learn entry PM at least must master the knowledge, at the same time must be combined with its advantages, such as in the original industry experience, this will greatly add cent, as mentioned below will be the PM technology lines and lines of business, The technical line is fixed, and you need to master the tools and technologies, but the business line is your in-depth knowledge and understanding of an industry. Therefore, if you have accumulated certain experience or contacts in the previous industry, it is very important experience for you to transform the PM of this business type.
Chapter III Summary
This is the core of the book. Personally, I really understand the daily work flow of a basic product manager in this chapter.
In the process of reading, I also clearly understood the role of user portraits and the general catalog structure of competitive product analysis. In a whole project I was in charge of before, I also adopted the method of product prototype screenshots and annotations for the product requirements document, which was conducive to the rapid development of the team.
Similarly, this is a similar requirement document (above) written before (actually not). What we lacked at that time was demand analysis and demand review, and we did not have a clear user portrait at that time, resulting in poor pertinence of promotion and operation after the launch.
Project management in this book is actually equivalent to PM, so the function of project management also comes down to PM. At present, I also use some online project management platforms to assist in project management (similar to fishbone, etc.).
To sum up, I have gained something from this chapter, and the author made me deeply appreciate the overall process through the cases of Taobao and Tmall. At the same time, it is also a small knowledge point for the data statistics of the product. I have learned the data conversion rate of the funnel model.
As it says in the summary:
1. The purpose of doing demand research is to make sure that what you want to do is meaningful; 2, the purpose of writing competitive product analysis is to correct and improve your product idea; 3. Mind mapping is to sort out the details and status of product functions without missing anything and list the priorities of user needs; 4. The purpose of drawing flow chart is to sort out business process and user process.
Chapter 4 Summary
The last chapter is actually some advice on the road to self-study and avoid the wrong path pit. You should probably get to the end of the book, and you can go straight to the brain map, and I’ll give you some ideas.
I think it is a point to learn something by yourself and find an organization, but you need to find a real organization. I don’t recommend it right now, but if you have the time or if you’re transitioning, you can find a junior product manager. The advice in the book is very good, that is, self-study transformation should be systematic learning, and be sure to go to a big company that can take you to progress, no one may take you to a start-up company, at the same time, no matter self-study technology, self-study PM, to accumulate. No one out is a high salary, the so-called some is their own has been silently learning to pay.
Be sure to reflect on your shortcomings regularly. ** After reading this book, I was very confused about how to be a product manager and technical management team suitable for our company. Each company has different development stages, and the function positioning of this PM is also different. In a word, confusion is good, and you will grow stronger and more mature out of it.
conclusion
Thanks for the author’s sharing, and I can see the author’s rich experience in PM industry. At the same time, this book is really suitable for xiao Bai to read. It is easy to read without too many professional words, so that many people can have a general concept of PM.
Finally, THE author also gave priority to the author of this paper, which was reviewed by Mr. Li Sanke, but was unexpectedly well received. Here I would like to thank Mr. Li Sanke again for his affirmation and contribution to the product manager industry, and I can see the author’s attitude towards readers.
Public number: Java cat said
Now architecture designer (code farmer) and entrepreneurial technology consultant, unruly mediocre, love open source, talk about program life and irregular dry goods.
