Performance management rarely fails at the review. By the time that conversation happens, doesn’t matter if it’s annual, biannual, or quarterly, the real damage is already done. Performance management failure is what happens when the processes designed to evaluate and develop employees (e.g. goal-setting, regular feedback, and review conversations) collapse long before the formal review takes place. The goals weren’t good enough, the conversations didn’t happen, and the review ends up carrying all that weight.
Why does performance management fail?
Most often, for two interconnected reasons: goals that are too vague, too safe, or too focused on activity rather than outcomes; and a breakdown in the honest, ongoing communication needed to make those goals meaningful. Neither can be fixed by just making a better review template on your HRIS.
The difference between a job responsibility and a performance goal
One of the most consistent problems in performance management is the confusion between job responsibility, which is what someone is paid to do, and a performance goal, which is what they should be actively working towards. These are not the same thing at all, but in many organisations, they’re treated as if they are.
What does a bad performance goal look like?
Speaking at a Mentorloop Industry Advisory Council session, Michael Werle, Director of HR Consulting Australia, put it plainly: managers frequently confuse activity with outcomes when setting objectives. A bad goal looks like completing monthly reports on time, attendance percentage goals for team meetings, or responding to a certain number of customer enquiries in a quarter. These are job responsibilities. These are the baseline expectations of the role, not performance objectives.
A better goal is specific, outcome-focused, and measurable: improving client retention from 82% to 87%, or reducing average response times from 48 hours to 24 hours. The difference isn’t about ambition level. It’s about whether the goal describes what someone does or what they achieve.
The scale of this problem is structural. Research from the Association for Talent Development found that while 90% of organisations expect employees to be involved in their own goal-setting, only 28% of those organisations actually train employees on how to set a good goal. That means most people are being asked to do something they’ve never properly been taught.
The fix starts before the goal-setting conversation itself. Give managers a simple test for every proposed goal: does this describe a responsibility or a result? If it’s something the employee is already expected to do as part of their role, it’s not a performance goal, it’s a job responsibility. Rewrite it toward a measurable outcome with a named baseline and a target. That discipline alone changes what gets discussed in the review, because now there’s something concrete to discuss.
|
Activity-based Job Responsibility |
Outcome-based Performance Goal |
|---|---|
| Completing monthly reports on time | Improving client retention from 82% to 87% by end of Q3 |
| Attending team meetings | Reducing average response time from 48 hours to 24 hours by mid-year |
| Responding to customer enquiries within the day | Increasing first-contact resolution rate from 60% to 75% by Q4 |
A job responsibility describes what someone does. A performance goal describes what they achieve.
Why do employees set safe goals and why do managers let them?
The goal-quality problem isn’t purely a skills issue. It’s also, as Michael Werle describes it, a social defence: goals used as cover rather than commitment. Employees learn quickly that easier goals mean higher ratings. Managers, often uncomfortable with the friction that comes from challenging someone’s self-assessed objectives, let it pass. Neither party is necessarily acting in bad faith, but both are optimising for the path of least resistance, and the result is a quiet collusion. Goals become a ritual rather than a tool.
Breaking this pattern requires managers to see the goal-setting stage as more than a formality. They need to be responsible for asking whether the goal is genuinely stretching, whether it’s within the employee’s control, whether it aligns with their level of seniority, and whether it’s something the organisation actually needs to happen. Building a short checklist around these questions and using it at sign-off as part of the standard process makes the challenge feel less like personal criticism and more like quality assurance. The conversation becomes easier when an expected part of a manager’s job.
Michael Werle cuts to the heart of why so many performance goals fail before the review even starts.
If you’ve ever approved a goal that felt more like a job description than a genuine objective, you’ll recognise this immediately.
The better question: “Were the goals worth achieving?”
Even when goals are technically well-formed (e.g. specific, measurable, time-bound), they can still be the wrong goals entirely. Michael points to a cultural shift that the most effective organisations are making: moving from asking “did they achieve their goal?” to starting with ”are these goals worth achieving?”
This reframe matters most at the senior level. Drawing on the work of organisational theorist Elliott Jaques, Michael notes that goals for a coordinator, a manager, and an executive should look fundamentally different both in scale and in the type of work they represent. A coordinator’s goals should be operational and shorter-horizon; a senior leader’s should be strategic and longer-range. Using the same goal template across every level is a structural mismatch that makes the whole system harder to take seriously.
The practical fix here is calibration of the content of goals and the questions asked when reviewing them. Building a step to ask ”are these goals the right ones?” into the formal review cycle as a standard question shifts the performance review from a compliance exercise to an actual evaluation.
How poor communication turns performance management into a paper exercise
When the review replaces conversations
Gallup research finds that only around one in four employees strongly agree that their manager provides meaningful feedback or that the feedback they receive actually helps them do better work. That’s a striking number, and it reflects something familiar to anyone who’s watched performance management up close: the formal review has quietly become the only conversation, rather than one touchpoint in an ongoing dialogue.
Michael describes a pattern most HR leaders will recognise: An employee puts genuine effort into their self-assessment by explaining what they’ve achieved, where they’ve struggled, where they want to grow. The manager logs in, reads it, types “agreed,” and closes the review. In that whole exercise, there would be no discussion, no challenge, and no developmental direction. The employee then walks away with no clearer sense of where they actually stand.
When managers can’t observe progress directly and most interaction happens asynchronously, it becomes easier to treat the system as the conversation rather than the structure built to support one.
The most direct solution is also the most straightforward: require a live discussion before a review can be marked complete. If your system allows sign-off without one, you’re enabling avoidance. This process change matters more than reminders.
Equally useful is reframing what the review conversation is supposed to accomplish. It needs to be framed as a progress checkpoint instead of a verdict. Gallup recommends calling these “progress reviews” rather than performance reviews precisely because the language shifts what both parties come prepared to discuss.
Have managers lost the skill or the will?
When performance management systems make it easy to sign off without a conversation, many managers do exactly that.
Michael Werle talks about how avoidance gets built into the process and whether managers have simply lost the skill of having the hard conversations face to face.
Why the evaluative relationship makes honest conversation structurally harder
There is a structural reason why communication breaks down between managers and direct reports, and no amount of manager training fully resolves it.
The manager-direct report relationship is asked to do two things at once: evaluate and develop. Those two functions exist in a tension that sits at the heart of any genuine performance culture, one that no process redesign alone can resolve. An employee who knows they’re being assessed is less likely to be candid about what they’re struggling with. A manager who may need to deliver a difficult performance outcome is less likely to invite that honesty. The relationship itself creates conditions for managed disclosure rather than genuine dialogue.
Recognising this distinction matters, because it changes what the solution looks like. Fixing the manager’s communication style only goes so far if the underlying structure of the relationship makes honest conversation costly for both sides. That’s where the design of the broader performance and development system needs to step in.
Why annual goal cycles set managers up to fail
Even with good goals and willing communicators, the annual goal cycle creates its own failure mode. By the time the formal review arrives, the goals themselves may no longer be relevant.
As businesses move, priorities shift. A goal set in January that was well-intentioned and strategically sound may be entirely disconnected from reality by July. If no one has checked in, employees will still be working towards irrelevant goals. Michael is direct on this: there’s no value in continuing to pursue a goal that’s no longer going to deliver an outcome, or that the employee has lost control over. Goals are point-in-time artefacts, and managing them as though they’re permanent is a recipe for wasted effort for everyone involved.
The solution is a mixed check-in cadence that does more than track progress against a fixed target. Here’s a model Michael is seeing some organisations adopt: a Q1 goal-setting conversation; a Q2 discussion focused on learning and role development rather than performance rating; a mid-year check-in to assess whether goals are still relevant and worth pursuing; and a Q4 formal review. Regular check-ins are also incredibly important so there’s always an opportunity to flag any developments or changes. Each conversation has a different purpose, which reduces the pressure on any single touchpoint to carry everything.
As for the format of those conversations, Michael suggests taking check-ins out of the office. Do them during a walking meeting, a coffee, somewhere that isn’t a desk and a screen. Moving the discussion away from the formal environment lowers the stakes and changes the tone. It becomes a conversation rather than a review moment, and that shift can make the difference between a manager who speaks honestly and one who defaults to the safe answer.
![[Webinar Kit] Mentoring for the 6 Stages of the Employee Lifecycle Learn how to make mentoring a core part of the employee experience and why it pays off at every stage.](https://no-cache.hubspot.com/cta/default/4058869/interactive-189627182868.png)
What mentoring adds that performance management structurally can't
Better goals, stronger cadence, and more capable managers will resolve a lot, but not the evaluate-and-develop tension of the manager-direct report relationship. It’s what makes honest conversation costly and while better process design helps, it doesn’t completely resolve this issue.
This is where mentoring is invaluable. A mentor sits outside the reporting line and carries none of the evaluative weight. SHRM explicitly recommends that performance management systems be designed to encourage employees to solicit career feedback from someone other than their direct manager. It characterises the mentoring relationship as “a nonthreatening venue in which to provide feedback,” where employees can test ideas, concerns, and developmental thinking without risk of retribution.
In practice, this means an employee can work through their goals honestly with a mentor before the formal review, without the stakes attached. They can say what they’re actually uncertain about, explore whether they’re working on the right things, and get genuine developmental feedback from someone who has no role in their performance rating. The whole point, and why it’s valuable, is that the mentor isn’t evaluating them.
It’s important to note that this isn’t about mentors stepping in for managers, or about introducing mentoring between direct reports. It’s about adding a parallel developmental channel that isn’t compromised by the same structural tension. Pairing that relationship with an individual development plan gives it practical structure and a shared reference point. This way, an employee’s goals, development priorities, and progress can sit outside the line of reporting and be worked through honestly with mentors who know how to make those conversations count.
Organisations that build mentoring into their culture more broadly find that something else follows too: regular goal reflection and honest developmental conversation become a shared organisational norm rather than a rare event. The practice of thinking about development outside the formal review cycle becomes familiar across the organisation, which raises the baseline for how those conversations happen everywhere.
Frequently asked questions about performance management
-
Why does performance management so often feel like a box-ticking exercise?
Because the process — goal-setting, feedback, and review — is frequently treated as an administrative cycle rather than a development tool. When goals aren't meaningfully set and conversations don't happen between reviews, the formal review becomes a formality. The box gets ticked because the substance was never there to begin with.
-
What's the difference between a job responsibility and a performance goal?
A job responsibility describes what someone is expected to do as part of their role: attending meetings, submitting reports, responding to customers. A performance goal describes what they should achieve or improve — a specific, measurable outcome with a baseline and a target. Confusing the two is one of the most common and most avoidable reasons performance management fails before it starts.
-
How often should managers check in with employees about their goals?
At minimum, a mid-year check-in to assess whether goals are still relevant — not just whether they're on track. A more effective approach mixes review types across the year: goal-setting in Q1, a learning and development conversation in Q2, a mid-year relevance review, and a formal performance review in Q4. Conversations in between are important too. Each has a distinct purpose, which reduces the pressure on any single touchpoint to do everything.
-
What does good performance goal-setting look like at different levels of seniority?
Goals should reflect the type of work appropriate to each level of seniority, not just the scale of it. Individual contributors should have shorter-horizon, operational goals tied to measurable outputs. Managers should have goals connected to team outcomes and process improvement. Senior leaders should have longer-range, strategic goals aligned with organisational direction. Using the same goal template across all levels is a structural mismatch.
-
How can mentoring support the performance management process?
Mentoring adds a non-evaluative developmental relationship that the manager-direct report structure can't provide. Because the mentor sits outside the reporting line and plays no role in performance assessment, employees can work through their goals honestly, explore what they're uncertain about, and get genuine developmental feedback without the stakes of evaluation attached. It complements the formal process rather than replacing it.
-
What should managers do when an employee's goals become irrelevant mid-year?
Change them. Goals are point-in-time artefacts — well-intentioned when set, but vulnerable to being overtaken by events. If a goal is no longer going to deliver an outcome, or if the employee no longer has meaningful control over it, continuing to track it is busywork. A mid-year check-in should explicitly ask: is this still the right goal? If not, reset it — and make sure the process allows for that without it feeling like a failure.
Ready to give your people the developmental conversations your performance management process alone can’t? Let’s chat! Book a demo with a mentoring program expert and see how Mentorloop can help you build a program that supports real goal clarity, honest feedback, and development that happens between the reviews.
