The weekend is here, you called three or five friends, called a wave of people in the group, and formed a round of werewolf kills. You became a judge, watching everyone laugh and curse, tit for tat.
You look at the big picture calmly, record the process, announce the winner, and replay the game. After the game, everyone said that you Latest Mailing Database are a good judge and hope you will be a judge next time.
Then you are more than enough to be a good project manager.
Let's take a look at the similarities between judges and project managers:
The judge doesn't care who wins or loses, but only cares about whether the game can go through the process completely - the project manager does not care about the internal details of the project, but only cares about whether the project can be fully delivered.
The judge does not participate in the game discussion and is the god of the game - the project manager does not need to do it himself, but is the supervisor of the project.
The judge needs to record the surviving players and the dead players - the project manager needs to record the member execution status.
The judge is the only one who can explain the ins and outs - the project manager is the only one who knows the overall flow of the project.
The judge needs to review the game for everyone - the project manager needs to report the progress and results to the superior.
Does it sound easy?
However, in all werewolf killing games, the judges are veteran players, and no novice will come up as a judge.
Why?
Because scripting is easy, adapting is hard.
How many times does the judge need to:
Explain the rules to new players.
Make decisions for arguments.
Decide on the order of speeches.
Inspire everyone with new gameplay.
Like judges, project managers need to have a strong overall grasp and be good at dealing with emergencies. If a project manager can't do these things, it will be difficult for him to manage effectively.
Then, through werewolf killing, I have summarized several key points for being a good project manager:
1. Process over technology
Judges can understand "the police", "kill", "golden water" is of course the best, but it is not important to understand. For judges, it is more important to know " where the game is going ".
The same is true of the project manager. He does not need to know the technical details of the project itself, but he must know what needs to be done in the next step of the project .
No one blames the project manager for a technical problem, because it's an engineer's problem. But if the project process goes wrong, the project manager must bear the brunt.
2. Appropriate delegation of powers
As the server of the game, one of the taboos of the judge is to interfere in the game process. Intervention by a judge can cause players to feel that "the judge is not impartial enough ".
As the service provider of the project, the project manager should not be too involved in the technical details of the project. The best project managers are those who " keep their independence ".
If the project manager interferes too much, the employees who are involved will feel that their professional skills are despised, and the employees who are not involved will feel that they have been discriminated against, and they will not be thankful in the end.