Recently, a large product system was designed, and many thought collisions occurred during the process of communicating with leaders and other colleagues during the design. The record is as follows:
1. Risks
For the early stage of the product, risk identification is not an important task. There are currently two comments:
1) identify risks at all levels as much as possible (especially those accumulated based on previous experience), consider risk response measures, and reduce the risk of project failure.
Problem:
It is easy to get down to details in the early stage, and fear Wolf and tiger, which is not conducive to overall planning.
The risk of detail may not be within the management scope of the leader. You cannot let the leader care about how to implement a very small technical problem. Therefore, it is easy to dislike leaders.
2) You should not take into consideration too much of the problem. You only need to consider a large risk. In case of any risk, the system resolves the risk based on the actual situation.
Problem:
It is easy to ignore some extremely important risks. On the one hand, it is not conducive to architecture design, resulting in high design defects. On the other hand, the risk avoidance costs will be extremely high in the future. It is easy to delay the project construction period and cause the project to fail.
Personal Opinion:
We should also consider various risks and not necessarily conduct risk assessment in the early stage. The initial risks mainly come from the previous project experience. Only pay sufficient attention to the risks encountered in previous projects. Avoid problems that may occur later.
2. Questions about employing people
During the preliminary planning, I encountered a problem. If there is a problem with the responsibilities of the UI designers in the group.
According to the current situation, the UI (UE) designers in small enterprises in China are actually doing some graphic design work, interface layout, and user experience. Generally, they are determined by the Development Manager or product manager, architects also give their opinions from the implementation perspective, so there are many restrictions on the UI Designer.
From the current planning, we hope to have two voices on the responsibilities of the UI Designer:
1. Plan based on existing work;
Advantage: The risk is low, but the development manager and architect need to be responsible for more work.
2. Let the UI Designer complete the uidesign of the product independently, including understanding the user requirements, designing a good user experience, and facilitating system development and implementation.
Advantage: it gives the UI Designer more space for design.
Disadvantage: The project is postponed due to high risks and high risks.
Personal Opinion:
The first solution is adopted. Of course, the UI Designer can be given sufficient space for discussion during actual implementation. However, it must not be handed over to the UI Designer, and no one else will participate.
3. Questions about initial design granularity
The design of small systems generally takes all the situations into consideration at the beginning, and then writes and designs various files. Therefore, there is generally no large design deviation.
However, in the process of designing a large system, if you continue using this method, you may be unable to understand the requirements and work.
Bottom-up design:
In the initial stage, the workload is huge and it is difficult to clarify the ideas. However, once clarified, the subsequent work is easy to carry out and there will be no major deviations.
All questions that can be thought of in this process are identified one by one, and all questions are confirmed.
Top-Down Design:
Initial work is easy to carry out, and the leadership is easy to accept, but the design and implementation are easy to change in the future, or even the project fails.
Personal Opinion:
Individuals are still used to adopting top-down design concepts.
Questions about the overall product design