The Annual Performance Review – is it Time for a Change?

All managers (Project Managers, department heads, Executives) in most organizations have a responsibility to provide feedback to their staff members.  Over the years I have found that many people view this as an agonizing task and some completely ignore performing this key process.  I recently read a great post by Lindsay Scott on developing Project Managers and employees, (http://www.arraspeople.co.uk/camel-blog/projectmanagement/five-questions-about-project-management-development/) in which she summarizes a book she read by Kimberly Janson “Demystifying Talent Management: Unleash People’s Potential to Deliver Superior Results”.  Her post made me think about how organizations today (and projects) don’t actually take time to give effective feedback to staff and employees.

No matter what you call it: performance appraisal, review, feedback, development, etc., the only way to help people improve and perform better is to engage them in effective feedback and conversations about their performance, objectives and career.

There are many books and articles written on developing employees and performance feedback techniques.  But what I see happening is that companies and organizations are changing the whole concept of giving feedback with many abandoning the traditional “annual performance review.”  The key term replacing “ranking and rating” is feedback.  And the timeliness of the feedback is key to the process.

I personally prefer the concept of conversations that are held throughout the year, during which you discuss performance and give feedback.  Many of you will say that your HR department wants to have these “conversations” documented in the personnel folder.  And I am sure the standard forms they give you are not for holding “conversations” and providing effective feedback.  So I thought I would share a format that I have used for many years both on projects and with employees to provide meaningful and actionable feedback on performance.

My feedback format has 2 main parts and deal with both positive and negative feedback.

  1. Section 1: Feedback from the Employee. The questions and discussion here should be tailored to the organization, job, or project.  I have some general questions that can be used as a starting point:
    • How are you doing? (Do they feel like they are making progress, are they frustrated, do they want more challenges, etc.)
    • Describe any likes or dislikes with your current assignment/project/etc.
    • Do you have what you need to get your job done effectively? (This can be tools, knowledge, skills, etc.)
    • What are your goals for the next [project, quarter, job, etc.]?
  2. Section 2: Giving Feedback to the Employee. I like to give feedback in three sections or groups – starting with the most positive and moving to the least positive:
    • Job skills and behaviors that the employee has demonstrated and he/she should keep doing!
    • Job skills and behaviors that the employee has not demonstrated or done consistently – you would like to see more of these.
    • Job skills and behaviors that the employee has demonstrated and should stop doing because they impede performance or trigger negative consequences.

 

While you have to give specifics to back these up, I find it is much easier to categorize performance into these 3 groups.  You are basically telling the person that they have both strengths and weaknesses.  By being honest and positive with the conversation, you should be able to steer the individual to more productive behaviors and ultimately increase their value to themselves and the organization.

I hope this post helps you to get a handle on what can be the best or worst process in your management toolkit.  Do you have any tips on giving performance feedback?  Leave a comment.

For those interested in digging deeper, here are few articles that I think you might find useful:

 

3 Responses to “The Annual Performance Review – is it Time for a Change?”

  1. paul Says:

    Great insight, improvement relies significantly on receiving meaningful feedback. Of considerable more debate is not whether feedback can bring about improvement, but what makes it “meaningful”. As observed by researcher John Hattie, “there is as much ineffective feedback as effective feedback”. In general, the point of feedback is to cause things to happen. While it is true that feedback causes things to happen, it is important to remember that some of those things are bad. Therefore, it is important to consider how to deliver feedback and what makes it meaningful.
    .

  2. Ken Ashe Says:

    Personally, I think too many people what to give critical feedback until the review process. Ideally feedback (both good and bad) should be give in real-time. This enables people to improve performance quickly if needed


Leave a comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.

The Lazy Project Manager's Blog

The Home of Productive Laziness Thoughts

ProjectManagement.com

Thoughts, experience, tips and tricks on issues affecting managers and project management

A Girl's Guide to Project Management

Project Management musings for one and all

LeadingAnswers: Leadership and Agile Project Management Blog

Thoughts, experience, tips and tricks on issues affecting managers and project management

Project Management Hut

Thoughts, experience, tips and tricks on issues affecting managers and project management

Herding Cats

Thoughts, experience, tips and tricks on issues affecting managers and project management

beyondcenter

Pushing the Edges Out ...

projectxpert

Just another WordPress.com site