Project manager insights
The past week I been talking the role as Project manager in my team.
This is a tought role witch usually don’t instantly shows result and may feel unappreciated in the beginning.
But wile the project run you slightly start to see result and it’s a very appreciated role after a wile if you work hard and are stubborn.
So I would like to share a few insights from this experience.
Clear goals
Make it super simple for everyone to know what’s expected from eatch one of them and what the members expect from the team.
This makes individuals feel like part of the team and makes it easier to for individuals to focus on there work when they don’t’ need to think of what there are suppose to do.
Push the group forward
The project manager aren’t necessarily the one the one that makes the big decisions in the group but he can make suggestions to move forward in the progress.
For example if the team are stuck in a long discussion he can figure out what everyone seems to agree on and ask a simple question as:
- As I understand it seems like everyone has agreed on “something” is that correct?
If the answer from the group is yes then the group have made a decision and if the answer is no then you have localized a topic where the team has disagreement.
Either way it’s helpful for the group to know what they have agreements and disagreements.
Controll without controlling
A project manager isn’t’ necessarily the same as being a leader. The reason for that is that is when working in a creative team we want the individuals to express themselves and come with suggestion and ideas. If you instead take a leader role and try to tell them what to do it’s a risk that creativity gets shuffled away. Or even worse they may choose not to listen to you.
In the other hand if you don’t give the team any suggestions they are likely to not work as a team and the final outcome and motivation may suffer from that.
So I would suggest a project manager should instead be a guide that suggest tasks as far as it’s possible.
Instead of saying “you are going to do this” “I would say” “I would suggest you do this because it supports the team in this way”
Adapt to group and members.
It’s about being observant, ask questions and listen. Everyone is different and no project module works for everyone.
Of course no one is similar and every team and individual requires a different approach.
It also important to take notice of different phases of the project.
For example in the beginning the team probably need a loot more leadership and guidance to get going while after some time they might instead have other needs.
So when I plan my projects I always take in account the different phases that I except the team to go throughout.
Bridge comminucation between team-members
The team members need to focus on their task so too provide value as PM a excellent task is communicating.
That could include arranging meetings, organize schedule systems or a easy thing as asking people what there doing.
Deal with conflicts
This is a hush topic but I belive differences and frustration in the team should be dealt with in a early stage of the project.
To bring this up is may directly bring up conflicts witch can be scary and time consuming.
But ignoring conflicts would in the other hand slow the project down in the long run with lack of motivation and frustration.
So I would say a good PM can quickly notice and deal with upcoming conflicts for the teams best.
Folowups
Check with teammembers if the tasks they signed up for is been completed.
If it has it cold just be a way to make the teammembers feel appreciated and motivated for he’s/her work.
If not it you may have encountered a issues where you as PM can step in to solve it.
What do you think? Am I on the right track?
