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

Absrtact: At work we often encounter the following similar "fog" scene, we can not see the direction, repeated trial but found still difficult, how to make the project or product direction clear? Break the fog? ......

I. Analysis of problem situations

Here's an example of the movie "The Fog" scenario ...

Figure 1:

1, a group of people began to appear 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 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 a new threat! It's always hard to get you out of a higher winning job plan.

Figure 3:

3, and may also be very injured, may be in the "fog" in the location of the time, there are some monsters or tentacles damage some combat effectiveness .... A lot of things here omit 10,000 words.

Figure 4:

4, and then with teammates back to the place (small supermarket), team confidence combat effectiveness has been hit, the team including research and development \ Leader \ Customer anxiety increased, but also need to regroup try to try to go outside the world ....

If the map is actually better than that, some of the research and development of the scene, the manager or the developers of the entire battlefield is not clear, or can only see a very small part, why do you want to do so? How did you succeed? The ambiguity of this critical issue may simply be an outline of the phrase that cannot be quantified into practical work ...

Individuals have summed up the possible causes of such problems

1. Information missing: The team's information is missing, you just get a small map, you can't see the whole map.
2. Cyclical issues: Many things are cyclical, such as 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 long-term or only the extreme short.
3. Implicit knowledge: the "tacit knowledge" point in this matter is too much, it is difficult to be linguistically! To understand the problem is a bit like college students to the high number of first classes, in turn, college students want to understand the difficulty of pupils, and then may say a bunch of nouns, and your noun stereotype people are different like "water wave effect" you see under "Figure 5", these effects are different for programming, If you first write the first customer or the leader said wrong, then change the second, the third such experiment to go on the project died.
4. Half words: This is similar to the previous one, but should not belong to "tacit knowledge" such as saying only half of the word like "architecture", if for a programmer he may understand as "technical architecture", if the security settings may be understood as "security architecture", if the architect that would destroy the "Application Architecture", "Technical architecture", " Security architecture, "business architecture", etc... Omit 10,000 words, and this can sometimes lead to an interesting thing, what might be asked is the technical architecture, the programmer made it because he is most exposed to this, but the architect is confused maybe you do a "business structure" ..., and conversely if 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 think clearly or indecisive he is expecting you to give the answer; or this is an experimental one, or a special long-term goal, such as the 5 grade, this is actually not too clear. Within 5 years, personnel and technicians 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 type is almost the same, if you want to write hundreds of, it is like a spam message if you 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 \ Communication \ Participates the question, the communication actually is the whole participant's thing ...

First of all we need to understand a core principle, our real goal is to do the project product well! This is the first, whether it is customer, leadership, or research and development staff, in fact, everyone is a collaborative relationship, division of labor, are equivalent to "project biology" of the different organs are the heart, can be a kidney, some of the brain organ is not good use is uncomfortable, Therefore, we need to work together to make the vision or long-term goal gradually refined and clear, do nausea for everyone is not good, so no matter what role, or some people have a natural history of the gap between this should be put down, we must strive to make things clear, otherwise do not team up, Since we want to team up everyone even though the way of thinking is difficult to unify in the short term, but at least it is necessary to do this thing, otherwise it is disband good not to waste youth.

So strengthen communication, participation is the first, do not communicate not to participate in the matter how can not clear, afterwards discuss who is wrong more meaningless ...

For information missing, periodic superposition of similar situations, it is best to see the full picture of the superficial ~ fine, if you are the author of the need to let workers see the whole picture is necessary so that we will be more reasonable to consider some things, to reduce in the fog by unknown threat to kill the possibility, Especially when you're a project manager explaining to the UI design, try not to send a button or icon, but try to give the UI as much as possible, because in the UI you don't necessarily understand the right thing, if you're a worker, if you find that doing so will affect project progress or results, And the author does not realize that it should be put forward in time, of course, if the author is the leader of the possible to deal with this matter or need some skills but still have to do.

For the "Hidden knowledge", "half word" similar to the situation is still not clear, the exchange as much as possible with the picture, less words or words, in no use animation. There is also the use of intermediaries to adapt to "adapter mode", such as poor business is a bit large such as pure technology and pure market natural 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, it also takes about 8-15 years of research and development to match, if the type of business, Experience double superposition of the situation may find a suitable person is also more difficult, such as a 20 years of research and development and the 20 market if all the same, this may not be able to find the right match, only two of you to be honest to comb clear.

For things that are not clear class, short-term is difficult to see the full picture, is to need you 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, in the end is the Exchange, communication, collaboration, this kind of problem is not a separate software development, any event class of more than one person may exist, to find a serious relationship between people and things gradually solved is the kingly, Of course, it doesn't have to be done right away. Sometimes it takes a while for you to take a headache and take a pill that takes a half hour and an hour to work, so sometimes it's important to be calm and so on (cool not to procrastinate, give up oh ...) ）。

-- Finally: maybe bad things happen, but we still have to move on in difficulties--Wish: Work smoothly!!!!

Advertising Promotion

Shenyang Golden Building Digital City Software Co., Ltd. Geographic information solution provider: http://www.jjgis.com.cn
Han Wei electronic official Micro store address: http://weidian.com/?userid=316021702#rd

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