Image of computer

Don’t use email to give criticism

This is a guest post by Sarah Clare.

As a project manager, there is sure to come a time when you have to address poor performance or substandard work. We all make mistakes, and we can all find ways to improve our work. When you are a project manager, it is your responsibility to make sure that you help your team to learn from those mistakes and to find ways to improve the quality of their work.

However, delivering constructive criticism can be difficult. You may not know how to distinguish it from plain criticism, or you may not know how to deliver it in a way that your team members do not receive negatively. Learning how to give criticism to inspire positive change is a skill that must be learned.

Here are a few tips for how you can better provide constructive criticism to your team:

Deliver it in person

E-mail might be the best way to communicate with busy professionals, but it’s not always the best way to communicate sensitive information. There is no tone in e-mail, and something that you intend to say with empathy and understanding may be read flat or even with malicious intent. It is important to have these conversations in person so that your tone of voice and body language can help to soften the message and to inspire a sense of team work to accomplish a mutual goal.

Focus on discrete, actionable changes

Criticism can very easily turn into a personal attack or a rambling rant that encompasses everything that you’re unhappy about with the employee. It is important to be very deliberate by thinking about what you intend to say before you approach the employee and to have a goal in mind for improvement. You can then focus on small, actionable changes that the employee can make to solve the problem, rather than providing vague feedback asking for improvement with no ideas about how to make it happen.

Focus on one or two actions at a time so that you do not overwhelm the employee. Once those are made, if additional changes are still needed, you can revisit the conversation to evaluate progress and to suggest continued improvement.

Be liberal with praise

Criticism is always hard to hear, no matter how well you deliver it. You can make it a little easier to bear by being liberal with your praise as well. Don’t wait until you have something negative to say to offer praise. Make it a habit to praise your team members when you see them doing something great or when they deliver good work. When you have to provide constructive criticism, you can build on that praise by highlighting recent accomplishments or aspects of the project that have been handled particularly well.

Encourage problem solving

You can engage the employee in figuring out how to solve the problem together in order to promote learning and real improvement. If you tell the employee what you would like to see change, it may not always be effective. You may only train the employee to do what you are asking in order to avoid repercussions – but the employee may not understand why the change is necessary or valuable and, therefore, won’t change the underlying behavior that caused the problem in the first place.

Instead, encourage problem solving together. Instead of providing a solution, talk with the employee about the problem and ask for feedback about what can be done to improve the situation. The process will encourage learning that will facilitate long-term change.

Provide a model

If you lecture an employee about being tardy but then don’t roll into the office until 10am every day, you aren’t going to be very effective in inspiring change. It is important to provide a positive role model for the kind of behavior that you want to see.

In addition to providing your own role model, you can support employees in making positive changes by providing mentorship opportunities, support, or ongoing training.

It’s never easy to hear criticism, and it can be even harder to try to give it in a constructive way. Developing thoughtful strategies for delivering criticism can help ensure that your message is heard so that you and your team can work together to create positive change. These strategies can help you accomplish those goals.

How do you handle giving constructive criticism to your team? Share your tips for success in the comments!

About the Author: Sarah Clare is a writer and oversees the site projectmanagementsoftware.com, where she has recently been researching time tracking software. In her spare time, Sarah enjoys cooking and scrapbooking.

What do you think? Leave a comment!

Project Stakeholder ManagementI’ve recently read Project Stakeholder Management by Pernille Eskerod and Anna Lund Jepsen (part of Gower’s Fundamentals of Project Management series). It talks about why stakeholders contribute to projects.

You might think that it’s obvious. After all, your project sponsor is probably the one who wanted this project to happen in the first place, and he or she has a vested interest in making it a success. But aside from the sponsor, all those other stakeholders don’t have to play nicely. They make an active choice to either help out, or hinder your project.

Eskerod and Jepsen say that before stakeholders make a commitment to a project they weigh up:

  • The expected consequences, both in terms of benefits and costs
  • What others will think about their involvement
  • Obstacles for making a contribution.

They might not work through this list and make conscious decisions, of course. It can be a very illogical process that they may not even be aware of. But as a result of those thought processes, however chaotic and unconscious, they will decide whether or not to contribute and if they will contribute, how much they will contribute.

Assessing the consequences

Project stakeholders obviously cannot know exactly how the project will work out, because it hasn’t happened yet. They also don’t have all the information to be able to make an informed decision about the expected consequences of their involvement in the project, as they probably have less information about the project than you do. Instead, they will consider their perception of the consequences, and use that as a decision-making tool.

The consequences of their involvement could be positive or negative. There are both benefits to being involved, and costs. The benefits are things like:

  • Being involved with a high-status, high profile project
  • Increased exposure to senior leaders
  • Tangible outcomes for their department such as the project deliverables like new software
  • Being able to shape the direction of the project as an early adopter instead of just accepting the changes later when the pilot is complete – getting in on the ground
  • Getting more skills for themselves or their team members
  • Career progression for themselves or their team members.

Costs are the other side of the equation, things that they will have to ‘pay’ in order to take part in the project like:

  • Offering up resources in the form of people or services
  • Money from their budget to fund the project
  • The time commitment
  • The administrative overhead of taking part in a project
  • The potential for negative publicity or a negative impact on their career if the project goes badly.

A stakeholder will mentally run through all of these and end up with a judgement about what is in it for them. There are probably a host of other things that you can think of that may affect a stakeholder’s willingness to contribute to a project. If you can work out what is bothering any particular stakeholder, you can work with them to overcome these issues and get a more positive outcome from them.

Concerns about contributing

Some people may be very keen to contribute but find that something is holding them back, consciously or unconsciously. One of these things could be what other people will think.

Peer pressure is prevalent in office environments, and what other people think about their involvement in the project is bound to form part of the decision making process for stakeholders. You can help them make the ‘right’ decision by encouraging them to see their contribution in a positive light, as something that someone in their position would naturally or logically do – assuming, of course, that you do want them to contribute! Otherwise I suppose you could encourage them the other way.

Stakeholders also consider influences from their own environment, outside of the project, so you could lobby those around them so that they hear positive messages from their own communities. This could include talking to their boss or mentor, or providing other options for positive role models to show that their community would value their involvement with this project.

Can they contribute?

Another reason why people may be reluctant to spend time working with you on the project is that perhaps they don’t feel capable of contributing in the way that you require. They may not have the skills they need, or they may feel as if they don’t.

You can help by encouraging them and boosting their confidence. You can also help in practical ways, such as providing training. One of the reasons people don’t want to get involved with projects is that they perceive a significant overhead in administration or in project jargon – the mysteries of project management. If you are expecting them to use software you can point out how easy they are to use and even provide some training. Once people have a good grasp of what is required of them, they will be less reluctant to commit to the project.

Finally, they may need permission to contribute, so even if they are very keen, they may still be waiting for their line manager to give them the go ahead. If you suspect that this is what is holding them back, have a quiet word with them and then approach their manager and ask him or her to release your stakeholder for some work on the project. Your stakeholder may have had a gut feeling that permission would be refused, but if you don’t ask, you’ll never find out!

How have you encouraged stakeholders to contribute? Let us know in the comments.

Buy on Amazon.co.uk

Buy on Amazon.com

1 brilliant comment, add yours

Project Management for Musicians

Not sure if this cover image is supposed to be a keyboard or a mixing desk. Or some other music thing I don’t recognise.

I have a great giveaway for you today – one of the heaviest books I’ve ever had to ship out as a giveaway! It’s Project Management for Musicians: Recordings, Concerts, Tours, Studios & More by Jonathan Feist. Published in February by the publishing wing of Berklee College of Music, it’s a complete guide to getting your music projects organized, whether that’s recording, going on tour, launching your music business or a studio or creating music study materials for others.

I think it’s very interesting to see how project management is impacting all areas of life now – 15 years ago I doubt we would have had this book – but it’s certainly a sign that project management practices are infiltrating how business works.

To be in with a chance of winning, get in touch with the phrase ‘I beat the project management drum’ and I’ll put your name in the hat.

During the last giveaway (which was for newsletter subscribers only), a couple of people wrote in to say that they weren’t sure if I would post a book to them as they lived miles away – like New Zealand miles away. Rest assured that where you live doesn’t affect your chances of winning and Royal Mail will let me post books all over the world!

Standard giveaway terms apply. If you can’t wait to take your chances, you can buy a copy now on Amazon.

4 brilliant comments, add yours

Guillermo Solis

Guillermo Solis

This is a guest post by Guillermo Solis.

Managing successful meetings is not a new subject, but neither is a waste of time to refresh ourselves about how best to manage meetings. Below I have some suggestions to bear in mind before, during and after meetings, when we are in charge of the meeting. These are based on experience mostly in Mexico and Central America projects.

1. Before the meeting

Objective. Define what the meeting is for and what we are expecting as a result: an agreement, approval, a work plan, etc. The meeting should start with a brief welcome and then the definition of the subject itself; it’s a powerful argument to keep the focus!

Participants. Who must and should be in the meeting? That’s enough people. Depending on the matters to deal with, we should consider inviting at least one member of the areas or departments involved (stakeholders), so that person can communicate to the others about what was said and how could affect them.

Notice. If it is possible, schedule the meeting with several days of notice, so we can give time to participants to check their agendas. If you can, it’s worth asking for their availability informally before sending the invitation. It’s not a guarantee of course but the possibility of the participants being in the meeting will be greater, and also the possibility to re-schedule will be smaller.

Agenda. Delineate the topics or issues to address in your notebook or/and the presentation. Assign a specific time to each item (and plan to have a clock in the meeting room). Always consider time for a Q&A session, and you can use this slot to deal more easily with interruptions – park any topics that upset the flow of the agenda to the Q&A.

The plan B. What if the projector fails? The meeting time is reduced half an hour? Or you have a last minute guest? It’s important to have in mind what could impact the meeting or your presentation and be ready to go in a different direction if necessary.

Time of the meeting. We all know the best time for a meeting is before lunch. If you schedule it for later, people’s attention will be diminished, attendees will be more tired, stressed, etc.

Place. Choose a place or location where everybody can arrive on time in a comfortable way. Consider ways to get to the venue, lighting, noise levels, availability of a projector, phone, etc.

Material. It is essential to have the necessary material. Check for the presentation twice (share it with someone else to see if it’s clear and easy to follow).

2. During the meeting

Welcome and agenda. Start on time, define the objective and agenda, but don’t wait more than 5 minutes for anyone who is late (respect the time of the rest of the attendees).

Questions, comments and detours. It’s always valid to answer questions and comments but if the agenda is too tight you can politely mention the Q&A section at the end. Try to be flexible and remember that meetings are not a monologue. However, try to avoid important detours that might compel your meeting into unnecessary delays.

Humor. Being serious is a way to call for respect, but if we don’t break the ice, the meeting will become dark and eerie. Sometimes a smart joke makes it easier to digest a hard subject, a delicate matter or the complex contents of your presentation.

Length. If you can make your meeting fit into an hour or less, that’s great, but if it goes beyond that, start taking 5 or 10 minute breaks to avoid stress or desperation!

3. After the meeting

Meeting minutes/summary. Acknowledge the participation of all the attendees when sending the summary as this gives importance to the meeting and shows you respect the time of the participants. You can use a pre-defined format for minutes or send out a summary via email. The format must include any decisions, a list of the participants (those who attended and those who sent apologies) and might suggest a date for the next meeting if necessary.

Cost of the meeting (aggressive approach to lack of attention). If you experienced a lack of people turning up for the meeting (or the wrong people turning up), or a lack of action as a result of the meeting, you could use this aggressive strategy: estimate the cost of the meeting. If the required data is available and you are confident using it, then calculate the estimated cost of the meeting. Work it out based on the time the participants invested in it, and talk to your project sponsor about it. It’s an effective way to make a point (although a little bit aggressive): we’ve lost time and money with this meeting because no one paid attention.

Follow-up. The meeting does not end when everyone goes back to their job. If you have proper follow-up and the result of the meeting is productive, than we can say that we had a really effective meeting!

It’s hard to have 100% effective meetings all the time, but with practice these tips will help you to forge habits that allows you to have a high effectively (and credible) average when you have to chair a meeting.

About the author: Guillermo Solis has over 10 years of experience in the IT area, resulting from support areas, development and management. In recent years he has worked as a project and resources manager in Mexico and Central America.

1 brilliant comment, add yours

Infographic: 10 Things You Should Know About APMP

May 6, 2013
Read more

4 ways to proactively manage stakeholders

May 1, 2013

Stakeholder management is a hot topic at the moment, given that A Guide to the Project Management Body of Knowledge (PMBOK® Guide)—Fifth Edition now includes a tenth knowledge area on managing stakeholders. So Pernille Eskerod and Anna Lund Jepsen’s book, Project Stakeholder Management, is quite timely. In it, they argue that proactive stakeholder management is [...]

Read more

My Life Is A PMP® Ethics Question!

April 29, 2013

This is an article by Jeff Furman, PMP®, whom I met at a PMI Congress one year, and we’ve stayed in touch since. Jeff has been a firm supporter of Social Media for Project Managers and I’m delighted to showcase some of his work here. Q.  The sales rep for a software vendor and his [...]

Read more

Carnival of Project Management #45

April 26, 2013

Welcome to the March/April 2013 edition of the Carnival of Project Management. It’s our 45th edition! Ben Aston presents How to run a great project kick-off meeting posted at The Digital Project Manager, saying, “All projects start somewhere. But how you start them can often dictate how the rest of the project or client relationship [...]

Read more

The Parent Project: Month 3

April 24, 2013

I did not expect to be the kind of parent that dressed my child in comedy outfits – in fact, before Jack was born I was adamant that I wouldn’t do that. Parents are embarrassing enough when you are 18 without having them bring out all the embarrassing photos of you as a child. But [...]

Read more

Talking about risk: interview with Wilhelm Kross (part 2)

April 22, 2013

Last week I spoke to risk expert Dr Wilhlem Kross about risk communication and the challenges facing project managers talking about risk. Here is the second part of that interview, in which Wilhelm and I talk about how project managers can best communicate about risk on their projects. Wilhelm, you talked about how sometimes people [...]

Read more