Continuous Performance Assessmentmanagement
Have you ever struggled evaluating the performance of your direct reports? Or have you been surprised in your performance evaluation meeting with your manager? In this post I'll explain a different approach and will give you some tips and guidelines to implement it yourself.
Is this 1-pager worth your time?
As managers, it is important to provide support and guidance in regards to performance so that people continue to improve and grow. And this should be happening regardless of the performance assessment cycle.
Let me start by trying to show you why I think this technique is for you, and also why Continuous Performance Assessment matters regardless of whether you are manager or a managee. This is for everyone.
How long do you spend on average preparing your performance notes?
Something between too long, and “please don’t ask me about that painful time of my life” → keep reading
How often do you discuss performance with your direct reports / manager?
Not often enough → keep reading
How do you track wins and misses?
I don't do it → keep reading
How do you know everyone in your team has the same understanding of the competency framework?
I don't know it, and just mentioning competency frameworks makes me feel goosebumps and a cold sweat on the back of my neck → keep reading
How confident are you that there will be no surprises when discussing the results of the performance evaluation with your direct report / manager?
Anything less than 100% → keep reading
I practice Continuous Performance Assessment with my team, and have been doing it for some time now. In this post I'll explain the benefits of this approach and will give you some tips and guidelines to implement it yourself.
Avoiding the big rush at the end
Being consistent at writing notes about performance is hard.
- It requires a lot of discipline.
- You need to know enough detail about the items you are capturing.
- It doesn't scale - In fact, it becomes exponentially harder as the number of direct reports grow.
Managers (me included) know this, and build mental barriers to avoid a process that is unpleasant to their eyes. As a result, it is often left to the very last minute, when there is no other choice but to sit down and write.
But what if this was part of your regular 121 conversations? You already have time booked for this.
Remind yourself of the benefits. At the end of the cycle you will have notes covering the whole period. This will help you remember details that you would have forgotten otherwise, so your notes will be much more thorough. And fairer. Recency bias will be less relevant, because you will have been capturing information more evenly.
Choosing a frequency
Should you update your notes every week? once a month? once a quarter? Only you know what works for you and your team.
Personally, every two weeks is the cadence I find more useful, which also maps to the frequency of my 121s. So if you can afford doing this every single 121, do it. If not, do it as frequently as you can. Seriously, this is important. Having a chat about performance should be as easy and comfortable as talking about the weather or asking about the weekend.
There are pre-requisites, of course. You'll need:
- Transparency about the process
It's a self-reinforcing cycle, you need transparency to generate trust, when you have trust and people see the benefit of having an open discussion about performance, there comes engagement. With engagement, there comes more feedback and proactivity, and more data. And with more data, there are even more reasons to be transparent and give clarity about how that data will be used.
Keep it simple. Use a table (or a nested list but I prefer a table). Define categories that are relevant to your environment, typically areas of your competency framework. Bias in favour of outcomes and impact, instead of actions. And use the same structure with everyone.
If you have an official structure for your performance assessment notes, you are half way there, use the same one. You don't want to reinvent the wheel and then have to spend time mapping between different formats. Equally, from the manager's perspective, you want to have meaningful discussion with other managers about the performance of your reports and their reports, and having a common framework makes it easier and more efficient.
Make sure competencies are fully understood by everyone in your team. Spend 121 time going through each competency and share examples of bad/good/great behaviours in each one. Consider having a refresher session every 6 months or when competencies get an update.
Don't forget to include misses. Discuss impact, foreseeability and response. It is paramount for your reports to understand what they should've done instead of what they did, and this will help them grow much faster. Also, it will give them the chance to turn the tables and come out stronger if you have these conversations early.
This is the absolute key. If you are the manager, after you prepared the table, explained the competency framework, got alignment and common understanding, and started the process with some notes of your own, there is one last thing for you to do.
That document is no longer yours. It's your report's. From this point on, most of the updates in the performance assessment will have to be done by them. It's no longer your performance assessment, it's a self-assessment now, with your input.
As a result, you will have frequent conversations about wins and misses. Performance will not be something to be evaluated at the end of the cycle, it will be a way to assess how I'm doing against my own career path in real time. And equally as important, It will become a framework to have meaningful discussions about what's next and how to get there.
If you want to try Continuous Performance Assessment:
- Avoid the big rush at the end by capturing performance on a regular basis.
- Choose a frequency that works for you and your team, but the more frequent the better.
- Use a structure that is compatible with your official performance evaluation notes.
- Avoid surprises at the end by making it a collaborative effort, and letting go.