Maya's manager hit the same problem many strong performers face in a review cycle. Maya had done strong work, but that work still had to survive summary, comparison, and limited room for explanation. In one common setup, that is where What Is a Merit Increase? becomes practical. It is a decision filtered through how clearly your performance can be described when others are weighing your case against nearby peers.
Maya worked in a role where much of her value came from messy cross-functional problem solving. She improved a fragile process, resolved repeated handoff confusion, and became the person people pulled in when decisions were stuck. By the time compensation discussions arrived, everyone around her agreed she was dependable. The harder part was proving the level and pattern of that impact in a room where not everyone had seen the work directly.
What a merit increase usually means in practice
A merit increase is a pay increase tied to assessed performance. In many workplaces, it is distinct from a promotion. You can receive one without changing level, and you can also have strong performance that feels underrepresented if the supporting evidence is vague.
That distinction matters because the review conversation often asks slightly different questions than you expect. The room may be comparing how convincingly each case shows sustained results, growing ownership, and impact that others can recognize.
For an individual contributor, this changes the job. You are leaving behind enough proof that someone else can explain the work accurately later.
The case before the calibration discussion
Maya entered the cycle with a familiar problem. Her manager knew she was strong, but most of the record lived in memory, chat threads, and scattered comments from partner teams. Her self-review named several projects, yet many bullets described effort more clearly than outcome.
A few examples looked like this:
- Coordinated stakeholders across a high-visibility process change
- Helped unblock a delayed decision
- Improved team operations and documentation
None of those statements were false. They were just too thin for comparison. In a calibration-style discussion, a thin statement loses to a specific one almost every time.
A stronger version of the same work looked more like this:
- Reworked a recurring handoff process across three partner functions, clarified ownership gaps, and reduced repeat clarification requests from downstream teams
- Pulled conflicting inputs into one decision memo that allowed leaders to choose a direction in the same review window
- Standardized an error-prone workflow so routine questions stopped returning to the same small group of people
The work did not change. The visibility of the work changed.
What happened in the room
Picture the review discussion moving quickly. Managers are summarizing multiple people, trying to distinguish solid performers from those showing broader or more consistent impact. Some cases are easy to repeat because the evidence is crisp. Others sound promising but blurry.
When Maya's manager first described her, the support was positive but general. Reliable. Strong partner. Helpful across teams. Those signals were good, but they sounded similar to what several other managers were already saying about their own people.
The discussion improved when her manager shifted from traits to examples. Instead of saying Maya was great at cross-functional work, he described the specific process breakdown she repaired, the decision she helped force to conclusion, and the repeated pattern of people seeking her out when ambiguity was high.
That shift matters because calibration conversations usually reward contrast. Another person in the room needs to be able to hear your case once and repeat it later without losing the point.
A compensation discussion gets clearer when someone outside your day-to-day work can explain your impact without guessing.
Why the first version of Maya's case was weak
The weak version had three problems.
First, it leaned on effort words. Coordinated, helped, improved, supported. Those verbs describe activity, but they do not always show what changed.
Second, it hid ownership inside team language. If a bullet does not say what you personally drove, the room may assume shared contribution.
Third, it lacked durable proof. There were positive impressions, but not enough preserved comments, outcomes, or before-and-after detail to give the case weight.
This is where many individual contributors get stuck. Their work is valuable, but the record is not specific enough to survive compression.
What strengthened the case
Maya and her manager rebuilt the record around three kinds of evidence.
- Repeated patterns, not one-off praise. They looked for examples showing the same strengths across more than one situation.
- Outcome language, not just activity language. Each example had to show what changed after Maya's work.
- Outside signals. Notes from partner teams and follow-up comments helped confirm that the impact was visible beyond her own team.
That combination gave the discussion something more solid than opinion. It showed that Maya did not just participate in important work. She made difficult work move.
A tool like ImpactLogr is useful here because it preserves those small signals before they vanish. A short note attached to an accomplishment, saved when the work happened, is much easier to trust than a reconstructed claim written months later.
What you can take from this if you are aiming for stronger review outcomes
This example does not prove that better notes always lead to a larger increase. Compensation decisions depend on company policy, budget, and the shape of the cycle. But it does show where documentation changes the quality of your case.
If you want your work to travel well into review discussions, capture these details as you go:
- the problem you stepped into
- the decision, fix, or system change you drove
- what improved afterward
- who noticed and how they described it
- whether the same pattern showed up again in later work
Those details help with more than compensation. They also make promotion cases stronger, because both conversations depend on the same underlying question. Can another person understand your impact clearly and repeat it accurately?
The practical answer: what a merit increase is
The formal answer is simple. A merit increase is a performance-based pay increase. The useful answer is broader. It is one output of a review process that depends on how well your work has been translated into evidence.
You cannot control every part of that process. You can control whether your accomplishments are documented well enough to help your manager make the case. If you want an easier way to capture that proof while the work is still fresh, create an ImpactLogr account for your next review cycle.