An ordinary product manager's day may be like this. Go to the company in the morning and think about what to do these days. Open the notepad and start doing tasks one by one according to the above requirements.

You need to add history in the product's chat module. Well, look at several common social tool apps, and they all know what they are doing. Open a blank

Sketch the document and start drawing.

At this time, an engineer colleague came over and found that a previous requirement document was unclear. So I took the relevant personnel to an emergency meeting to check. Oh, there is still a logic that has not been described well. Just discuss it clearly. Everyone dismissed the meeting with satisfaction.

Continue processing the document. It's time for lunch. Just about to go to dinner, the boss suddenly stopped and said, alas, the one who arranged the product introduction yesterday.

PPT, are you ready? I suddenly thought of it, but I wrote it down in my notebook and didn't have time to do it.

So I ordered takeout and made PPT first. It took an hour to finally finish. Send an email to the boss as soon as possible, and then continue to do the chat module.

After the plan is completed, send it to UED.

Department. Look at the unfinished task. Oh, there was an email before, and the operation department mentioned that the current transfer function was inconvenient to use and the user feedback was poor. So I dug out the requirements document of the transfer function and studied it carefully.

Did it for more than five hours.

An optimization scheme, called several product colleagues to discuss for half an hour, decided the details, and prepared to complete the document and submit it to development the next day.

There was a project iteration meeting in the evening, but not this time. Yesterday was also because people were not together. After thinking about it, they are really unreliable. They have to open a day later, and they may have to postpone it and take the blame again.

I had a casual meal downstairs and came back to see the task and investigate the commercialization of social software, so I searched out various articles on Zhihu, Weibo and WeChat official accounts and read them one by one.

Read until 9: 30, very full. Go home from work. Just got home, the boss called to ask PPT.

What happened? I replied that I had sent an email. Maybe I missed it. The boss checked, and it turned out to be so.

A good product manager's day may be like this: come to the company in the morning, open the to-do list and rank yourself in order of priority. The boss said there was a PPT of product introduction.

This is very important, so do this first.

PPT flower 20

Make the first draft in minutes, show it to the boss and ask if this is what you mean. The boss said there were several inappropriate places. So I changed it, and then continued to supplement the completeness and adjust the typesetting. Finally, I invited a designer colleague to help me comment and adjust the color matching and layout.

Sort it out and send it to the boss. Considering that the boss was worried that he might miss it, he went to his office to remind him that he had done something.

At this time, it is probably lunch time. Thinking that I haven't had much contact with the development brothers recently, I called several engineers to have dinner together. While eating, I talked about some problems encountered in product strategy and development recently, and by the way, I communicated my feelings and talked nonsense.

After dinner, I began to do the historical function of the chat module according to the arrangement in the list.

First, write out the requirement logic of this function, such as who uses it, when to use it, when to use it, and how to use it. Then, combine the scenarios and requirements to derive the function.

At this time, according to the function, draw three schemes: A, B and C, and then look at several common social tools.

APP, learn from each other and put it in your own plan. Observe the advantages and disadvantages of the three schemes again and write clearly.

I discussed several different schemes with my product colleagues, and agreed that scheme B was the best, so I initially decided that it was scheme B and sent it to UED.

Part, by the way, sent to the relevant developers, let them have a look at the feasibility.

At this time, a colleague of the development said that a previous requirement document was unclear. So I took the relevant personnel to an emergency meeting to check. Oh, it turns out that there is a logic that has not been described well and discussed clearly. Then, I will tell you the problems that appear under the resumption, when, why, who found them, why they were not found before, and so on. After understanding this, we will work out a new collaboration process together to avoid problems that will arise. Everyone is dismissed.

Look at the unfinished task. Oh, there was an email before, and the operation department mentioned that the current transfer function was inconvenient to use and the user feedback was poor. So I went to my colleagues in the operation department and asked them who asked the question. Colleagues in operation said that there are several users, and they need to get their contact information and call back directly. Take sth down

Three questions, and then think about the corresponding 3.

An optimization scheme, show it to the colleagues in operation, and then prepare to complete the document submission and development the next day. And remind colleagues in the operation department that such questions should be provided together with the user's contact information in the future.

There was a project iteration meeting in the evening, but not this time. Yesterday was also because people were not together. We can't put it off any longer. Find some colleagues who have something temporary today and tell them sternly that if we don't have a meeting together, this iteration may be postponed and the consequences will be borne by them. Send another email back to the TV station, cc to all participants and their.

Leader, explain the situation. Everyone said that the meeting would end the next morning.

I had a casual meal downstairs and came back to see the task and investigate the commercialization of social software, so I searched out various articles on Zhihu, Weibo and WeChat official accounts and read them one by one. When reading, put all valuable ideas in order.

Evernote, and make an index for easy reference.

Read until 9: 30, very full. Go home from work.