How to write year-end summary

First, , Why do most companies write year-end summaries ？

I think the essence is —— Review and summary of my work in the past year , Find out the experience and lessons , Find out the regular knowledge , Do better for next year's work . Of course , This is also a time for managers to have a more comprehensive understanding of their subordinates , It has certain reference significance for managing each subordinate and performance evaluation .

How to write a year-end summary ？ We'll start right away .

1、 List the five most satisfying things to do this year

In my submission , You should list at least five things you are most satisfied with , These five things can be agenda work , It can also be difficult or challenging, or very valuable .

So with these five things , How to write the highlights of our work ？ Let's continue to look at the following .

2、 Analyze everything from four thoughts

Most of my readers are programmers / The product manager , I suggest you summarize from the following four dimensions , It will definitely brighten the eyes of your leaders ：

a、 Result dimension

As a result, this dimension focuses on the value of what you do , There will be some differences in the performance of different types of teams .

If you're a business development team , It is inevitable to summarize from the business dimension , For example, the daily work of a business user / What is monthly life . For technical optimization requirements , Mainly think about the value that technology optimization brings to the business ？ For example, this technology optimization makes the business P2 Fault from 3 Times reduced to 0 Time . If you're a team leader, For the results of your management measures , This measure is how efficiency and quality improve .

If it's you / Infrastructure team , I suggest your results from the performance of the system 、 Availability and cost .

If you are a support team , That is, operation and maintenance / test / Efficiency engineering and other teams , I suggest you start with quality 、 Think and summarize the aspects of efficiency and cost .

b、 Data dimension

The second dimension is data , Without data, there is no way to quantify , There is no way to compare and improve , So data is very important ！

Such as “ Improved system performance ” This relatively empty description , Should be changed into TPS/QPS From how much to how much, this specific description is the positive solution .

When describing the results through data , Not only do you have to list the relevant data , And you should know the meaning behind these data like the back of your hand , Especially for the evaluation criteria of data , Through the evaluation of data, we can cultivate our business thinking .

such as , The same is to put a APP Increase your daily life 5%, For a relatively stable product such as Alipay, such a business is very difficult. , But it's not enough for a new business , Same thing , from 10% promote 15% And from the 80% promote 85% , Different meanings .

Another example , You change the availability of a core system from 98% Upgrade to 99 %  And from the 99%  Upgrade to 99.999% , The cost and difficulty of the latter is much higher than that of the former .

A lot of times , We feel that there is no way to describe it with data .

But the truth is , It's not that you can't describe it with data , But you didn't collect relevant data , I haven't formed this habit .

c、 Technology dimension （ Product students are professional fields ）

For programmers , After finishing a project or scheme , What improvements have been made in technology , What new technology have you learned or what deeper understanding have you had , You can try to systematically summarize , It's important ！

such as , We used... When designing the scheme redis cache , However, this does not mean that we have a deep and comprehensive understanding of caching , What pits did we encounter in the process of landing and how to solve them , For example, what about cache penetration ？ How to set the expiration time of cache in different business scenarios ？ Whether you need to consider secondary caching, etc , These need to be sorted out and summarized afterwards . Other areas of technology can be extended .

d、 Growth dimension

In addition to the improvement of the above technology , You also need to care about the growth of personal comprehensive ability , That is, the improvement of soft skills . For example, understanding the business 、 project management 、 Cross team collaboration 、 Communication skills and ways of doing things, etc .

These abilities may not be so important in the year-end summary of low-level programmers , But for architects / Students above the technical manager level are very important .

Take the understanding of business as an example , You can think from the following perspectives ：

What is the business scenario ？

Who are the target users of the business ？

What are the characteristics of the target users ？

What problems does the product solve for the target users ？

Why do users like / Hate this new feature ？

What is the realization method of this product ？

What is the difference between our competitors' products and ours ？

3、 Our problems and how to improve

such as , Here are the common problems of most young programmers , We can say that my own shortcomings, professional and technical foundation is relatively poor , Not very good at too much communication , In particular, it is difficult to communicate with strangers , I'm rather impetuous , Accuracy is sometimes not enough .

In addition, the overall awareness is not strong enough . Sometimes do things 、 Work only from yourself , Lack of understanding of some major decisions made by the company and the project , Although we have also completed the work to be done according to the requirements of the leaders , Psychologically, there are still some other ideas . There are still problems at work to see 、 hear 、 What I thought of but haven't done yet , There is also a need to further enhance the sense of responsibility and personal drive .

4、 Next year's plan and direction

except , You can develop according to your business / Technology Architecture / Support the team to focus on different to plan （ For details, please refer to the previous results ） Beyond the direction of next year , The next year can also be planned from the following three aspects ：

b、 Improve personal professional ability .

such as , Change your technical ability from P5 Upgrade to P6 , Then the details should be in daily work , Strengthen the study of professional knowledge , Accumulate rich professional knowledge , Be strict with yourself , Find and solve problems decisively .

We should have a rigorous working attitude and good communication and cooperation skills , Strive to improve their comprehensive quality , Do everything in your hand in a down-to-earth manner , Reflect more from every drop of every day 、 To learn more 、 More communication , Keep summarizing .

c、 Improve language communication and cooperation skills .

In practice , We should be more proactive in reporting to our leaders / Problems encountered by senior colleagues , And communicate more with colleagues , Learn their methods and working experience in dealing with practical problems . Through learning more 、 Ask more questions 、 Think more to constantly improve their practical work ability .

d、 Cultivate personal interests .

People with interests , Life will be happy , Just like I like programming , In addition to technology / Soft skills / Knowledge of growth, etc , The body is also important , In normal life , Exercise more , Improve physical fitness , The body is 1, Everything else is 0 .

The year-end summary is definitely a great reflection 、 replay 、 Opportunities to improve and improve yourself , Please face it seriously ！