Four things to be sure of as a junior product manager!

in this impatient era, many people are anxious to learn something and become Daniel immediately . Product Manager . Make products that change people and change the world. Is that the case? Of course not! Some people say is not to see you today's share, will be like Jin Yong novels, the Master of the unique stunt can dominate the " martial arts " . In fact, I would like to tell you that you want to become a qualified product manager, we need to do our down-to-earth practice, in order to understand the knowledge learned. Is there anything we can learn from our junior product managers? Let's take a few detours, more products feel it? I summed up, summed up in the following aspects:

Internet Product Manager pre-Preparation

First, to develop a keen sense of insight and self-thinking power;

Second, to determine the corresponding target users of our products, clear pain points;

Thirdly, how to transform the user's demand into landing;

Four, the overall control of the project acceptance.

A keen insight and self-thinking power

To develop a keen insight is the first need for us to focus on some of the necessary sites every day to see what is there? Portals, microblogging sites, reading sites, now advertising, new media prevalence, their information is also the forefront of the most rapid; The following media is also the primary product manager must pay attention to: Lei Feng Network, Fast road network, love stylish, tiger sniffing net, moving point technology, Krypton, etc.

It takes us not only to work, but to focus on events in our lives, to focus on the experiences and needs of our users, and to form a way of thinking. If you are observant and you are good at discovering, you will find that the framework of the product is equally applicable in life.

Here are two daily habits that are recommended for everyone:

1. Learn to record (for example: Download an Evernote note). What do you do with it? To keep track of what is going on around you and make it a simple precipitate;

2. mobile phone Download a number of science and technology, economic, product categories of books to use on, off duty, before bedtime debris time to watch;

3. to learn to share, product managers are required to have a certain capacity to speak, not to say that you will be a qualified product manager nearly a big step forward, sharing is nothing but their own knowledge precipitation, reconstruction of an important process.

There are many examples in our lives that we can observe. For example: The bank's call-to-order system, the Beijing Metropolitan Subway, the electronic shopping cart and so on, we should be good at discovering their shortcomings, and appropriate to give some solutions. As a whole, go towards a better life. Products are not necessarily tangible, service is also a product performance.

ii. identify target users and clarify pain points

The second thing is to tell us. The target user pain point, catch their itch point. Stimulate their excitement point.

The first thing to determine who the target user is? The use of a product role object, of course, can be the boss, technical colleagues, product managers themselves or others. And what are the properties of these target user portraits? Mainly include their age, gender, income, hobbies, consumption habits, product scenarios and so on.

Second, if you find the target audience, then the next thing to note is the user experience (the user experience is straightforward is the user's most direct response to using your product).

How do you understand that? Let's assume a user scenario: A user who uses your app to order a meal, first he sees is your app 's user interface, he will care about whether the interface is beautiful, the interface is clear and other factors, And then there's the real sense of what it's like to be in the process of ordering.

iii. Transformation of Demand

A simple understanding of demand transformation is the process of translating offline needs or business needs and user desires into specific product forms; The main experience in the user's collection and analysis, the final output the process of PRD documents.

We have mastered the above two things, also learned to arm themselves, know how to identify the target users and digging into their own pain points, excitement point. So how to transform the needs of these users into product requirements. The process of demand transformation.

First, Business or business needs (this can be defined as a company's strategic needs, usually a company policy or demand for new market policies);

Second, user needs / feedback (mainly on the product of an interactive feedback improvement, of course, the value of retaining core users);

Third, functional requirements (including product improvement,bug modification, etc.).

iv. acceptance of the project

The last thing is how to control your product, let it continue to go on. Temporarily to the matter from demand to product on-line supervision, acceptance work.

I use Xmind drew a simple flowchart to illustrate a process from requirements to testing / acceptance, and cautioned that any and all of a link's shedding or a little problem would probably rework the product's PRD documentation.

So it is necessary to devote enough effort to refine these details so as to reduce some time cost for design and development personnel. Product acceptance is also the final need to pay attention to the whole process.

Here's a little bit of emphasis. PRD document, which includes prototype design, functional requirements, interactive documents, as well as writing user instructions (for operators, for example: Customer service).

Source: Product 100

Four things to be sure of as a junior product manager!