This article describes how to go from the weak chicken development to the counterattack of the product owner. From the confusion at the beginning of the work to the process of becoming the person in charge, you can come and see. Look.

Editor’s note: This article comes from Everyone is a product manager , author vitamin.

3 years from weak chicken development to product owner < / p>

As of March 2020, my product life is almost three years old. Taking this opportunity, I decided to write something to record my product journey in recent years, many of which I have stepped on. Experience, I hope it is helpful for you who are reading this article.

I just joined the company in 17 ~ I just started in 18

I have been in the product-related content for about half a year since I just started my job. It can be said that I am equivalent to “sitting” on the cold bench for half a year and “watching” the water dispenser for half a year.

  • On the one hand, the reason is that the company was established shortly before, and the product team did n’t have any training system in place. I may have been here for several months and I still do n’t know how many systems the company has. Which piece, what is the specific development process, release process and so on.

  • On the other hand, because of the supply chain management, competing products are difficult to find, lack of physical and specific scenarios, and it is too difficult to understand the business.

    I remember that it was a few months later that I went to the warehouse twice, and I realized that people often say “picking”, “picking”, “reviewing”, “delisting”, “out of stock”, What do you mean by “receiving goods” and “checking out”? Before that, no one had given me a business flow chart, and no one had given me training or explanations.

    At that time, it was probably the longest life. No one cared about me, and no one told me what to do. I can only look at some product-related books, tutorials, and courses every day, but I lack the opportunity for practical combat. I basically forget to read them, or I ca n’t see them at all.

    After boiling the frog in warm water for a while, I was arranged to go to the warehouse to do some hard work and help. These episodes are quite miserable, but they have gained a lot. At least they are familiar with some of the doorways of the warehouse.

    Just started in 18 years ~ before promotion to product management in 19 years

    It was around May of 18 years. Due to the problem of personnel transfer, I finally started to actually take over the related business. I was responsible for the company’s warehouse management system, WMS. In this way, I fell in love with WMS in the past two years. It started.

    When I first took over the WMS system, my first feeling was “simple”, and excessive simplicity was “simplicity”. Few features, few pages, and logic doesn’t seem complicated. But when I actually started to prepare for the show, I realized that I still think too young and I don’t see enough.

    At that time, I was accessing an e-commerce platform. They raised some requirements. We will meet them only after they meet them. Then they began to organize the needs, find competitive products, do analysis, and finally raised a brow. Program. Then began the review. After the internal review, I felt that there was no problem. We went to communicate with the e-commerce platform, and as a result, many plans were passed on the spot. So I went back to the internal discussions, revised it, and then continued to communicate with the e-commerce platform, and many plans failed.

    two thousand years later …

    After so many trips back and forth, the leader above decided to make a decision. In any case, the docking will be done during the Mid-Autumn Festival in September.

    With Deadline, it seems that everyone’s cooperation has become happier and more efficient. In the last few days, I worked overtime and stepped on the line and posted it online. Then, as the person in charge of the relevant product, I went to the Hong Kong warehouse to actually collaborate on the production operation, and spent a significant Mid-Autumn Festival.

    It is also from that day onwards that I know that Hong Kong ’s Mid-Autumn Festival is closed on the second day after the Mid-Autumn Festival, and there is only one day off. In those three days, I almost went out early and returned late, and fell back to sleep after returning to the hotel.

    Fortunately, all these efforts paid off. My product capabilities, my output and my enthusiasm still made my colleagues recognize me, and I began to take over the WMS system slowly and comprehensively. Also from that time, I felt why I said that products are treated like my own children.

    I proposed to reform the framework of the system, changed the new framework UI, and planned many new features.

    Although many ideas and solutions were too naive, they were too shallow. However, with my tenacity and enthusiasm, even before I joined the new front-end, many CSS styles were directly written and debugged by me, and some places were harsh enough to explain how many pixels.

    At that time, I was unwilling to accept imperfections. Perfectionism is not only a requirement for myself, but also for specific products. Of course, I still make a little sense, so as not to put forward a bunch of needs to be hacked for development in pursuit of perfection. That time was the time I loved and enjoyed the most about the profession of products. I felt the charm and motivation of this profession, and also understood the meaning of “self-driven” and “kernel-driven”.

    After 19 years of promotion management ~ now

    After fully taking over WMS in 18 years, I started to find some rhythms of making products. Many things were slowly contacted, and my business was a lot familiar. But at this moment, the product team is still a piece of sand. There is no leader and no cohesion.A lot of information is not shared, and everyone’s capabilities are uneven.

    Combining all aspects of the cause, and the luck of “all relying on peers”, I was like the catfish thrown into the sardines, which stirred the originally quiet situation. A “spoiler”, with the kind of enthusiasm of the newborn calf, was a small wave. I was promoted to the leader of the product group in the early 19th. At that time, there were 6 people in the product group.

    Promotion is naturally a happy event for me, it can also be said to be proud of the spring breeze; then naturally there will be frustrated people, which caused the dissatisfaction of the old members of the product group. Maybe it ’s because I did n’t get along with me, maybe I did n’t get attention, or maybe I ’ve encountered a better opportunity. In the end, three products left in succession. It was originally a group of 6 people, and there were only 3 people left. One of them was an intern who had just joined the company.

    For me, the resignation of the old members is beneficial to me to some extent, because the management of elder members who are older than their own age, experience, working age, etc., I will have some pressure and some places Open; but in some aspects, obvious shortcomings have been exposed. The shortcomings of the previous products were exposed at once. If one person leaves the job, then the other person under his responsibility cannot take over for a while. The document has no system. , Specifications, historical data, data, etc. have not been collected and sorted out.

    This led to a lot of pressure later on. I had to stand up to several people at the same time, and I was busy recruiting and supplementing new students.

    This experience actually inspired me a lot, and it turns out that some things really need to change before we meet new opportunities and discover new continents. From this experience, I realized the importance of teamwork, the importance of regulations, and the importance of intangible assets.

    As a result, I am still doing product work on a daily basis, and I have spare time to make up for management knowledge. My management road also started around March 19th.

    As far as the management experience is concerned, at present, it is very difficult for me to have any insights, nor can I refine any framework experience. But regarding the three importances, I did work hard to explore, and I also have a little bit of a shallow opinion.

    (1) The importance of teamwork

    Since I took over the team, I have begun to strengthen the management of team collaboration in several ways. One is software, such as using Axure’s team collaboration version and Tencent’s document collaborative office. On the one hand, it regularly holds product weekly meetings, proposes weekly report systems, and product sharing sharing communication meetings. Let everyone sit together and communicate as much as possible. Whether it is the assignment of work tasks or the experience of the product, these things that bring the team closer can be done without spare time.

    (2) The importance of rules and regulations

    I began to document my methodology and experience of product work, and then recorded it in WIKIn I, I edited an item called the product daily work specification guideline; I also combed and restructured the links that were developed or tested, complained, and spit out in the daily product work, and then announced in the team what will be needed in a future link Do not do anything, it is equivalent to the next command. At the same time, I also encourage everyone to self-examine, review, and raise irregular points in daily work that need to be improved, and then we follow the new system and process together to prevent similar things from happening in the future.

    (3) The importance of intangible assets

    The “intangible assets” mentioned here actually refer to the collation and collection of some documents and data.

    For products, there are many daily data files. Common brain maps, flowcharts, prototypes, demand pools, demand files, demand applications, and even learning materials, PDF e-books, weekly report templates, PPT Templates, mail templates, reporting templates and more.

    With the increase of working hours, a huge amount of data will be generated, and many times when leaving for transfer or rotation, because these materials are not collected and sorted at the time, it will not be found when it is needed. Now, some things may be rewritten, and some do n’t remember at all. It is painful and costly to turn over the records and restore them with memory.

    So “intangible assets” are also assets, and they should be valued and dealt with in advance, just like the risk awareness in investment. Precautions in advance may sometimes seem daunting, but in the event of a risk accident, this part of the preparation will have the effect of sending charcoal in the snow.