What is the technical plan?

Recently, reviews of planning documents are always available. You can write it yourself, read it by others, and help people make suggestions.

These planning questions include the future language planning, public resource management planning, and industrial development planning of the company. However, planning is probably one thing that requires three or even five years of development in advance. Plan a general goal and then point out a route so that everyone can proceed in the future.

Many people may say that the future cannot be predicted, and planning is actually very difficult. The plan changes at any time. What is the significance of a longer plan?

I just want to talk about this. Some people believe that things can be planned, implemented, and succeeded. This is the way many entrepreneurs come along. I can't count on success in my career, but I agree with it.

Let's continue with our technical plan. I have to say that the technical plan is first of all an innovation process. It is the least easy to write out whatever you say. I highly respect those who have already written technical plans. Many of my experience stories are made to better help my partners and myself and make good plans.

1. The first problem encountered during technical planning is that you do not know how the person reviewing the technical plan looks at your plan. What should I do? For example, if you have a technical plan, you can draw a conclusion when presenting your goals, and then list many reasons to support your conclusions. This is very taboo. Why? First,

We need to figure out what the judges are doing? Judges are a group that helps you make a correct decision, or someone who helps you provide some technical inspiration and ideas. The previous case was for review, and the latter case was for technical support. Let's talk about the most common review. The idea of the judges is to check whether your analytical thinking before making your decision is correct, whether you should consider it, whether you have considered it, whether it is enough to consider the balance between advantages and risks.

Based on this idea, if you just want to prove that you are right, the judges can only try to prove that you are wrong. During some organizational reviews, such reviews may be rolled back at the beginning: the ideas are unclear and the method is incorrect!

The simplest method is to write out what problems we encounter. Then, we have several ideas about this problem. What are the advantages and risks of each idea? Finally, for each type of choice, you can also add your judgment results on the top. This is how it is listed

1. List problem targets

2. Proposed Solution list

3. Analyze each solution

4. Comparison Scheme

5. Draw conclusions/verify target support

In this way, it is easy for the judges to help you check in every step. Your plan will naturally come out.

2. problems that may occur during technical planning are the final solution, which cannot solve the set goals. The reason for this may be that we often come to a conclusion first and then add other details. However, we can use the document writing process to verify the rationality of our solution. For example, we set three points in the target, and the final solution is to solve two of them? Or are they all solved? If not, how can we solve it. This regression process is very valuable!

We have many cases, all of which are discovered. The final conclusion is actually unable to support the previously set goals. It seems that this is a simple problem, but this is not easy to do. Most of the time, the author thinks that he has come to a conclusion. The so-called preemptible, it is easy for them to ignore this in their judgment.

In fact, there are many other problems in technical planning, such as incorrect expressions, written things, and completely unreasonable logic. However, I think it is better to solve the problem from the "road". What kind of technical plan should we write before talking about how to write the technical plan skills.