Project Manager, don't let the monkey jump back!

I haven't recommended a book for a long time. Today I recommend a good book in the workplace: Don't let monkeys jump back. The "monkey" that jumps in the workplace "? What's going on? I am very confused about this. Do managers like pet monkeys in the office? Well, there is a cute pet monkey. I saw the photo a while ago. It's cute. With a question, I feel childish. This book is actually a classic of enterprise management, written by William anken III, a world-renowned corporate manager. In the United States, "monkey on the back" has become a classic enterprise management metaphor, that is, the so-called "industry consensus ". It seems that I have been outdated for too long. So what is this "monkey? The following is an example: Manager Zhang San handed over to employee Li Si for a task. Executing, Li Si found the problem "a", so he reported to Zhang San and asked what to do. John gave me a bit of thought and told Li Si That You Would "X. Li Si followed the "X" method and found the problem "B". He immediately reported the request to James, "I followed 'X' and there was a 'B' problem, what should we do next? ". Because the "X" method is James's idea, he had to continue to make up his mind: You "Y. Soon, Li Si brought about the problem "C", so Zhang San again prompted "Z ". Later, Zhang San and Li Si will always work happily together... What exactly is this? Why did the task of Li Si become a common task of Zhang San and Li Si? Further, if the final task fails, who is responsible? I'm afraid it's James, not James. Because every step of Li Si is performed according to John's instructions. Oh my God, our poor Manager Zhang San. In the above example, do we find a monkey jumping? Yes, it is a "task ". The "task" monkey will be on Michael Zhang's shoulder for a while, and then jump to Li Si. Of course, the master won't simply settle on it. William anken III pointed out: in fact, it's not a breeze, not a trigger, or a heart, but a responsibility. The master further pointed out that the "responsibility" monkey should be locked on Li Si forever. Why? In fact, assignment is an authorization. Accepting the authorization from the superior means taking responsibility. Managers should never tolerate "reverse authorization", that is, their subordinates should return their responsibilities to managers, for example, Li Si. The words of the Master are advanced and accurate to all corners of the world. I think this is not only a rumor to the enterprise leadership and middle-level managers, but also a great inspiration to the project managers. In the Chinese workplace, project managers are often the core motivation of projects, and there are plenty of projects that are completely different from project managers. Project managers are also fully aware of this and often overestimating their capabilities to take on various responsibilities in the project. Result: The monkeys of the project team ran to the project manager's shoulders. I suddenly remembered that I had been full of monkeys and almost vomited. The master did not stop at pointing out the problem. The "master" font is now his ideological depth. Anken III said: corporate executives should change their own ideas. From being dependent on the individual abilities of entrepreneurs to being dependent on the organizational abilities of employees. Entrepreneurs must truly build their enterprise growth on the basis of employee growth. Whether employees can grow, become independent, and take responsibility is what it means to let employees take care of their monkeys! I am very touched by the words of the master. Maybe the project manager should also change his mind. Lock the "monkey" of the team member to himself. This is by no means the project manager is lazy or irresponsible. On the contrary, this can maximize the independence of the team members and continuously improve their problem-solving capabilities. I think the project manager is the project manager responsible for member growth and the project manager responsible for project success. So how can we lock the "monkey" on the team members? Wait for the next decomposition.