Team efficiency model (2)

 

Team efficiency model (I)

 

Team Efficiency Model

 

Email confirmation

Problem

During Game Operation, O & M personnel are often required to adjust the online environment. After the O & M personnel are completed, they will reply in an email saying "the operation has been completed, please accept it ". However, there are often no one to accept. Find the cause and find out that the product colleague is initiated for the function, the planning colleague is determined for the solution, the configuration is provided by the Development colleague, and the testing colleague is responsible for the test. Everyone will receive an "please accept" email, but everyone thinks that other people will accept it, so it's okay if you don't miss me. Therefore, no one has accepted the request. In this way, problems often occur, and some are serious accidents.

There will also be many other things like this at work:

L no response is received after the document review email is sent. By default, no comments are received.

L no one has responded to a group's work schedule email. When the execution starts, the other groups are running again and need support.

L a colleague applied for a break. No one responded that there was an arrangement. When everyone else had a rest, they jumped out and said there was an emergency to do.

 

Solution

All owners should be truly responsible. However, this is not an operational task. An operational solution should be a specific, fruitful, and measurable rule.

Simple: Everyone needs to confirm the content they need to respond to by email.

 

Effect

If you have not done your work, have you done it on time? The effects can be reflected in the confirmation email.

The confirmation email is sent, indicating that you have done something you need to confirm. If the message is not sent, either you did not confirm the message or you forgot to send the message. However, no matter which one is sent, you are remiss and the result is the same, that is why this chain has fallen from you.

The time when the email is sent is the time when you confirm the completion. Others are waiting for your email to determine whether the task is completed. If you send it late, others will wait for you and the whole task will take a long time to complete. Efficiency reduction is your problem.

The confirmation email should list the confirmation results. Which aspects meet the requirements, which are problematic, and which are unexpected. If you write OK, but find that there is a problem, then you confirm the effect is very poor, the sense of responsibility will be questioned.

In short, with the confirmation email, the quality of each link in the work can be quantified, and the results can be evaluated afterwards, in order to identify short boards and improve efficiency. At the same time, it also avoids time waste, repetitive work, and chaotic planning due to lack of timely confirmation. The efficiency of the team has been improved here.

 

To be continued...