Logicality of product manager

First of all, a product has certain systematic characteristics, from product positioning, functional architecture, structural analysis, framework design. All links of product construction are permeated with rigorous logical thinking.

1. Product positioning

Product positioning is a highly abstract process, in which the core elements are directly selected from various factors; This requires the product manager to think carefully and filter layer by layer. Finally, the core point is clear: who meets what needs; From the strategic level, there are two perspectives: what value your users provide; What kind of value is provided to the company;

2. Problems with product architecture

The product architecture is not mentioned much; In the technical field, there are many references to the system technical architecture; But I think this "product architecture capability" is very important; A product can be regarded as a system, containing multiple function dimensions (this dimension can be a layered structure or a circular structure), and each function dimension is distributed with multiple function points;

Such thinking is conducive to our overall consideration of the function construction of a product; The need for balanced extension at all levels; It doesn't go deep in one line, but the rest is really a short board (similar to bucket theory); It helps us to build more solidly on the core and basic functions (for example, VIP operation is divided into core functions and long tail functions), rather than focusing too much on some marginal elements or long tail;

A product manager should be a product architect, not just a thought transmitter who can put forward several ideas;

3. Functional structure problems

To describe a function, we need to analyze it with a rigorous interaction process; In addition to grasping the mainstream scenario, consider various abnormal branches;

At this time, the description of the business flow chart is very necessary for the product manager.

4. Frame design problems

For general products, an interface (WAP page or software) is an interaction unit; The information layout, or frame structure, on this display page needs to be very clear;

Take WAP page design as an example. Before designing a page, the product manager should determine the information framework of the page in his mind:

1) It needs to be clear that this page is divided into several framework modules from top to bottom, from left to right (generally available in WEB);

2) Each module should have a clear functional definition (what to do);

3) Then deploy some links or text in each module;

4) At the same time, it is also necessary to limit the number of modules in a page to avoid too much information, which will cause users to pay attention to scattered points;

A clear frame page allows users to see the past, so they can roughly understand the information to be conveyed without confusion and reading fatigue; Your logicality is perceived by the users looking at this page; This perception is: clear, or confused; How can apples and oranges be put together with shoe brushes?

Our common problems:

The layout is organized only by the granularity of a URL (or a line of text), resulting in multiple different kinds of information being organized together, or inserting links arbitrarily on the page, ignoring the impact on the overall page; For example, where to open an advertising area on the page to carry cross links, it should also be considered here, not to interfere with the user interaction process, and not to make the user area click by mistake;

The ability to summarize and summarize here requires the product manager to have a logical and organizational ability for information, and be able to view a product systematically, from macro to strategic positioning, functional architecture, from micro to interaction process, and UI experience.