When You Disagree with Your Performance Review: Making Overlooked Work Visible

How reading tools work

Listen reads the article aloud. Speed read shows phrases in sequence at your chosen pace. Language practice compares available translations. Save keeps a bookmark in this browser; find it in the player’s bookmarks. Play this article as Breakout turns its own words into bricks for you to knock out.

Share this article

You are described as “the person who made the videos,” even though the real work was redesigning how people learn their jobs. You are told to “show more initiative,” but it is unclear what you are supposed to do differently. Frustration with a performance review can come from more than the rating itself. The same assessment may also shape your next assignment and your opportunities to grow.

Start by asking why you received that assessment and what evidence the evaluator has. Rather than trying to make someone understand your entire range of abilities, it is often more productive to clarify three things: what they observed, what work they may have missed, and what you could do next that would lead them to revise their judgment.

This article uses “low-resolution assessment” to describe a picture of someone that becomes fixed despite being based on limited observation. It is not a research diagnosis or a measure of intelligence. The examples of workplaces, job changes, and products below are hypothetical illustrations. They do not establish the abilities of any particular employee or prove that a particular company treated someone unfairly.

1. Reviews hurt because today's rating can affect tomorrow's opportunities

Other people cannot know everything that went into your thinking. You know how you reached a decision; your manager may have seen only a report or part of the finished work. You observe the work from different positions and have different amounts of time available.

A review carries weight because the people assessing you also have authority over the allocation of work. Their judgments can influence your assignments, discretion, development opportunities, promotion prospects, pay, and the work you get to try next. Some systems involve several evaluators and calibration meetings, so one person does not necessarily decide everything. Even so, an initial impression can remain influential if it becomes the starting point for later decisions and is not properly reconsidered.

Suppose an assessment says, “Can produce procedure manuals, but is not yet ready to lead planning.” If you genuinely lack planning experience, you need training and opportunities to practice on a small scale. But you may already have been defining problems and comparing options, while the evaluator saw only the finished manual. Those two situations call for different responses.

Do not settle the question solely on the feeling that you deserve a higher rating. Separate work that has not been observed from capabilities that still need to be developed. That is the starting point.

2. Explain the work behind the video or procedure manual

Producing a training video involves several kinds of work. Beyond filming and editing, someone has to decide what to teach, gather examples of exceptions, determine what can be standardized, and break down steps that people are likely to misunderstand.

Suppose you created videos and procedure manuals in a workplace where new-hire training varied by trainer. “Produced three videos” tells the reader how many items you delivered, but not what you were trying to solve. The following sequence makes your decisions visible as well:

  • Problem: Trainers explained the steps in different orders and gave different instructions about whom to contact when something went wrong
  • Investigation: You interviewed trainers and compared existing materials to identify the differences
  • Decision: You standardized the routine steps and kept equipment-specific conditions in a separate document
  • Implementation: You put the common steps into videos and documented exceptions and checks in a procedure manual
  • Follow-through: You recorded where users became confused and what questions they asked the trainers
  • Next steps: You planned to check the effects of using the materials and decide who would update them and how often

The number of videos here is hypothetical. You cannot claim a percentage reduction in questions or a certain number of training hours saved unless you measured those results. Record production, actual use, and demonstrated improvement as separate things.

There is also no need to assume that analysis is valuable while production is low-value work. Implementation, maintenance, and coordination require expertise too. The point is to explain the decisions and responsibilities that the finished product does not reveal, not to rank different kinds of work.

3. Do not assume that everyone else has missed the point

When a review overlooks your work, it can be tempting to think you are the only person who understands what really matters. But that would mean judging others on limited information too.

Structural analysis is only one kind of ability. Other strengths include keeping operations running, spotting risks through experience, reconciling stakeholders' interests, and reducing information to an amount the listener can use. Someone who speaks briefly in meetings has not necessarily thought less deeply. Conversely, a long, complex explanation does not guarantee an accurate judgment.

The research concept of integrative complexity distinguishes between “differentiation,” or recognizing different perspectives, and “integration,” or relating them to one another.[3][4] For example, separating an employee's learning habits from a workplace environment that discourages questions, then considering how the two interact, can help explain this distinction.

Reading this article does not establish that you have high integrative complexity. Nor can research on how groups process information be used directly as proof of an individual's exceptional ability. In practice, the question is not just whether someone identified several perspectives. It is whether they checked the evidence, discarded unnecessary hypotheses, and reached a useful judgment.

4. Do not explain a resignation solely through the employee's attitude

Looking at a departure makes it easier to see what connecting different perspectives involves. Suppose someone joins with prior work experience, struggles to learn the required procedures, and asks to move to another department. If they have not been taking notes, their learning approach deserves attention. But the presence or absence of notes alone does not establish ability or motivation. Check whether they were using a method that allowed them to learn and reliably carry out the necessary tasks.

An employee may need to change their behavior while the workplace also has conditions it could improve. Separate the areas to investigate.

The employee's actions and expectations

Did they seek clarification about what they did not understand? Did they use the available materials? Did they understand how they were expected to learn? Was there a mismatch between the work described before they joined and the actual job? Ask separately about what they did and why they did it.

Relationships with managers and colleagues

Were they reprimanded for asking questions, or made to feel that checking something was a nuisance? Did they know whom to approach? Did requests for help lead to specific support? Examine actual exchanges rather than diagnosing “low psychological safety” from an impression alone.

Conditions for learning the work

Were roles and expectations clear? Was the necessary information accessible? Was there support for onboarding people hired with prior experience? Was time set aside for questions and practice? Consider whether understaffing or workload left both trainers and learners without enough capacity.

Other cases and aggregate data

Have similar problems occurred elsewhere? Are departures within a defined period after joining concentrated in particular departments or under particular managers? If you examine transfer requests or leaves of absence, distinguish them from resignations and use consistent time periods and clearly defined group sizes. Take care not to identify individuals through small-group statistics. Similar cases alone do not establish that a particular manager caused the problem.

Management's explanation and the next improvement

Does management receive information beyond descriptions of the employee's attitude? Has it considered whether someone coming from outside may have noticed a problem in established practices? Did the findings change how the next job was explained during recruitment, how people were assigned, or how they were trained? Check whether each case ends with “it was the individual's problem” while the same situation keeps recurring.

This approach is not about automatically defending someone who left or blaming their manager. It is about identifying both support the individual needs and conditions the company can change.

5. Show how you connected and tested ideas, not how many you listed

Listing terms such as “onboarding,” “engagement,” and “organizational learning” does not tell anyone what to improve. Knowing many concepts is different from producing a diagnosis that can be used.

Looking only at outward behavior might lead to “they did not learn what they needed to know.” Examining relationships might reveal that requests for clarification were met with harsh rejection. Looking at the environment might show that procedures differed depending on who explained them. Aggregate information might reveal that other people who joined around the same time also took longer to learn. From there, you might propose a clear contact for questions, common procedures, and protected practice time.

This is an illustration, not a promise that investigation will reveal those causes. It might instead show that the employee's learning method was the main problem. Revise hypotheses when the evidence contradicts them, and leave unresolved questions open.

For a performance review, “Compared three possible explanations, ruled one out through further interviews, and tested small improvements addressing the remaining two” is easier to verify than “Conducted a deep analysis of the organization.” Three is only an illustrative number; use the number that matches the actual work.

These abilities involve experience, interest, learning, and a habit of testing ideas. There is no need to use a personality type such as INTP, or the fact that you keep thinking about work outside working hours, as proof of ability. Spending longer thinking is not the same as producing better results or supporting your health. You do not have to surrender your rest to demonstrate your value in a review.

6. Simplifying information on a review form serves a purpose

A performance review form is not meant to preserve a complete account of someone's abilities. Information has to be narrowed down so it can be read in limited time, shared between evaluators, and used to agree on behavioral goals and development plans.

Translating “Connected information about individuals, systems, and day-to-day work to analyze a training problem” into observable actions is reasonable: “Gathered information from stakeholders,” “Organized the issues,” “Compared possible improvements,” and “Incorporated the findings into the procedure manual.”[1]

Problems arise when too little is observed before the information is condensed, there is no opportunity to explain decisions, or the wording remains unchanged despite contrary evidence. Research reviews on performance management also examine how evaluators' cognitive processes and context affect ratings.[1] A rating should therefore not be treated uncritically as a direct reading of ability itself.

At the same time, an imperfect review does not make every criticism invalid. If it identifies specific problems, such as failing to communicate deadlines, explain matters to another department, or complete a handover, address those separately from gaps in observation.

7. Distinguish development from repeated rewriting

The usefulness of a review conversation can be judged by what changes in the work afterward, not just whether the document looks finished. Look for the following cycle:

  1. Observe specific work and situations
  2. Ask what information the employee had and why they made their decisions
  3. Compare the evaluator's understanding with the employee's explanation
  4. Agree on the behavior to improve and the evidence to examine
  5. Provide the assignments, discretion, time, and support needed
  6. Check what happened and update the next assessment

If phrases such as “initiative,” “role awareness,” and “working proactively with others” are repeatedly rewritten but assignments and support stay the same, it is worth asking whether the process is helping development. Rewriting can also clarify goals and make records consistent, so the number of revisions alone does not establish that the exercise is pointless.

Ask: “What behavior should this change in wording lead to?” “Will there be an opportunity to carry out that behavior?” “When will we review it, and on what evidence?” Research on the effectiveness of performance management also highlights the importance of distinguishing the components of a system from the outcomes used to judge it.[7] The six steps above are a practical way to make a review conversation more concrete, not a universally effective formula guaranteed by research.

If someone changes departments, continued involvement from their previous manager is not automatically good or bad. Clarify who will observe what, which period of work they will assess, and how information will be shared with the new manager.

8. If you have not shown the work, is it inevitable that it goes unrecognized?

Evaluators cannot accurately assess work they do not know about. Employees therefore have a role in communicating what they do and what they achieve. But “just speak up” does not resolve every situation.

An explanation may turn into a discussion of your character. Proposing an idea may bring more work without the authority to carry it out. Long meetings may consume time without moving decisions forward. Repeated experiences like these can make sharing information burdensome. Silence cannot be explained solely by personality or motivation; it also involves expectations about the consequences of speaking and the workplace context.[2]

Still, it would be a mistake to assume that every reason for remaining silent is sound. Prioritization, insufficient explanation, discomfort with a task, and unclear routes for asking questions are all possibilities. Both the evaluator and the employee need to establish what must be shared and what is getting in the way.

Where it is safe to speak, you can start with one decision and its evidence rather than disclosing everything about yourself. For example: “I did not standardize this step because the equipment conditions differ. Here is the comparison I made.” You do not need to disclose confidential information, what colleagues told you in confidence, or health information. If you are concerned about a hostile response or adverse consequences, first identify a route where you can seek advice, such as an available internal support channel.

9. Can the number of times someone speaks stand in for their contribution?

Not speaking in meetings, rarely consulting a manager, and not volunteering for high-profile assignments are easy to observe. That makes them tempting indicators of initiative. They do not, on their own, explain why someone behaved that way.

The person may be addressing the problem through another route. The meeting's purpose may be unclear. They may be prioritizing an important deadline, avoiding additional responsibility without authority, or limiting requests for clarification because of previous responses. It is also possible that they are neglecting necessary coordination.

Instead of counting contributions to a meeting, check whether the work's needs were met. Did stakeholders receive the information they needed to decide? Were concerns shared before it was too late? Could someone else take over the work? This is not an argument for automatically rating quieter people more highly.

Research on workplace reputations examines how perceptions of people become shared and how those perceptions relate to outcomes.[8] Agreement among several evaluators is important information, but it does not by itself guarantee accuracy. They may be passing on a common impression, or they may have independently observed similar, specific examples. Check the basis for the agreement.

10. Bring disputed feedback back to behavior and support

In a review conversation, clarifying the evidence behind a judgment is usually more productive than criticizing the evaluator's abilities. The following are examples of how to ask. Adapt them to your workplace relationships and to what feels safe.

If you are told, “You lack initiative,” ask, “Which assignment and which situation led you to that view? What action was expected at that point?” Once the situation is clear, compare the information you had with what you actually did.

If you are told, “Pay more attention to the people around you,” ask, “Who needs what information, and when do they need it?” Turn the answer into a feasible action: “On the next assignment, I will confirm the assumptions with the relevant departments at the start and consult them when a change requires a decision.”

If you are told, “You lack planning experience,” break it down: “Is the gap in defining the problem, comparing options, coordinating with stakeholders, or reviewing the results?” Then discuss which parts of a small assignment you could take on, who would approve decisions, and how much time would be available.

The conditions that make feedback useful vary with its content and the situation in which it is received.[6] These questions cannot guarantee a higher rating. The aim is not a promise of a favorable review, but a shared understanding of what actions could lead to a different judgment.

11. Create a one-page record of your contribution

You do not need to explain every part of a complex thought process. Choose one representative assignment and organize the following on roughly one page. You can use it in a review conversation or when reflecting on your work experience.

  • Problem: What happened, who was affected, and how?
  • Your responsibilities: What were you responsible for, and what did others handle?
  • Facts examined: Which documents, observations, and interviews did you use? What remained unknown?
  • Decisions: Which options did you compare, and why did you choose some and reject others?
  • Implementation: What did you create, which procedures did you change, and how did you coordinate with others?
  • Results: What outcomes have been verified, and which effects have not yet been measured?
  • Learning: What differed from your expectations, and what would you change next time?
  • Next opportunity: What further responsibility would you like to try, and what support would you need?

If you automated a reporting process with VBA, you can record more than the fact that you wrote a macro. Explain how you dealt with inconsistent inputs and how responsibility for exceptions and maintenance was assigned. If you measured processing time, include the conditions and period of measurement. Do not claim a team's results as your individual achievement or add unverified effects to the record.

This document is not a definitive statement of your abilities. It is a record to update as evidence grows. It can preserve decisions omitted from the company's form, but a record taken outside the company should not simply reproduce internal documents or customer information. Even material you believe you have anonymized can identify someone, so check what may be disclosed and what your organization's rules permit.

12. Separate feeling underused from proving your abilities

Feeling that you could do more can help you examine the gap between your current job and the work you want. That feeling alone does not establish that you are already fully equipped for the next role.

A research review on overqualification and underused capabilities brings together findings on their relationships with work attitudes, intentions to leave, behavior, and careers.[5] It does not prove that everyone dissatisfied with a review is highly capable, or that a transfer will necessarily solve the problem.

Suppose someone with experience in procurement, Excel automation, standardization, and training design wants to move into digital transformation or product work. That experience can be a strength. But employers will still need to establish how much responsibility the person has actually had for defining customer requirements, setting priorities, working with developers, implementing systems, and being accountable for metrics or budgets.

Experience is also not the only possible reason for a hiring rejection. Role requirements, competing candidates, the number of openings, and how experience was presented may all matter. The outcome alone does not reveal the cause. Rather than concluding that no employer understands you, or that you have no value, identify the evidence you still need and the experience you could gain next, as far as the available information allows.

13. Make a small proposal for the experience you want next

Explaining your assessment differently does not, by itself, add to the work you have actually done. It can help to define a small part of the role you want next and agree on what you would need to demonstrate.

For a training-improvement project, for example, you could propose more than continuing to produce videos: “I would like to identify the problems users face, compare two possible improvements, test one, and report the results.” Two is an illustrative number. The number of options and the scale of comparison should fit the project.

Include the scope, deadline, decisions you can make, decisions requiring approval, people who will support you, and priorities relative to your regular work. Agreeing on what you would learn if the result is disappointing can also help avoid a plan that depends on promising success.

Not every company has the assignments or capacity you hope for. If even a small opportunity is unavailable, find out whether the obstacle is the department's situation, a constraint in the system, or a specific capability gap. That information can help you compare another internal role with options such as changing employers. You can work on correcting the current assessment while also considering a different environment.

14. Wanting to earn independently can be about widening the routes to evaluation

Dissatisfaction with workplace reviews may prompt interest in a side business, an independent project, or self-employment. If it feels as though one person's opinion dominates how your value is judged, it is understandable to want feedback from customers, users, or readers instead.

Creating a product can give you more say over the problem you address, the abilities you combine, the price you charge, and the time you invest. Revenue, continued use, inquiries, referrals, and search traffic may provide information different from an internal review. But traffic and revenue are separate measures, as are purchases and continued use.

These are considerations for choosing how to work, not a general recommendation to become self-employed. Income can fluctuate. Selling and maintaining an offering take work. Contract terms and dependence on customer-acquisition channels also matter. Relying on a single customer or platform can narrow the routes through which you are evaluated in a different way.

Leaving a company does not automatically give you control over how you use your abilities. Use small trials to examine actual demand and workload, while considering the effects on your livelihood and checking your employer's rules on outside work and confidentiality.

15. The market will not understand complex abilities in their entirety either

Customers usually want to know how their problem will change, rather than how deeply the provider has thought about it. The starting questions are practical: Which task becomes easier? How much effort could this save? What could it prevent? Can I use it immediately? How does it differ from other approaches?

If you wanted to turn process-analysis skills into a product, for instance, you could describe the offering in concrete terms:

  • A tool that helps create instructions for Excel workflows
  • A template that organizes what needs checking during a handover
  • Materials that use public information to support company research and interview preparation
  • A tool that helps structure training videos
  • A checklist for identifying waiting time and bottlenecks in a process
  • A tool that helps applicants review and improve their own application documents

These are illustrative product ideas, not recommendations with verified demand or profitability. The application-document example is about helping applicants improve their own writing. It is not a recommendation to automate decisions about whom to hire.

Selling still requires presenting information briefly and clearly. A useful product will not be used if it does not reach the people who need it. Even if it reaches them, price, trust, effort required to use it, competition, and timing may affect their choice. Keep the reasons a product did not sell separate from a judgment about your overall ability.

Treat a short product description as one way of offering something, then improve it in response to feedback. That helps distinguish clear communication from restricting all your potential to one role. Even in self-employment, though, customer expectations and past work can lock someone into a specialty. Freedom is not guaranteed.

16. Decide how much time to spend responding to a review

Trying to resolve every disagreement can lead to an endless cycle of explanations and revisions. Decide what you want the effort to achieve. Correcting a factual error, clarifying the next action, securing an opportunity to gain experience, and completing a required form call for different investments of time.

On the company's form, give a concise account of verifiable facts, actions, outcomes, and next steps. Keep a fuller account of your decisions in a separate record that respects confidentiality and organizational rules. Instead of making complete understanding of you the sole goal, choose the facts that need correcting and a practical next step.

After the conversation, keep a short record of the agreed actions, the company's support, the review date, and unresolved points. It can serve as a reference next time. Do not record something as agreed if it was not. If there is a process for challenging an assessment, check its steps and deadlines. Specific procedures and rights vary by organization and location.

If you are considering a transfer or a job change, separate what is worth addressing in the current workplace from what you need to prepare for the next environment. More explanation is not always the best choice if it crowds out rest or your main work.

17. What evaluators can reconsider

Evaluators also need to recognize the limits of what they have seen. Distinguish “I have not observed this” from “this person cannot do it.” At the same time, do not accept the employee's account without question. Compare finished work, records of decisions, and specific examples from the people involved.

When commenting on behavior, identify the situation, what was expected, and what actually happened. Look beyond prominent contributions in meetings or polished documents. Depending on the person's responsibilities, examine prevention work, handovers, coordination across departments, and maintenance too. The aim is not to rate every less-visible activity highly, but to assess necessary work and contributions that can be verified.

If improvement is required, check whether the person has the authority and opportunities needed to act. Asking for initiative while allowing no small decisions, or demanding planning experience while assigning only execution tasks, creates contradictions that individual effort alone cannot resolve. Addressing support after the review and setting a time to reconsider the judgment creates room for development beyond completing the paperwork.[1][7]

18. Conclusion: Connect the review to evidence and opportunity, not a ceiling on ability

When you disagree with a performance review, you do not need to settle, all at once, whether you are exceptionally capable or the evaluator has failed to understand you. Separate what was observed, what was not, and which capabilities still lack evidence from practical experience.

Start with one representative assignment. Describe the problem, your decisions, implementation, results, and your own responsibilities. Bring abstract feedback back to specific situations and actions. Clarify the opportunity and support needed to test an improvement, along with when it will be reviewed. If something remains unchanged after you have explained it sufficiently, that can inform your consideration of other internal roles or external options.

A review form, a résumé, and a product description each select information for a particular purpose. None of them defines the full extent of your abilities. At the same time, the potential you believe you have is not the same as a demonstrated track record. Treat a limited assessment as a judgment that can be revised, and build experience that can be examined next. That is a practical way to expand your future options.

References (8)

The following sources provide background on the concepts and the limits of the research. The hypothetical workplace examples and suggested wording for review conversations are this article's explanations and proposals. They are not findings in which the cited papers diagnosed a particular workplace.

  1. Pulakos, E. D., Mueller-Hanson, R., & Arad, S. (2019). The Evolution of Performance Management: Searching for Value. Annual Review of Organizational Psychology and Organizational Behavior, 6, 249–271. https://www.annualreviews.org/content/journals/10.1146/annurev-orgpsych-012218-015009
  2. Morrison, E. W. (2023). Employee Voice and Silence: Taking Stock a Decade Later. Annual Review of Organizational Psychology and Organizational Behavior, 10, 79–107. https://www.annualreviews.org/content/journals/10.1146/annurev-orgpsych-120920-054654
  3. Molina, I., et al. (2023). Current research trends on cognition, integrative complexity, and decision-making: a systematic literature review using activity theory and neuroscience. Frontiers in Psychology, 14, 1156696. https://pmc.ncbi.nlm.nih.gov/articles/PMC10546895/
  4. Brodbeck, F. C., Kugler, K. G., Fischer, J. A., Heinze, J., & Fischer, D. (2021; online 2020). Group-level integrative complexity: Enhancing differentiation and integration in group decision-making. Group Processes & Intergroup Relations, 24(1), 125–144. https://journals.sagepub.com/doi/abs/10.1177/1368430219892698
  5. Erdogan, B., & Bauer, T. N. (2021). Overqualification at Work: A Review and Synthesis of the Literature. Annual Review of Organizational Psychology and Organizational Behavior, 8, 259–283. https://www.annualreviews.org/content/journals/10.1146/annurev-orgpsych-012420-055831
  6. Cioca, I., & Gifford, J. (2022). Performance feedback: an evidence review. Practice summary and recommendations. London: Chartered Institute of Personnel and Development (CIPD). https://www.cipd.org/globalassets/media/knowledge/knowledge-hub/evidence-reviews/performance-feedback-evidence-review_tcm18-111378.pdf
  7. Schleicher, D. J., Baumann, H. M., Sullivan, D. W., & Yim, J. (2019). Evaluating the Effectiveness of Performance Management: A 30-Year Integrative Conceptual Review. Journal of Applied Psychology, 104(7), 851–887. https://www.apa.org/pubs/journals/features/apl-apl0000368.pdf
  8. Connelly, B. S., & McAbee, S. T. (2024). Reputations at Work: Origins and Outcomes of Shared Person Perceptions. Annual Review of Organizational Psychology and Organizational Behavior, 11, 251–278. https://www.annualreviews.org/content/journals/10.1146/annurev-orgpsych-110721-022320

AdBooks on this topic

This article contains affiliate links (ads). About advertising As an Amazon Associate I earn from qualifying purchases.

If this article helped you, you can support the site. Support

Read this today

Each one answers a question readers of this article tend to ask next.

Browse all articles

Find other articles

All articles

Mendoi-chan

Who runs this site

Mendoi-chan

She turns friction at work and in everyday life into clear structure and practical next steps.

Latest articles

  1. 1Why Are Company Events and Work Drinking Parties So Exhausting? The "Fake Private Time" That's Really Unpaid Work
  2. 2"Should be able to" is not operational capability