[Management tips] How much do you know about "Queuing?

Scenario Reproduction
======================================
Today, my friend asked me to buy a ticket. I just went to the train station and agreed.
When I lined up in the ticket hall, I accidentally heard that the 6-year-old boy asked his mother, "Why are we queuing here? Why is there no number generator here ?"
"It's coming. It's coming soon ." Mother stroked the child's head and replied.

I hesitated. "Sorry, yes! Why is there no number generator here ?"
======================================

In this way, this problem has been entangled with me until now.

Everyone has the experience of queuing, waiting for customs, buying tickets, sending remittances, and waiting for handling. Queuing management is the reason why queuing exists, and even leads to the invention of the number queuing machine.
Queuing is a simple process and can be seen as a balance between supply and demand. Waiting for handling (buying tickets, checkout, remittance, and so on) is a request; a window for handling the matter, or a side that provides the ability to handle the matter, is. If the team is too long and the waiting time is too long, the supply is in short supply; otherwise, there is no one in front of the window, and the door is too busy. It seems that there is a small problem in the queuing of a window, which reflects a lot of truth.

There is nothing to say about a window vs a queue. the processor's speed determines the length of the queue.
In this case, multiple Windows vs multiple queues and multiple Windows vs one queue are very different.
※Even with the same standard procedure, the processing speed varies with different persons. This is determined by the maturity of the handler and the complexity of each case. For example, it is also a banking business, with withdrawals, remittances, cards, and loss reports.
① Multi-window VS Multi-queue
After nine queuing experiences, I felt that the progress of other teams was faster than that of my team. when I switched to another team, the speed suddenly slowed down and I was very annoyed.

② Multi-window vs one queuing (similar to a number generator)
Most people think that this approach is just to prevent the queuing staff from sending a packet to a window (model window) and let each window "fair" handle the same number. Is that true?

Here is a theoretical example:
There are three windows, 15 of which need to handle the same business. The average time for each window to process the business is 3 ~ 5 minutes.
Mode 1: There are five people in each window, and the fifth person has to wait until the first four have completed the processing before his turn. He wants to absorb all the "fluctuating" time, or 12 or 20 minutes.
Mode 2: everyone in the team will enjoy the efficiency of the three fastest windows. The average processing speed must be less than 4 minutes.
In this way, the efficiency of model ② must be higher when the processing of the 15 people is completed, and it is fair to everyone. Isn't that true?

A friend was impatient and asked, "What do you want to say when it's so cloudy and foggy ?"
There is a workshop with five employees who produce 200 screws each day. The factory produces 1000 screws each day.
If we regard "1000 screws" as "Queuing", and "5 employees" as "Windows", can we use mode ② to greatly improve production efficiency. Maybe 1000 screws can be produced in six hours.

Some people say that I am crazy. Are employees so active? In this way, 500 pieces of data cannot be produced in a day ."
Yes, I admit it. If you use pay-as-you-go, you can solve the problem.
※This may be the source of "pay-as-you-go. Explain)

I also thought about applying pattern ② to project management.
"Tasks" are long queues (task dependencies are ignored for the time being); "team members" are seen as "Windows"; and "performance pay" is also guaranteed.
What about last?
It should be feasible in theory, but I don't know why it is always impossible.
→Some organizations do not strictly manage performance appraisal, and have no specific data to explain it. In addition, they even say "Excellent, good, moderate, and poor" to managers ", employees have lost interest in their public trust.
→In some organizations, the "performance salary" is not big, and no one will give up "Idle Work" for RMB 2 or three hundred ".
→ In some organizations, the "Performance Appraisal" system is strict, and the "performance salary" fluctuates greatly. However, most employees are not the bottom-layer people who rely on the "pay-as-you-go" service to maintain their lives, at ordinary times, they sniffed out the inertia. If a small number of employees make a "performance salary", they will be regarded as a different type of employee, slide and flattering. After a long time, only a few people will be lost.
This is the current situation of most organizations. Have you seen it?

By the way, after so long, I have not answered any questions from the children.
The ticket sales business adopts the model ①. It is reasonable because the ticket sales business is relatively simple. The two sides only need to find out the starting point, the end point, the departure time, And the fare, and then make a payment to complete the entire ticket purchase process, if the management through the number server seems to be less than worth the candle, it will reduce the efficiency of "fail (just my personal opinion)

--------------------------------------------------------------- Cainiao-level QQ management exchange group: 295388584 interaction (management experience exchange site): glxdjlz just got started, cainiao collection ......

 

[Management tips] How much do you know about "Queuing?