Managing Project Teams – Guidelines for Giving and Receiving Feedback

October 6, 2009

Guidelines for Constructive Criticism/Feedback

In the course of managing our projects there comes a time in our personal interactions where the project manager will have to provide feedback and may even have to say something negative to the person they are dealing with. There may also be the case where they have to say something negative to say to you. I prefer to call it constructive criticism/feedback rather than negative but many people refer to it as negative. You may find that many people become embarrassed, distressed, and even angered by this criticism/feedback. Too often relationships can become strained and work can even be disrupted. However, there are some people who are able to transform these moments into opportunities for success. They are able to take this information and enhance their work skills, relationships and continue to advance, develop and grow professionally.

The Guidelines:

1.       Acknowledge the need for criticism/feedback

It is the main way to know what things need to improve. It is vital to the success of the project team and its members. Giving and receiving criticism/feedback should become the “culture” of the project team.

It is very important that the team should agree that giving and receiving feedback is an acceptable part of how you will work together and continuously improve as a team.

 2.       Provide both positive and negative criticism/feedback

“Catch” people doing things right as well as when something goes wrong. Reward and remember to tell people when they are doing things right. You want that to continue. People will be more receptive to your negative comments if they have also been accustomed to your positive comments. It shows that you are truly trying to work towards improvement.

 3.       Understand the context

Before proving feedback be sure you review the actions and decisions that led up to the event that you will be providing feedback on. Understand the circumstances completely.

 4.       Know when to give feedback

Determine when the moment is right. Are you ready to give the criticism? Is the person ready to hear it?

Do not give feedback when:

  • You don’t know a lot about the circumstances
  • You don’t care about the person or will not be around long enough to follow up on the aftermath of your feedback
  • The feedback, either positive or negative, is about something the person does not have the power to change
  • Your purpose is not really improvement
  • The time , place, or circumstances are inappropriate, i.e. you are angry or others are around
5.       Know how to give feedback

Use a tool like:

When you [do this], I feel [this way], because [of such]. What I would like you to consider is [doing X], because I think it will accomplish [Y]. What do you think?

Example:

When you are late for meetings, I get angry because I think it is wasting the time of other team members. I would like you to consider finding a way to better planning your schedule so you can get to meetings on time. This way our meetings can be more productive and we are not wasting the time of others. What do you think?

  • Be descriptive - give specific examples
  • Don’t use labels – avoid labels like unprofessional, irresponsible, and immature. Describe the specific behavior and drop the label.
  • Don’t exaggerate - To say “You are always late for deadlines” may not entirely accurate.
  • Don’t be judgmental - Don’t use words like “good”, “better”, “bad” or “should”. You don’t want to appear to be in the role of a parent.
  • Speak for yourself – Don’t refer to absent or other people. Don’t use comments like “a lot of people here don’t like it when you….”
  • Talk first about yourself, not the other person - People become defensive with that usage. Use phrases like “I feel annoyed when you are late for meetings” rather than “You are frequently late for meetings”.
  • Phrase the issue as a statement not a question – Use statements like “I feel annoyed when you are late to meetings” rather than “when are you going to stop being late for meetings”. Most people become defensive and angry with a question. The use of an “I” statement implies “I think we have an issue we must resolve together.”
  • Restrict your feedback to things you know for certain – Speak of what you have seen and heard not what you feel and want. Don’t present opinions as facts.
  • Help people hear and accept your compliments when giving positive feedback – Some people tend to feel awkward about positive feedback. Reinforce positive feedback even when the person says “it was no big deal”.

 6.       Know how to receive feedback

There may be times when you will receive feedback from someone who does not know the guidelines. Help your critic provide the feedback by asking “What did I say or do to dissatisfy you?” then take it from there.

When reacting to feedback:

  • Breathe – Taking full deep breaths forces you to relax and allows the brain to stay alert.
  • Listen carefully – don’t interrupt. Don’t discourage the criticism.
  • Ask questions for clarity – ask for specific examples if you don’t get them.
  • Acknowledge the feedback – repeat back what you heard in your own words so the person knows you understood.
  • Acknowledge valid points – agree with what is true and what is possible. That does not necessarily mean you agree to change the behavior.
  • Sort out what you have heard – you may need to take some time to sort out what you have heard before responding. Check with others if needed. However, don’t use this as an excuse to avoid the feedback.
  • Don’t be defensive – take the feedback for just what it is feedback. Do not try to defend or justify yourself on each point. Again, just listen.

Al Senzamici, PMP
Program Manager
ImageSource, Inc.

Share on Twitter


What Type of Search is Right for You?

July 8, 2009

For many functions in the organization the full text “Google” like search capability found in most document management systems may be useful.  For others, it’s not sufficient in providing the business value.  Here’s some situations that may help determine what is right for you.

A business professor once said “There are three core functions to any process… 1. Procurement of Materials 2. Conversion of Materials and 3. Distribution of those Materials.  All other functions only support these three”.  In translation, these three things can map to any function found in business for any department (Sales, HR, Information Technology etc.)  It seems that when analyzing any business process, this old adage always comes back and discussing search in the enterprise is no exception.

When looking at search it’s helpful to see both sides of these functions for document management.  Documents either “drive the process” as a core function, or documents are ”driven by the process” as in a supporting role.  The differences are not all that hard to see.  Document that drive the process are directly related to the three functions above 1. Procurement 2. Conversion and 3. Distribution.  Documents that are driven by the process may be everything else.

Vouchers, Invoices and Checks are all documents that drive Purchasing.  Service Orders and Proof of Delivery are documents that drive Operations.  Purchase Orders and Service Contracts drive sales. 

On the other side, Marketing Literature  is driven by Marketing.  Brochures are driven by Sales.  The company Calendar is driven by HR and Inventory Reports are driven by Operations.  These documents support the functions of their departments.

A less technical way to look at this dichotomy is ”gotta have that document now” and “gee, this looks like what I’m looking for”.  When designing a search architecture, this is one of the basic questions you can ask yourself.

Documents that drive the business process tend to require a discrete index field search.  This is because the user is typically looking for the one document they need, and they need it quick.  A Sales Order for a customer service representative or an Invoice for a purchasing manager.  These documents also typically already have a structured meta-data component already designed for them before the document management system is in place.  A Sales Order Number field is always generated for Sales Orders and an Invoice Number Field always has an Invoice number.  This is true before or after a document management system exists.

Documents that are driven by the process are less structured in nature.  Marketing Literature, Progress Reports and the Employee Vacation schedule to name a few.  The user is typically looking for some information that could be in one, or many of these documents.  Could an employee figure out if Memorial Day is a company holiday by finding the wrong documents to their search?  Like last years vacation schedule?  Probably so.  If this is the case, a full text content search may prove successful.

Documents that “drive the process” answer questions to a search that only that one document can satisfy.  What items were billed for Invoice # 123456?  What date was Employee #78910 hired?  Who signed for Proof of Delivery #34567?  In these cases, a discrete index field search is required.

 

John Moffitt

Systems Engineer

ImageSource, Inc.

http://www.nexusecm.com/index.htm

www.imagesourceinc.com

www.ilinxcapture.com 

Share on LinkedIn   Share on Twitter


Follow

Get every new post delivered to your Inbox.