UI designers want to become product managers, what do I need to learn systematically? What knowledge

1.Document class.

BRD (analysis focusing on business model), MRD (analysis focusing on market share), PRD (analysis focusing on product functions), etc.;

2.Graphics class.

Flowcharts, swimlane diagrams, mind maps, information architecture diagrams, conceptualization of information, instantiation of concepts, prototype diagrams (hand drawings, wireframes, wireframes for a large static description of page jumps, high-fidelity page jump prototype diagrams), etc.;

3.Utilities.

Visio (flowchart), Axure (prototype diagram), mindmanager (mind map), todolist (task priority), ppt (brd, mrd), word (prd), excel (data analysis), etc.;

4.Category: Works.

If you have a background in UI design, you also need to prepare UI works that you have done before. Including: UI interface design drafts, icon works (hand-drawn, flattened, skeuomorphic, realistic), size marking manuscripts, cutting specification manuscripts, hand-drawn works, portfolio links, etc.;

5.Accumulation of ideas.

A good design collaboration product should be able to help BAI designers solve the difficult problems of experience and efficiency. zhi

In my personal opinion, there are no good experiences and bad experiences, only experiences that are in line with business goals and those that don't meet business goals. An experience that can help designers solve the experience and improve efficiency is an excellent experience. The Blue Lake Product Design Collaboration Platform is designed to be just that.

The Blue Lagoon is a great way to improve efficiency, allowing designers to work smoothly and store design assets with confidence. Meet both user experience and business goals.

On the surface, user experience and business goals are contradictory. For example, some e-commerce companies deliberately hide customer service** to reduce costs, which is not in line with user goals from the perspective of customers, but is in line with the business goals of e-commerce companies.

But essentially, there's no contradiction between doing UX design and achieving business goals. A good business goal is the only way to give birth to a good user experience.

Tools are also important:

Axure, Ink Knife, Blue Lagoon.

According to the actual situation, the actual project to communicate, the product manager is mainly to sort out the user needs to ask for a good job, compile a document, and then draw a good product flow chart and prototype diagram, and then combine competitive product analysis, market, user groups to communicate with UI designers, positioning product style, main color, function, user experience precautions, etc., the rest by UI designers from a professional point of view to design the layout of the product, product renderings and then with the town which product manager and related operations, Communicate with marketing colleagues and leaders to optimize products.

After finalization, it will be submitted to the development engineer for research and development of the project or product.

1. Keep in touch with customers.

Mini Programs should pay attention to customer retention, which requires us to find ways to retain users. Enterprises should not only allow users to complete the elimination of stools and fees on the first opening of the Mini Program, but also improve the repurchase rate on this basis.

2. Know the needs of users.

I believe that all merchants have a clear understanding of their target customers. But after clarifying, we still need to do two things: one is to reach out to customers and open the door to active marketing; The second is to segment customers to facilitate the formulation of precision marketing strategies.

Method 1: Divert offline customers to the Mini Program. For merchants with offline stores, this is the most commonly used, and it is also the effect as an obvious drainage channel. Many of our clients are people who live or work in the surrounding area.

They are often already familiar with the merchants, have a certain loyalty, and have a foundation of trust in online consumption. A common method is to hang and post a leaflet of a promotional poster with a mini program code. It is more effective to cooperate with some marketing activities of the store.

Method 2: Promote online marketing campaigns. That is, through self-sharing of Mini Program marketing activities, or encouraging users to share Mini Programs, to achieve communication effects. Generally speaking, merchants only need to use simple user operation methods or community operation methods, combined with marketing activities, to encourage users to share the rough and corrupt order of Xiaocheng Shi, continuously promote traffic fission, and achieve the purpose of rapid dissemination.

3. Stimulate potential demand.

Letting customers spend is the ultimate goal of merchants. There are many factors that affect customer consumption, especially from offline to online, and many consumption scenarios will not appear offline. For example, we may meet with friends or business partners in a coffee shop, but sometimes in the company's internal department meetings, the leaders will pay for coffee and treats.

Customer service solves the problem of customer relationship building and customer relationship maintenance. The task of customer service is really customer development and customer relationship management. The development of the customer involves the organization of speech and the training of communication skills, which will not be repeated here.

The process of customer relationship management can be divided into three links, namely the establishment, maintenance and repair of customer relationships.

UI to product, there are some advantages and disadvantages of this position itself:

1. Strong aesthetics.

2. Familiar with the product process, especially the part from prototype design to front-end implementation.

3. Pay more attention to the details of the product and be delicate.

4. Have the ability to understand abstraction.

5. The software is relatively quick to get started (compared to PS, which is simple).

Cons:

1. I don't understand the business, the overall situation is not formed, and it is easy to get into the details and can't get out.

2. I don't know how to operate and lack experience in dealing with users.

3. The process structure is not smooth, especially the background logic.

4. Do not understand technology and cannot accurately assess the development time.

Therefore, when UI is converted to a product, it is necessary to make use of its strengths and avoid its weaknesses. Here's how:

1. Start with the company's internal products (because the highest success rate of job transfer is the company's internal job transfer), who is the target user of the dismantled product, how to meet the needs of users with existing functions, and what methods can be used to solve the current problems. Think about where you stand in the team at a higher level.

2. Daily reading and accumulation, such as "Everyone is a Product Manager" and "User Experience Elements", to understand the daily work of the product and the core process of product design.

3. Write your own competitive product analysis and draw prototypes. You can also start with your current company's business and products.

4. Industry exchanges, more forums or communities, more exchanges with experienced people, and more offline activities.

Definitely yes, but you need to understand the relationship between the two:

From the perspective of the three elements of user experience, the product manager's focus is on the usefulness of the product, and the UI designer's focus is on the product's ease of use and satisfaction. The user researcher happens to be like a regulatory role, monitoring the three elements of the product user experience in the form of walk-through, data analysis or user research, and raising questions and suggestions.

In terms of the specific division of labor, the product manager is concerned with what to do, and the output, i.e., the product document, focuses on the background, definition and description of the requirements, as well as the sorting out of the business process and logic. These basically determine what the main pages of the product are, and what are the main elements of the page. When working with UI designers, in order to better communicate and control some basic design points, product managers may draw prototype sketches of individual key pages, and these sketches generally lack details, which does not mean that UI designers need to design solutions in this way.

After receiving the product manager's deliverables, the UI designer's job is to think about the layout of the page, navigation, and how the various controls interact, so the output is a very detailed interaction document.

Although there is a specialization in the art industry, it does not mean that the product manager cannot propose modifications after the UI designer has done a good job of the interaction plan. Because the product manager is the demand side of the UI designer, the job of the UI designer is to meet the needs of the product manager. This is reflected in the fact that after the output of the interactive solution, the first review is communicated to the product manager.

But if the UI designer just doesn't agree with the product manager's revisions, the final product manager can either make concessions or take the problem to a higher level and let the higher-level leaders make decisions.

To sum up, the relationship between the product manager and the UI designer is only the upstream and downstream of the work, and the decision-making position is relatively equal. However, in practice, UI designers tend to be weaker because product managers are more persuasive or UI designers don't want to debate too much.