Performance management has a reputation problem. For most employees, it means the annual review — a bureaucratic ritual that feels disconnected from their day-to-day work and rarely changes anything. For most new managers, it means an uncomfortable conversation they feel underprepared for. Done well, performance management is neither of those things. It is an ongoing system that makes expectations clear, keeps people developing and ensures that feedback is specific, fair and timely enough to actually be useful.
The framing that changes everything
The most important shift in how you think about performance management is this: it is not a judgement system, it is a development system. Its purpose is not to classify people but to help them do their best work and grow in their capability over time. When managers operate from that frame, the conversations change, the frequency changes and the outcomes change. Teams managed with a development mindset perform better and stay longer than those managed primarily through evaluation and consequence.
Everything in this article flows from that framing. Clear expectations exist not to catch people out but to give them the clarity they need to succeed. Feedback exists not to document problems but to help people improve in real time. Metrics exist not to reduce people to numbers but to ground conversations in evidence rather than impressions. Keep this in mind as you build your approach.
Principle one Set expectations with enough specificity to be useful
One of the most common and most avoidable causes of underperformance is ambiguity about what success looks like. If a team member is unclear on what they are supposed to deliver, how it will be measured and by when, they cannot reliably meet your expectations — and you cannot fairly hold them to account for missing them.
The SMART framework — Specific, Measurable, Achievable, Relevant, Time-bound — is a useful discipline here. The test is simple: after you have set an expectation, could someone with no prior context look at it and know exactly what they need to do and how they will know when they have done it? If not, it needs more specificity.
Beyond individual goals, make sure your team understands the broader context: why their work matters, how it connects to team and organisational objectives, and what good looks like qualitatively as well as quantitatively. People who understand the purpose of their work make better decisions about how to do it.
At the start of each quarter, spend 20 minutes with each team member reviewing their goals. Ask them to describe in their own words what success looks like for each one. Gaps between their description and yours surface immediately — and are much easier to address before work has started than after it has finished.
Principle two Make feedback continuous, not periodic
The annual performance review is a poor vehicle for feedback. By the time it arrives, the behaviour it addresses is months old, the context has shifted and the person receiving it has limited ability to change what has already happened. Feedback that changes behaviour is specific, timely and delivered close enough to the event that the person can connect it to what they actually did.
This does not require elaborate systems. It requires the habit of noticing when someone does something well or something that needs to change — and saying so promptly, specifically and constructively. “The way you handled that client question in today’s meeting was excellent — you stayed calm, you were clear and you found a solution without escalating” is more useful than “good work this week.” “I noticed the report went out without the executive summary we’d agreed on — can we talk about what happened?” is more useful than waiting until the next review to mention a pattern.
Schedule a brief one-to-one with each team member at least every two weeks. Keep them to 30 minutes and structure them consistently: how is the work going, what is getting in the way, what is one thing I can do to help you? These conversations, sustained over months, create the kind of ongoing dialogue that makes formal reviews a summary of things already discussed rather than a series of surprises.
Performance management is covered in depth in the LeadWise Emerging Leaders Program — alongside feedback, coaching and team development, with practical exercises applied directly with your real team.
Explore the program — €299Principle three Ground assessments in evidence, not impressions
Bias is one of the most significant risks in performance management. We are all influenced by factors that should have nothing to do with performance: how much we like someone, how visible their work is, how confidently they present themselves, whether they remind us of ourselves. These biases operate largely unconsciously, which is what makes them so persistent and so difficult to correct through good intentions alone.
The most reliable counterweight is objective evidence. When you base your assessments on specific, documented examples of behaviour and output rather than general impressions, you reduce the space for bias to operate. For each team member, track concrete examples of what they have done — projects delivered, problems solved, contributions made — alongside specific instances where standards were not met. Your assessment at review time then reflects a genuine record rather than a retrospective impression shaped by recency and affinity.
Keep a running note for each team member — a simple document or note — where you record specific examples of strong performance and areas for development as they occur. A two-sentence entry after something significant happens takes 90 seconds. Without this habit, you will find at review time that you can only clearly recall the last few weeks, which is almost never representative of the whole period.
Principle four Document consistently and for the right reasons
Documentation in performance management has two purposes. The practical purpose is that it makes your assessments more accurate, more defensible and more useful — both to the person being managed and to you. The protective purpose is that if a performance situation escalates, thorough documentation is what ensures the process is fair and legally sound.
New managers sometimes resist documentation because it feels bureaucratic or surveillance-like. The reframe is useful: documentation is what allows you to be specific and accurate in your feedback, what protects your team members from being assessed on vague impressions rather than real evidence, and what ensures continuity if circumstances change. It is a tool for fairness, not a tool for prosecution.
After every significant performance conversation — a formal review, a feedback discussion, an agreement on next steps — send a brief written summary. Not a formal document: a short email. “Following our conversation today, I wanted to confirm what we agreed: [x, y, z] with a check-in on [date].” This closes the loop, creates a shared record and means both parties are working from the same understanding of what was said.
Principle five Orient performance conversations toward the future
The most common failure mode in formal performance reviews is spending the majority of the conversation on the past — rating and discussing what has already happened — and very little time on what comes next. This gets the emphasis backwards. The past cannot be changed; the future can. A performance conversation that is primarily backward-looking is less useful to the person receiving it than one that spends equal or greater time on where they are going and how they will get there.
This means building development goals into your performance conversations as a matter of course, not as an afterthought. What does this person want to work on in the next quarter? What skills are they developing? What opportunities can you create or connect them to? These questions shift the conversation from evaluation to investment — and that shift in frame changes how the conversation is experienced by both of you.
Structure your formal performance reviews in three roughly equal parts: reflection on the period that has passed, honest assessment of where performance stands now, and forward-looking development planning. Most managers front-load the first part and rush the third. Protecting time for the development discussion — putting it in the agenda as a named item rather than hoping you get to it — ensures it actually happens.
The bottom line
Fair and effective performance management is not a system you implement once — it is a set of habits you build over time. Clear expectations, frequent feedback, evidence-based assessment, consistent documentation and a development orientation are not complex in concept. They are difficult in practice because they require consistency, self-awareness and the willingness to have honest conversations regularly rather than occasionally.
The new managers who build these habits early — before they feel urgent, before a performance situation forces the issue — are those whose teams perform best and who find the formal review conversations least stressful. The investment is front-loaded and the return compounds.