Skip to main content

The time of year for Performance Reviews - Dos and Don’ts

I am worried to open my browser on the evaluations website, to find out how many reviews I need to fill in. I have blocked out Friday for this, while I work from home, but we all know how planning days free of ‘work’ often works. Everywhere around me I see people going through the official adjectives list, googling some of them, figuring out what the best term is to define someone who does really well 90pct of the way but then is never able to finish. I appreciate the commitment to do it, but inevitably we all complain. 

Very timely, I put myself on a management course on providing feedback and supporting career development this week. Although more focused on the actual discussion, for me it was important to go over a few techniques and I am certain it will set us all in the mindset to write better reviews. 

What is a valuable review? 
  • It has clear feedback - no dancing around the issue or vague compliments. How? ‘You did a great job well done!’ vs ‘You have done a great job to establish great relationships in the cross functional project you have just done and people’s feedback is that you are very good to work with and they value your methodical approach to solve problems’. It allows the person to know what and when they have done well (or badly), what were the key attributes valued and that there are actually comments regarding this. If you can pull out a quote even better. For next year, this will focus the mind of the employee in what they can do more of.
  • It has examples - this is especially important for development feedback, where we try and contextualize the area of negative feedback. It is not just ‘your tone can be aggressive some times’, but rather ‘when you say things like xyz that may be perceived negatively in some environments’ or ‘in meeting A you made a few arguments like xx and that could be interpreted as B’.
  • It has impact - for good or bad feedback, providing the person with the impact to the person. This is easy to do for positive feedback ‘job well done, project complete, happy client’, but much more challenging to explain when it is a subjective piece of feedback. In our training, the practical case was about an analyst that was seen as overstepping the mark on her views about how a project should be run, which the project manager was not pleased about. I was an F for failure at my mock practice but learn something valuable. If you explain impact,  it makes the person understand why it matters. When some of us went through the facts of what she was doing wrong (with some dancing around the issue), she was frustrated that doing a good job for the project was deemed wrong. Only when we explained the impact on her career of coming across as arrogant and non collaborative did she then realized how that was not at all her original intention. It was powerful.
  • It has questions - this applies naturally to the actual discussion rather than the write up but also means we keep an open mind. Questions allow the person to process the information just received and, in an ideal scenario come up with a few alternative solutions to address it, especially the development feedback piece. For someone to be invested you need them to not only understand why the feedback exist, how it impacts the business but also what can be done to address it. It also allows them ways to express their doubts on potential area that are less clear. Don't make it a monologue.
  • It has goals - the key thing about reviews is that they need to be focused on the future. When problems exist, you need to help the employee come up with potential solutions. Don’t feel like you have to have all the answers. There is plenty of research to show that we learn better if we conclude things ourselves. In fact, Harvard teaches all their case method on that basis. It also reduces dependency, people are not exclusively relying on you to solve the problems, they slowly develop autonomy to do it themselves. They need to be able to work through problems and identify courses of action. But goals can also be positive - what are areas you want to focus on, what skills do you need to develop, where will you press your advantage. By setting goals people have a clear sense of direction which can be key to allow prioritization at busy times. 
  • It has silence - weird right? But that has been a key learning I have had through multiple training sessions this year. Silence is an essential feature of a difficult conversation. It gives people room to process, address, think. It may be the case that what you are saying is not new news, but it may be. And it can be a hit that people need space to work on. 

But why do we do performance reviews and why do they matter so much
Are they not just a tick the box exercise we need to do? Arguably, people that you work with should know what you think of them. The end of year process should be just a structuring of all the feedback people have to allow better consumption and planning. However it is many times the case that this is the first time people get feedback. 
Ideally, reviews are not a once a year thing. If that is the case and you are keeping open conversations with your team, then the above becomes much more natural. There are steps in between that can really develop a culture of feedback that goes way beyond the HR process. Recently, I asked the team to do a Q3 review of their top 3 achievements and goals for the next quarter. They were surprised (my bad, first time I asked), but also keen. They all prepared well thought achievements with examples, making my job much easier when I get to write their reviews. At the same time, they all had forward looking goals and some of them gave me really good space to address development points. It was a win-win in a non formal 360 environment and I am committed to do it every quarter. They also understand the importance of it, and hopefully will grow to be good managers too. Good feedback is timely feedback. 

You may think reviews are a large corporate kind of thing but I am ready to challenge that. 
Reviews are important in any work environment where you value professional and personal development and where you want to allow space for feedback. A few years back, I implemented them in my small charity in Portugal. Unusual and unexpected, they turned out to be valuable for me as manager but I believe also for them as employees as it forces them to stop and think out of the frenzy of the day to day. We also do our annual Christmas lunch around a review of the year by checking what we can do better and setting goals for us individually for the year. That is part of the culture I want to create. OK, I admit that I am late in kicking the off this year, but they are featuring on my October list! 

A final point I wanted to make concerns women. 
Also timely, this week’s episode of Women at Work, the HBR podcast, addresses the topic of feedback to women and how different it is to men’s. The title reads ‘We deserve more than Attagirl’ and it is undoubtedly controversial but I highly recommend it. My view on it would require a whole new post, which may come at some point, but I was struck by the ‘positive sexism’ where we are protecting women by giving them positive feedback or very little development feedback. How can they grow and develop then? Attagirl helps no one. Men or women. 


Comments

Popular posts from this blog

Strategy Making with a Fact Based Approach without Facts

One of my first tasks as I came back from maternity leave was to conduct a strategic review of one of our businesses, one where we have consistently under-performed.  The premise is simple, we should have everything to succeed in this business, what is wrong then! We stopped buying that the market was slow a long time ago, as competitors deals kept being thrown in or face. We knew we had a structural problem but when we asked the team for a business plan, we got a pipeline back. Given I was reading the #leanstartup while doing this, I decided to apply a fact based approach, whereby I started from basic assumptions to question the team. After a first round focused only on market size and product details, the claim continued to be lack of transparency on the numbers. The discussion jump started to a business mix debate, as it became enlightening that people had very opposed views about why we should be pursuing different parts of the business. Diagnostic 1: no-one agrees with each

The trouble with data

I a bit of a data freak. I like my data, preferably correct. I feel like James Bond as he approaches the bar. How do you like your data? "Accurate, not Cut". That would be me. I don't take it re-worked, re-cut or in extracts. I take it raw so I know what it is, what it means, what it tells me, what flaws it has. The problem with data is that people more often than not do not understand what they are looking at. You asked for a piece of analysis and someone sends you a chart and you take it as it is. You believe you have done the right question and the person has interpreted what you were after the write way, extracted what you intended. A whole bunch of assumptions which my time working inside an organization (other than in the client facing side of the business) has taught me are mostly flawed. When we start looking at a problem, most likely we don't really know what we are after. We feel that there is some data that illustrates our story but really

Due Diligence: The Art of 100 Questions (to start with...)

It is one of those stories that the old days come back to haunt you. I started my career as a Banker and am no stranger to due diligence lists. I have been both on the receiving end and in the creative end of those. I have created data rooms to respond, massive excel spreadsheets, and have trolled through data rooms to find more information. I have mention this before, I am always data hungry. For those paying attention you might ask - but aren't you done with your banking years and off due diligence lists? Well, not really. First, I was never entirely out of due diligence. In fact, I apply due diligence as a modus operandi for challenging the status quo. I just start looking at the numbers, and then ask question #1, which inevitably leads to #2 and is inevitably linked to #3. It does not take a form of an excel spreadsheet and I don't get answers back via data rooms, but the concept is constant - a truly inquisitive nature with the purpose of understand and evalua