Therefore, we generally call new products "handyman" in a friendly way, which perfectly explains our requirements for new products: we should look at everything, be busy with everything, and every department should have a stroll to build a good mass base ... The purpose is to make new products quickly familiar with the company's product line, the company's workflow rules and regulations, deal with trivial matters that colleagues, brothers and sisters have no time to take care of, and integrate into the team.
Take app products as an example: how to be familiar with products?
Go to the company and carefully download the previous version of the requirements document and product prototype several times. If you don't have permission, you can ask the product manager. Since joining the team, you are no longer a user of the company's products, but a product designer. Looking at the past work records will help you to re-examine the product from the perspective of God, understand every detail of the product, and not be weak at the meeting.
If you read each document carefully, you can't guarantee how deep you have mastered the core requirements of the product, but you can definitely grasp what is strong demand and what is weak demand in your leader's mind, and you can also understand the company's design specifications for documents and prototypes, so it will be much easier for you to do it yourself.
Newcomers always have many omissions in product design. In fact, this is not a question of logical ability. To put it bluntly, it is an unfamiliar problem. For example, a login function simply includes three parts: registration, existing account login, and forgotten password. Registration also includes mobile phone, email address, third party and so on. How to choose? Further study, the app also has to deal with the forward compatibility of account information when the version is upgraded, and the details such as whether the same third-party account can bind multiple mobile phone numbers, which are rarely considered when you go to school. When you really join the team, these problems may not be your turn to deal with, but you must learn.
When reading prototype drawings and documents, learn how your leader describes a requirement. His routine is not necessarily the best, but it is definitely the most familiar to the whole team. Do it first, no loss. Sorting out the requirements documents of each version in chronological order, and going through the requirements of key, important and general levels according to the time axis, there will definitely be many gains, which is euphemistically called: cultivating a sense of overall situation and product. To sum up, the order of workload is: 1. Telephone exchange (terminology: inter-departmental communication and coordination of project progress), 2. It is comparable to the crazy typing of secretarial work (terminology: outputting high-quality documents), 3. Abuse by testing (terminology: participating in product testing), 4. Drawing (terminology: part of functional prototype design), and 5.
Analyze one by one:
1. Running errands and sending emails in groups are inevitable for newcomers. Be enthusiastic and unrestrained. The more people you know, the more you know. Dealing with operations, BD, R&D and so on will be an important part of your future career. Knowing their interests and personality characteristics is of great benefit to your work.
2. Writing documents, basic skills, no skills, staying up late.
3. Being responsible for a small function for the first time, the document and prototype are definitely not detailed. The brothers and sisters in the test group drag you to the conference room to confirm the requirements. Inexperienced, you are easy to be abused and fall behind. What should I do? Pull the leader! After receiving the invitation from the test team, don't hesitate to bring the leader. Leaders will lend a helping hand at an appropriate time. Of course, you should live up to expectations and pay attention to collecting experiences and lessons.
4. Newcomers often make prototypes quickly, which can be completed in a day or two. One reason is the fine division of functions, and the other reason is the lack of experience, especially those who don't understand technology. Many problems may not take into account the difficulties that may be encountered in research and development. Crash techniques are in previous documents and prototype diagrams. Look at the use case carefully and read the comments. For example, chestnuts, you should add geographical location information to every post on the app timeline and display the distance at the same time. Here comes the problem. What will you consider when you meet this demand? The form tells me that you just cut a postal map, filled in a geographical location icon on it, and put the city name and linear distance next to it. (The mobile phone obtains gps data and uploads it to the cloud, and the cloud judges the distance by pulling the map data by weight, which simplifies the straightforward technical background). What you need to consider is the judgment strategy, such as whether it is more appropriate to directly display the distance if the poster and the poster are in the same city. If the distance is very close, is it more appropriate to use meters, accurate to several decimal places, etc. If you want to pull the information of nearby buildings, it is more complicated. Therefore, the newcomers make prototypes, think more about some problems, feel that they have tried their best to think, and then take a look at the leaders. After modification, when sending emails, send copies to their own leaders, R&D leaders and test leaders.
5. Docking with customer service is to cultivate product feeling, in fact, it is to let you understand a truth, change your subjective consciousness and impetuous psychology at school, and experience what it is like to stand in front of a thousand Hamlets. The word user demand is so big that you will be ashamed to mention it for a long time to come. Valuable suggestions and bugs fed back by users are recorded in excel in time and copied to department leaders (although they hardly read them).
6. Young and strong, hey.
7. Have a meeting, practice your expression skills and practice your gas field, but it's best for newcomers to talk less, take notes, watch them argue, and seriously understand how to win (no one is convinced by reason, but it depends on materials to win. . . )