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


ECM Upgrade – Do it Yourself or Turn to the Experts?

July 31, 2009

Content/Document Management (“ECM”) systems are built upon software platforms that are continuously innovating and improving features and performance.  The vast majority of organizations using ECM systems subscribe to Annual Software Assurance so they can continuously receive updated or upgraded software as it is released by the software publisher. 

For example, Oracle® and Kofax® are software publishers of two of the frequently implemented ECM solutions among the many that are supported by ImageSource to provide solutions for clients.  These two major software vendors  have traditionally been expected to publish major upgrades approximately every 18 to 24 months. 

Users of ECM software understand that it is critical to maintain currency with regard to the versions of mission critical software applications they are running.  By upgrading to new releases, you enhance your ECM system with new features and functionality and maintain your investment.  You also stay on the most current version so that you always acquire the benefits of having the fully up to date software throughout the life of your system.

The question frequently asked by user organizations is whether or not to implement major upgrades using internal resources, or turn to an expert and trained vendor to work with them to get the tasks completed.  With each new release, the new software version solves additional business challenges and offers new functionality. 

Some vendor and integrators (ImageSource included) offer an Upgrade Consultation Program.   Using this approach is ideal for customers who are currently using an older version of the software applications, have received or are about to receive their update/upgrade, and are interested staying current and moving their system to the latest product release.  This professional services program is normally designed to accurately identify all of the technical and functional considerations that need to be taken into account prior to and during an upgrade. 

Major reasons to consider the involvement of your ECM vendor or integrator as a business partner when you are faced with a major upgrade can include factors where the experienced vendor or integrator:

  • provides technical resources that may not be available internally, or only available at the sacrifice of other planned internal projects
  • has specific training with regard to the version upgrade being implemented – they know the most efficient way to complete the required tasks
  • has deep software product knowledge and prior experience implementing the upgrade at other clients
  • has dedicated staff whose primary job description and every day experience is working with the software and all aspects of installation, planning, and other important factors.  User organizations do not usually have staff that spends significant time and an intense level of focus on the intracies of the ECM system software.
  • frequently, as a part of the upgrade project, organizations take advantage of new features to implement improved processes and applications – or just make the effort to enhance the system with new productive solutions when additional ECM training within the organization is going to be scheduled anyway

The recommended program should follow a formal Project Methodology developed through specific knowledge and experience.  It should provide the user organization with the analysis, process, a defined Project Plan and a firm cost to move forward with the assistance resources needed for a major upgrade project.  This analysis and planning is critical in order to minimize potential complications and allow a smooth and successful upgrade with minimal if any reflection on the productive use of your system.

User Organization Benefits of an Upgrade Consultation

  • Increase return on the initial investment in the ECM system by implementing additional functionality
  • Benefit from the expertise of a knowledgeable and trained Project Team who utilize best practices
  • Gain a detailed understanding of the project requirements and cost justification of an upgrade
  • Understand system requirements to ensure success
  • Understand the opportunity for organizational benefits leading to improved operations
  • Identify major considerations upfront and proactively determine ways to avoid risks
  • Define the Training Program that will optimize the new upgrade features and benefits

Primary Tasks in an Upgrade Consultation

  • Current system audit and assessment
  • On-site analysis and interviews
  • Current system snapshot and baseline metrics
  • Create upgrade execution plan
  • Review upgrade execution plan with customer

Project Plan Developed For an Upgrade Project

  • Report on the opportunities, benefits, and functionality that will result from the upgrade
  • Architecture analysis — a detailed analysis to review the current hardware and network architectures and then identify any recommendations for improved performance with the upgrade
  • Upgrade Project Schedule and execution plan (procedures, activities, roles, prerequisites)
  • Firm – Fixed Cost based on disclosed considerations and staying with the Project Plan
  • A Project Plan developed in conjunction with, and presented to, key stakeholders (IT, application owners, executive management, etc.)

On average, an Upgrade Consultation Program should be able to be completed in seven to fifteen days – depending upon the complexity of the installation and the amount of customization that has been included with system design.   If you are attending NEXUS 2009, make sure to discuss your approach to your next major upgrade project.

Neil W. Lindsey, Project Manager / Business Analyst
ImageSource, Inc.
www.imagesourceinc.com

Share on LinkedIn   Share on Twitter


Follow

Get every new post delivered to your Inbox.