As project manager we are chartered with not only creating a plan, but getting the team on the same page by providing the leadership necessary to get this group of individuals to act and deliver as one. Like most things, there is no single style of leadership that must be followed in order to be a successful leader for your project. There are many different styles the can be leveraged and in most cases those styles are put into action depending on the situation at hand.
In observing the best project managers over the last 20 years, I have noted some common themes in the successful application of different leadership styles. The themes coalesce around four types that I will characterize as the following:
- Task Master
Let's explore each in turn:
The Task Master
Bring out the whip and let it rip, says Brian a senior project manager for a financial services firm in Boston. Being a task master may sound like you are evil and overbearing person, but in reality there are times a team needs to put their collective heads down and get things done. In those cases, a project manager will need to make sure that there are no distractions taking away from that focus.
As a task master, you want to provide an environment where each team member has blinders on in order for them to focus on their deliverables. With this leadership style, it is essential to make sure the plan is clear and the responsibilities are well known by each team member. Each project and each organization will define and determine what shape those blinders take. It can be from moving the team into a single location to be focused, daily group check-ins like a Daily Scrum, or a daily personal reminder by you as the project manager to each team member to see where they stand with their deliverable. Your focus as the task master is the plan and keeping it moving forward while making sure any distractions are dealt with quickly.
There can and should be a positive nature to the being a successful task master. It is hard and not everyone is going to like the enhanced attention that is focused on each member of the team. If it done without malice, as a result of poor project management, or out of spite, being a task master can produce successful results.
There is a delicate balance that you need to be aware of as a task master. The dark side is always close at hand and is easy to slip into if you dont keep it in check. There are two aspects to the dark side that I will call out. The first comes from a personal place where you are taking advantage of your position to make life miserable for certain members of the team or the entire team. As you can imagine, there is not much good that can come out of being this type of task master. The best way to avoid this path is to remember that the project is all about business and it is not personal. If the situation is truly personal, then dont try to deal with it alone. Get help from your management and human resource department. You dont want others or the project to suffer because of few bad folks.
The other aspect of the dark side generally falls squarely on you as a project manager and that is the result of having to be a task master because of poor project management. Teams or individuals never respond well to having a task master, but especially when they are not at fault.
Projects always have moments where things slip and original commitments are at risk. What needs to be avoided is having those risks not be as a result of poor planning or leadership by you as the project manager. This is your failure and not the team. If it is true, then be honest with the team on what happened and what needs to be done to get back on track. They will not like it but will be more willing to help out if they know the full story.
As a leader it is important to encourage and to provide positive reinforcement, especially during long and complex projects. The advocate style of leadership is more than being a cheerleader for the team. It is about being there for the team in order to pick them up when the need help ― to provide that pat on the back when things go well, and to have an open door when there is a need to talk. The advocate is one of the most unselfish styles as it is truly about putting the team and their needs first.
To be a successful advocate starts with creating the right environment. Making sure at the start of the project that you have done your best as the project manager to determine the needs and wants that will be required for the team to execute. Examples of what makes up an encouraging environment include making sure they have the right tools, the right work space location, the correct user name and password, a strong and reasonable vision, a plan on how to achieve objectives, and letting the team know there is someone there who is looking out for them.
The advocate is also looking for opportunities to promote the team and team members not only within the project team but also outside with management. As project manager, you are generally placed in many situations that allow you to publicly represent the team and the project. As the advocate, you can begin to share that spotlight with other members of the team as appropriate. The ability to present, run a meeting, or be the featured speaker because are great examples of how to provide opportunities for others to shine. The other is to call out the key accomplishments of others. This not only provides a nice feeling but it also shows management that the team is deep and successful.
There are times within many projects where a team or individuals require more than just encouragement, they need direction. The role of the captain is to gently guide a person or team in a general sense so they can stay on track, but still allowing the guided to to do things in their own way. As captain, your leadership comes through in the direction that is set, in helping provide the boundaries for the team, and to act a bit like the police―keeping watch over them to be able to make any course corrections that may be needed take place.
The captain leadership style is an active one. Although you are not explicitly providing the exact steps that need to be executed, you are still required to know what is going on at a detailed level. If you are truly hands off and willing to just be provided updates, then you are more at risk for failure.