Are you giving them the start they need?
Too often we don’t take the time to really build a strong project team. That’s a real shame because in order for a team to be effective and successful at what they are tasked to do, they must have a good start. A good start means that they are on their way to being a high performing team. It means that you – as the project leader – must give them that good start.
So how do you do that? Take these steps:
- Take the time before the project actually starts to get the team together in a social environment. Let them get to know each other on a personal level. This increases their comfort level and enables them to more easily develop a “team outlook.” It enables them to trust each other.
- Once the project begins, have a kick off meeting with the entire team. As a group, assign roles and responsibilities, decide on the approach to be taken to ensure the project meets its goals, determine how problems will be handled and decisions made. Remember you are the team leader with ultimate responsibility, but share that responsibility with the team. Enable them to participate in how the project will be managed toward its successful conclusion.
Now that you have the team off to a good start, keep the momentum going! - Allow the team members the autonomy to make decisions around their particular tasks. I’m not suggesting that you should be out of the loop – but allow the team to get the work done as they see best in order to meet the timeline, budget and quality needs of the project.
- On a regular basis – have a small team get-together (other than the regular team meetings) – go out for coffee as a group, have lunch out, get together after work for a few drinks or dinner out.
- Recognize the team members’ efforts regularly. When someone on the team has done an outstanding job, completed a task earlier than expected, helped out someone else, or solved a tricky problem, acknowledge their efforts and make sure the higher-ups know about it.
- If possible, invite team members to present status report updates to the stakeholders to give them visibility. This works in some businesses and not as well in others. But if it works in your company, why not give them the chance to be in the spotlight on occasion.
- When the project has been delivered, celebrate the successes. Take the team out for dinner and drinks after work or for lunch. Thank them for the efforts and for helping to make the project a success. Ask the sponsor and other key stakeholders to join in and also thank the team for their success. The team will appreciate it!
If your team is virtual, you can still make this work though sometimes it can be a bit trickier and take longer to build a highly performing team. Get them together for kicking off the team starting up and closing out the project if possible and then be sure to check in regularly via phone, email, the computer (such as Skype or Webex) and/or a collaboration portal.
What can you add to the list? How are some ways you have built your project teams? Please share with others in the Comments field below.
Thanks!
See related team posts here:
Hi Eleanor,
Thanks for your comment. It is absolutely essential to get the team together before the project kicks in simply to spend time getting to know each other without worrying about the project just yet. This makes managing problems, conflicts, etc. that pop up much easier to deal with before they get out of hand. That little bit of time spent to get to know each other better helps to build confidence and comfort in working together.
Thanks again for your comment and for reading!
Best,
Gina
I love your advice about getting the team together before a project! Managers tend to foist team building and development on people only when there are problems popping up; by then, some team members would already have less than pleasant relationships and may encounter difficulties in ironing out problems.
Hello Vicki,
Many thanks for sharing your post with my readers and with me. You have included some great ideas for team building. I’m glad you have enjoyed the article and found it valuable.
Thank you again for reading and sharing your post. I look forward to continued collaboration and an exchange of ideas.
Best regards,
Gina
Thank you for the great post Gina. There seems to be a trend of team building floating around this week. I posted some of my favorite exercises in a recent blog post at http://professionalprojectservices.wordpress.com. This includes a bingo card, work style preferences round robin, and mid-project retrospective. I’m going to poast a cross reference link to this post as well.
Reading you points, I have to agree that the more informal yet inclusive you can be or give them some acknowledgement or kudos, the better results you will have in teambuilding.
I look forward to the continued exchange of ideas!
Hi Ravi,
True…they prefer to be left alone to do their jobs – especially the more technical and more senior level they are. An approach you may consider is a “softer one” – (not saying you aren’t doing that now…but just a suggestion) – such as…”Hey…I’m wondering if it is possible to do “x” rather than “y.” I was thinking about it and I thought the “x” approach may help us to reduce the timeline for the project. But I may be missing something. What do you think?”
If your ideas are not related to reducing the budget, improving the quality or reducing the schedule or something else that would impact the project final deliverables – then why make them?
Hope this helps!
Best,
Gina
Hi. Thanks for the reply. I am working in IT sector. Though I am no expert in coding, my logic (I feel) is some times better than my techies. But they are simply reluctant to accept ideas from me since I am not a techie fundamentally. I don’t want them to accept my ideas without questioning but I just want them to consider it and take an objective decision. I can say its something related to point 3 in your article. They need 100% autonomy :-).
Hi Ravi,
What specifically do you find difficult about managing technical experts on the team? Of importance is ensuring that you rely on them for the technical expertise; especially since you don’t have it. Of course, if you don’t trust their expertise, that is an issue and it makes it difficult then for you to accept their thoughts on scheduling, budget, etc. When managing technical experts on the team, I try to learn enough about the technology to understand it from a high level and do ask them to explain to me in “laymen’s terms.” I also rely on their expertise for resource needs, budget and scheduling to be deliverables. Please provide a few more details about what in particular you find difficult and I can better provide some specific ideas.
Best,
Gina
Excellent info. What I often find difficult is to manage certain team members who are technically more experienced than me. Do you have any specific suggestions in this case?
Hi Robert,
Thank you! I’m so glad you found it of value. What you do when you see a team is stressed is perfect – it helps! Sometimes I try a cartoon, or, for example when we get a particularly thorny problem that stakeholders may think is easy to resolve – I’ll use the Staples “that was EASY button” to lighten the mood.
Thanks again!
Best,
Gina
Gina, great post! I have never thought about a social BEFORE the project starts. I always think of fun stuff/ice breakers at the kick-off and such, but before you come out of the gate is genius!
I don’t think this really qualifies as team building (I think you captured it) but when I know the team is stressed, if it is going to be a difficult meeting, etc I try to lighten the mood and bring them back that place of trust/relationship with a short video to make them laugh. I make sure the agenda allows for a 5-10 minute diversion of watching the clip and the chatter it may cause.