6 major considerations in the early stages of product design

The uncertainty factors in the daily work of the product manager are not related to the function bug and the requirement change. What are the main points that can be prepared in terms of product operation, through pre-investigation and prior confirmation? This article tries to list six points to throw bricks.

1, the implementation of the problem

(1) Overview of data sheets involved in mastering requirements

This is the basis of the last five points, such as the field type, scope, what to take, how to fetch, where to return, to return to affect the existing fields and so on (in the large environment of drastic changes in personnel, this step is often not easy);

(2) Internal and external coordination

As the "edge" of the military map is the most easily broken, in cross-module, cross-domain and other multi-party interface is the most frequent bug, but also prone to three regardless of the region, it is necessary to pay special attention to the data situation at the interface, especially the current ' open ' situation, the problem of the partner interface is the ' big '

(3) Defects in the process itself

Logical and thoughtful, Zennai data source mismatch, the older the system the more serious the situation. Honestly, if you don't do the first steps, the basic data collection will simply not be able to circumvent these mines and cause total runaway. In theory, the collection of defects in the process itself can also provide a reference for the reform of business processes. What do you say? Driving business from it, perhaps in theory, is always a matter of speaking.

2. Performance Hazards

(1) The requirements involved in the field, which are the most frequently accessed, how often. The most frequent fields (and their parent and son) have overlapping and overlapping levels in the same project;

(2) the page on which the demand is located, whether it is a key page of high incidence of concurrency, or whether it will have a related impact, including the subordinate pages;

(3) If the event is held, whether the function and monitoring of the various preparation.

3. Coping with different prescription

Distinguish between long-term, periodic, one-time, and possibly multiple repetitions of a disposable.

Disposable semi-artificial cottage plan can be adopted to speed up the progress of implementation;

Cyclical can consider the development of tools to improve the ability to reuse;

The intermediate state, which is likely to be repeated several times, is partially implemented as part of the historical experience.

4. Change of halfway demand

Consider the amount of data, the frequency of updates, that do not involve logic or that may change in advance. Cultivate this "common sense" and "habits", in the need to put forward redundancy, do advance consideration.

Consider the complex associations and new logic that may increase, and anticipate the workload of these changes in advance.

What if there is a huge demand change that cannot be rejected? Theoretically through the so-called "mining demand side of the real purpose, to guide, to achieve a double win" to deal with the demand change, the actual work is not so idealized, the need to change the complex interests involved in the dispute, often is no way to win, as far as possible to rely on professional judgment, try not to get involved in the camp (in fact,

5. Experience

Whether the key processes (such as shopping carts, payment pages) add additional steps, or have an impact. If involved, try not to touch the key process, take the asynchronous parallel way, avoid the risk of runaway. Even minor textual changes in key locations need to be cautious.

Any detail that takes into account performance, page opening and responsiveness is the basis of all user experience, as much as possible to infiltrate the thinking of operational perspective into the subconscious.

6. Monitoring

The impact on existing monitoring and deployment, global awareness, not only to ensure the correct monitoring of new requirements, but also to ensure that no impact on existing other monitoring.

Consider the mutual effects of cookies and JS, and repeatedly confirm the mutual coverage of monitoring with the business.

Data monitoring point of attention: the focus of consideration plus and withdraw two points, whether there is abnormal movement.

s capture data, server log monitoring, business data and other common monitoring angles, according to the specific needs, select the focus of attention.

Article Source: Everyone is a product manager

6 Important considerations in the early stages of product design