Breaking through the fog and moving forward in difficulties--project, schedule, goal management

Absrtact: At work we often encounter scenarios such as the following "fog", which we do not see clearly in the direction. Repeat the experiment but find it difficult, how to make the project or product direction clear? Break the fog? ......

I. Analysis of problem situations

Here's a sample from the scene of the film "Fog" ...

Figure 1:

1, a group of people started as if in a small supermarket inside, outside are "fog" is not clear direction, the task is unclear, the technology is not clear, the manpower is not clear, the performance of the financial side is not clear ....

Figure 2:

2, you try to get out of this environment, when you summon up the courage to prepare some manpower to try, with their own team Telework rushed out, found that the battlefield visibility is very low, although more than previously seen a bit, but limited, and you can again arrive in the same position may be new threats! It is always very difficult to get you out of a higher winning work plan.

Figure 3:

3, and may also be very injured, may be in the "fog" where the time, there are some monsters or tentacles damage some combat effectiveness .... The situation is very much omitted here 10,000 words.

Figure 4:

4, and then with teammates back to the place (small supermarket). The team's confidence in battle was hit. Team includes research and development \ Leadership \ Customer anxiety is rising. Still need to regroup try to try to go to the outside world again ....

This is actually a better representation of the texture. Some of the research and development of the scene, managers or developers of the entire battlefield is not clear, or only can see a very small part, why do this? How did you succeed? Such a critical problem may be vague and not quantifiable as an actual work ...

Individuals have summed up the possible solutions to such problems

1. Information missing: The team's information is missing, you just get a small map, can't see the whole map.

2. Cyclical problems: A lot of things are cyclical, for example 10, 5, 3, 2, 1 years of long-term vision. or 4-quarter, 3-quarter, 2-quarter goals, you or the team only know the extreme forward or only the extremely short-term.
3. Implicit knowledge: the "tacit knowledge" point in this issue is too much, very difficult to language! Say that the problem is a bit like college students to the primary school to the first lesson, in turn, college students want to understand the difficulty of pupils, and then may say a bunch of nouns. And the stereotype of your nouns, people are still different analogy "water effect" you see under "Figure 5" under the image of Baidu, these effects are different for programming. Let's say you write the first customer or the leader incorrectly, then change the second one, the third one, and the project dies.
4. Half words: This is similar to the previous one, but should not belong to the "tacit knowledge" analogy only half of the word like "architecture", assuming that for a program ape he may understand as "technical architecture", assuming that the security settings may be understood as "security architecture", assuming that the architect would destroy the "Application Architecture", "Technical architecture", " Security architecture, "business architecture", etc... Omit 10,000 words, and this sometimes raises an interesting thing. What may be proposed is the technical architecture. The program ape made it. Because he is most exposed to this, but the architect is confused perhaps you have made a "business structure" ..., and in turn assume that you ask more than the proposed person may be a customer or leader will be annoyed ....
5. Things are not clear: demand or the vision of the person itself may not be clear or indecisive he is expecting you to give the answer. Or this thing is an experimental one, or a special long-term goal, such as the 5 grade of the fact that it would not be too clear in 5 years, staff and technical personnel may be uncertain. These are the natural fog and the basic can not be completely clear only relatively clear.

.... There may be a lot of situations but the types are almost identical. Suppose you want to write hundreds of articles. Just like a spam message. Suppose you have a phone number to kill which may never be blocked, so this is no longer a one of the write.

Figure 5: Baidu Search "water wave effect"

Ii. Coping Strategies

For this kind of problem countermeasure, actually this basically belongs to the communication \ The communication \ The participation and the question, the communication actually is all the participant's thing ...

First, we need to understand a core principle. Our real goal is to get the project product done. This is the first place. Whether the customer, the leader, or the research and development staff, in fact, in this matter everyone is a collaborative relationship, division of labor is different. are equivalent to "project biology" of the different organs have a heart, can be kidney, some brain which organ is not good use is uncomfortable, so we need to work together to the vision or long-term goal gradually refinement. It's not good for everyone to be disgusting, so no matter what the role is. Or some people have a natural history of the gap between this should be put down, and strive to try to make things clear, otherwise do not team up. If you want to team up, even if the way of thinking is very difficult short-term unification. But at least want to do this thing well this is necessary, otherwise it is disband good don't waste youth.

So strengthen communication, participation and degree is the first, do not communicate and how things will not clear, afterwards discuss who is wrong more meaningless ...

For information missing, periodic superposition of similar situations, it is best to try to see the full picture of the superficial ~ fine. Suppose you are the one who makes it necessary for workers to see the whole picture in such a way that everyone will consider things more rationally, reduce the possibility of being threatened by unknown threats in the fog, especially when you are a project manager explaining the UI design as much as you can, by sending a button or icon. Instead, try to give the desired goal to the UI as much as possible, because in the UI you don't necessarily understand that it is right, assuming you are a worker who assumes that doing so will affect the progress or outcome of the project, and that the author does not realize that it should be presented in time, Of course, it is necessary to assume that the author is the leader who may be able to handle the matter or need some skill.

In the case of "tacit knowledge" or "half-word", it is still not clear that the communication should be used as much as possible, with fewer words or words, and no animation.

There is also the use of intermediaries to adapt the "adapter mode." For example, poor business is a bit of a big analogy to pure technology and pure market natural very difficult to communicate. At this time can find "product Manager" adaptation, there may be a 20 years of research and development and 3 years of research and development is not able to say a lot of things, then also need about 8-15 years of research and development suitable for, assuming that the type of business, The double superposition of experience may find a suitable person to be able to match more difficult analogy a 20 years of research and development and the 20 market hypothesis have a disagreement. This may not find the right person to match. Only two of you can be honest and ready to sort it out.

For things that are not clear class. The short term is very difficult to see the whole picture. Is that you need to know as soon as possible that this is not clear! and step by step to do it never clear to clear, it depends on your comprehensive ability, and play the real-time strategy game when the full picture Allbright which is the comprehensive experience of strategic and tactical integration strength ...

Iii. Summary

In fact, that is the exchange, communication, collaboration, such issues are not in fact a separate software development, no matter what kind of events are more than one person may exist, find a strong relationship between people and things gradually solved is the benevolent, Of course, it doesn't have to be done immediately. Some things just need some time like you have a headache to take the medicine is also need a half an hour an hour to be effective, so sometimes need to calm and so on is also very important (cool not to procrastinate, give up oh ...) ）。

-- and finally: maybe bad things happen, but we still have to move on in difficulties--Wish: Work is smooth!!!

Advertising Promotion

Shenyang Golden Building Digital City Software Co., Ltd. Geographical information solution provider: http://www.jjgis.com.cn
Han Wei electronic official Micro store address:

Userid=316021702#rd "target=" _blank ">http://weidian.com/?userid=316021702#rd

Breaking through the fog and moving forward in difficulties--project, schedule, goal management