Shulou(Shulou.com)06/03 Report--

This article mainly explains "sharing the four Rank in the delivery work from a case analysis". The explanation in the article is simple, clear and easy to learn and understand. let's go deep into the editor's train of thought. Let's study and learn "share the four Rank in the delivery work from a case analysis"!

Background information:

Some time ago, we used the wiki model to update the work weekly report, and wanted to change the weekly report from a passive delivery form to an active update and periodic update. Usually we will make the plan clear on Monday, and on Thursday we will go over their progress on a small scale. There is little specific discussion on who did what at the meeting, and only after running-in for a few months can we basically adapt to this model.

On Monday, I mentioned a task: when the anniversary of the company is approaching, there will be a lot of activities. We need to do an inspection of the existing services to find out in advance the bottlenecks of configuration, services, and capacity. We especially need to pay attention to the business in the direction of the cluster, which mainly covers monitoring and alarm.

As the task went on, everyone seemed to understand and nodded again and again, but in retrospect I thought it was a very poor job delivery.

I take this as a case to analyze.

First, the time node of this task is not clear. Since it is a task that everyone has to complete, is there a time point? at present, the time point is obtained by reverse reasoning, and no updates or changes are made on Friday. So the time can only be pushed forward, so it can be basically made clear that a time point should be Thursday, but Thursday is not specific and clear, it may be noon or night. Including finishing this task after work, different people actually have different understandings (for example, some people get off work at 9:00 in the evening, he will think that the time of delivery is around 9:00), so a relatively clear time can be set as: before noon on Thursday, so that everyone has no ambiguity, and also allows the task to really run.

Second, the timing of this task has not been discussed. For example, we set this thing to be completed by noon on Thursday, and we can push it back. For example, Zhang San thinks that this thing should be done on Wednesday and Thursday. Wang Wu thinks that this thing should be done on Tuesday and Wednesday. There is no problem. Everyone's rhythm is different, but the task can be disassembled. For example, monitoring and alarm are one kind of task, which can be done together. Cluster services can be a separate type. Configuration capacity assessment and so on may be divided into a module, so these will take some time, and each part of the work can be considered one by one.

Third, the output and delivery form of the task is not clear. For example, when we have done this thing, how can we prove that we have done it well and correctly? there are many forms, such as inspection reports, such as visual presentation. If there are 1000 servers, it is very good to directly use the way of patrolling and inspecting the market. At this time, how to sort out your work rationally. If it is simply said that the inspection is over, there is no problem, I think anyone will have questions, right? What aspects have been checked.

Fourth, the ongoing status and progress of the task delivery, take the delivery before noon on Thursday as an example, most people deal with it without any feedback on Tuesday and Wednesday. If you need some assistance to confirm with the leader or other colleagues on Thursday morning, it is already lagging behind, and once things begin to lag behind, the quality and efficiency will be greatly reduced, because these delays may rely on the support and assistance of others. In addition, there will be some uncertainties in your work, and if you don't confirm it until near the time point, you will feel that you haven't taken it seriously, or even started to do it. Of course, the form of the weekly work report I mentioned at the beginning is in the same line as the daily newspaper. The update of this wiki mode can be updated at any time and can be used as a mirror of one's own work, rather than a work delivery that needs to be updated before it is updated.

To meet the above points, can be regarded as a basic Rank, of course, there should be a lot of people still can not reach this stage. We can lower the standard a little bit:

1) people who are often unable to deliver work normally can be regarded as the first Rank.

2) the person who can meet most of the conditions is regarded as the second Rank.

Third Rank:

Before starting the analysis, let's go back to the problem of origin, what is the goal of our inspection? the goal of inspection is definitely not to output some documents and output forms, but to find potential problems and solve them in a timely manner.

If no problems are found in the inspection, either the usual basic work is solid enough, or it is not serious enough, and the work is scrawled.

Let's go a step further, now that we have found a potential problem, the subtext is that it needs to be fixed, so we should have completed the repair of the potential problem by Thursday, so we should find the problem a little earlier and set aside some time for repair.

To reach this level, the delivery and collaboration of a lot of work should be comfortable, usually of quality and quantity, and there is a higher-than-expected quality delivery.

In short, people in this Rank have developed good thinking habits and behavior patterns.

Fourth Rank:

This position mainly lies in ideology, and we often say that knowledge and practice are one, so these tasks should be planned in advance and arranged in advance. Here is divided into three levels, one is to set goals, to be able to make reasonable goal plans according to the current situation, this is a more self-driving work mode, and the self-driving force in the workplace is actually very difficult to define, it is basically difficult to decide how to start, but the results are clear and visible. The second is task disassembly, which is a general deficiency found in communicating with some colleagues, that is to say, this kind of person is very scarce and popular at work, such as a vague thing. He can disassemble some feasible steps according to the current situation and be able to adapt to the current business situation. The key is that these steps can be landed, which is very rare. The third is the thinking model, with execution and planning, already have the basic conditions, on this basis the thinking model really determines your efforts and value. There is a more rigorous judgment logic, that is, your thinking model can solve most practical problems, and can adapt or answer more or even unknown problems. For example, the road taken in the process of natural language processing, from the study of rules to the study of statistics, from the perspective of rules, even if the grammatical rules have been very complex, still can not solve most of the language situations, but from the idea of statistics, give up grammatical rules, establish a statistical-based model, and use Bayesian and Markov processes to build a new model, the accuracy and practicability will be greatly improved. At this stage, the competition is also the pros and cons of the thinking model.

Thank you for your reading. the above is the content of "sharing the four Rank in the delivery work from a case". After the study of this article, I believe you have a deeper understanding of the problem of sharing the four Rank in the delivery work from a case analysis, and the specific usage still needs to be verified in practice. Here is, the editor will push for you more related knowledge points of the article, welcome to follow!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.