Merit Conversation with Your Manager: What IT and Business Professionals Need to Know

Most IT professionals walk into a merit conversation with one number in their head and no plan for the room. The manager already has a number too – and that number was finalized weeks ago in a spreadsheet you never saw. This article shows you how to build a documented, data-backed case before that meeting, what to say when the offer lands on the table, and how to handle the answer when it is not what you expected.

What a Merit Conversation Actually Is – and What It Is Not

A merit conversation is a structured discussion between an employee and a manager about compensation tied directly to demonstrated performance. It is not the same as a general performance review, though many organizations run both in the same quarter. It is not a negotiation over your value as a human being. It is a business conversation about what the market pays for your skills and what your contribution has produced for the organization.

In most large IT organizations – especially in healthcare IT, financial services, and regulated industries – the merit budget is set at the company level before any individual manager touches it. Your manager typically receives a pool, often 3–5% of their team’s total base salary, and allocates it across the team. That pool does not grow because you asked nicely. It can, however, shift in your direction when you have shown clear impact and your manager has the documentation to justify the allocation to HR.

Knowing this changes how you approach the meeting. You are not convincing your manager to like you more. You are giving your manager the business case they need to advocate for you one level up.

Merit Conversation vs. Performance Review: Key Differences

These two conversations are often conflated. Treating them as the same meeting is one of the most common mistakes mid-level IT professionals make.

Tufts University’s HR guidance explicitly separates these two meetings – performance review first, merit communication afterward – because combining them typically causes the employee to disengage from the performance discussion the moment a number is mentioned. If your organization runs them together, you need to manage your own mental separation between the two parts of that conversation.

Building Your Case: The Documentation Framework

Vague assertions do not move budget. Your manager needs a document trail they can attach to an HR justification request. Here is what that trail looks like for an IT professional.

1. Quantified Deliverables

Every claim needs a number, a timeline, or a named project. “I improved the release process” is not a claim. “I reduced UAT cycle time from 14 days to 9 days on the Q2 enrollment platform release, which moved the go-live two weeks ahead of schedule” is a claim. If you work as a business analyst, document the number of requirements you elicited, the stakeholder sign-off rate, and any rework cycles you prevented through early validation.

2. Scope Expansion Since Your Last Review

If your responsibilities have grown, you need to name the delta explicitly. Compare your job description from 12 months ago against what you actually do today. If you are onboarding new team members, owning a domain you did not own before, or covering someone else’s gaps during a hiring freeze, that is scope expansion. Organizations routinely absorb headcount pressure by quietly expanding existing roles without adjusting compensation.

3. Market Benchmarks

Use Glassdoor, Levels.fyi (for technical roles), the Bureau of Labor Statistics Occupational Outlook Handbook, or industry-specific compensation surveys. For healthcare IT roles – HIPAA compliance analysts, EHR integration specialists, HL7 FHIR developers – the HIMSS Compensation Survey is one of the most credible benchmarks available. Pull data for your metro area, your role level, and your years of experience. Bring a range, not a single number.

4. Certifications and Skill Development

Any credential you earned during the review period is billable experience for your manager’s justification. SAFe certifications, BABOK-aligned training, AWS or Azure credentials, new testing tool proficiency – list them with the completion date and the direct application to your current work. If you earned a certification on your own time and dime, say that explicitly. It signals initiative and reduces the company’s training cost.

Real-World Scenario: Healthcare IT EHR Migration

The lesson here is not that documentation always produces an immediate result. It is that documentation creates a record your manager can use to advocate for you through channels that are not the merit conversation itself. Budget cycles are not the only compensation lever in an organization.

What to Actually Say in the Merit Conversation

Structure the conversation in three phases: anchor, evidence, ask. Do not combine them or skip one.

Anchor: Set the Frame Early

Open by connecting your contribution to a business outcome the organization cares about. For an Agile team working inside a SAFe release train, that might sound like: “I want to talk about my compensation in the context of what I delivered this PI cycle. The team shipped three features on time, and my test coverage work reduced regression defects by 30% compared to the previous PI.” You have established the frame before the number is mentioned.

Evidence: Present, Do Not Argue

Walk through your prepared summary: the quantified deliverables, scope expansion, and market data. Hand your manager a copy. Do not lecture. Present the evidence, pause, and let them respond. Most managers have not thought as carefully about your contribution as you have – the pause matters.

Ask: Name a Specific Number

Vague asks produce vague results. “I was hoping for something more substantial” invites sympathy but not action. “Based on market data for a mid-level QA analyst in this metro area and the scope I’m covering, I was expecting an increase closer to 6%” gives your manager a specific number to either approve, modify, or explain in concrete terms why it is not feasible. Research from Harvard Law’s Program on Negotiation confirms that naming a specific, well-researched number – rather than a range or vague language – produces meaningfully better outcomes in salary discussions.

Handling the Offer When It Comes In Low

Most merit conversations in mature IT organizations end with a number that was already decided. Your manager is communicating a decision, not opening an auction. That does not mean the conversation is over.

If the offer is below your target, ask two questions: what specifically would need to change for the increase to reach your target level, and when is the next realistic checkpoint to revisit this. Both questions are forward-looking. Neither of them is an argument. They convert the conversation from a closed announcement into a planning discussion, and they give you documented criteria to hold the organization to at the next review cycle.

Alternative compensation is also a legitimate topic when base salary is constrained. A professional development budget, an accelerated promotion timeline, additional PTO, remote work flexibility, or a mid-year check-in with a stated target are all negotiable in organizations where the merit band is hard-capped. If you work in a role where skills are in high demand – QA engineers with automation experience, or analysts who understand payer-provider data integration – you have more leverage on these items than most managers will volunteer.

The Merit Conversation as a Manager: What the Other Side Requires

If you are the manager in this conversation, the employee’s preparation should not surprise you. It should prompt you to show up equally prepared. You owe the person across the table a clear explanation of how the merit decision was made: the pool size, the performance criteria used for differentiation, and where they ranked within the team’s allocation – even if you cannot share exact numbers.

Avoiding specifics creates more disengagement than delivering a lower number with a clear rationale. Gartner’s HR research on compensation conversations consistently shows that perceived fairness in the process matters as much as the outcome itself. An employee who understands why they received 3% will perform better over the next 12 months than one who received 5% with no explanation of how it was determined.

Timing the Conversation Inside the Project Cycle

In Agile organizations running on SAFe or Scrum cadences, the merit conversation competes with PI planning, sprint retrospectives, and release deadlines. The worst time to request a compensation discussion is the week before a major release. The best time is during a planned 1:1 approximately six weeks before the organization’s compensation review period opens.

If your team follows an Agile or Scrum framework, use the natural visibility points in the delivery cycle to document your impact in real time. Sprint demos, program increment reviews, and retrospective outputs are all legitimate sources of evidence. They are also time-stamped records your manager can reference in an HR calibration session.

In healthcare IT specifically, project cycles often align with regulatory deadlines – CMS final rules, ICD-10 update cycles, HIPAA enforcement windows. If you delivered on one of those deadlines under pressure, that is not just a project milestone. It is a risk-mitigation outcome with a quantifiable dollar figure attached if a deadline had been missed.

Merit Conversation Timing Across Common IT Roles

Different roles carry different types of leverage. The nature of your contribution shapes how you frame the conversation.

If you work across the full software development life cycle, you can frame your contribution at multiple phases – requirements, development, testing, and delivery – which gives you more evidence surface area than someone in a single-phase role.

Edge Cases and Real Constraints

Not every merit conversation happens under ideal conditions. A few situations require a different approach.

Hiring freeze or budget lock. If the organization has announced a compensation freeze, bringing market data is still useful – not to force an exception, but to establish a documented baseline for when the freeze lifts. Get your manager to confirm in writing (email is sufficient) that your case has been noted and will be reviewed at the next opportunity. That confirmation matters.

Mid-year promotion without a title change. In many large IT organizations, scope expansion happens without a formal promotion cycle. If you are doing the work of a senior role without the title or pay, that discrepancy is your core argument. Frame it as a role alignment issue, not a performance issue. The BABOK v3 competency framework distinguishes between role levels based on demonstrated analytical complexity and stakeholder influence – if your actual work meets a higher competency tier, document it using that language.

New manager with no context on your history. This is common after reorgs, which happen frequently in healthcare IT following mergers, acquisitions, or CMS mandate cycles. If your manager has less than six months of direct observation, you need to provide more context than usual. A brief performance summary covering the past 12–18 months – with supporting artifacts like release notes, test reports, or stakeholder emails – fills the gap your manager cannot fill from memory.

Competing offer as leverage. Using a competing offer is a legitimate tactic if you genuinely have one and are genuinely willing to leave. Using a fabricated offer is a career risk that rarely pays off in close-knit verticals like healthcare IT, where reputations travel. If you do have an offer, name the number and ask your current employer to match or explain why they cannot. Then decide based on the full picture, not just the salary figure.

After the Merit Conversation: What Comes Next

Whatever the outcome, follow up in writing within 24 hours. A brief email summarizing what was discussed – the number offered, any commitments made, and the next checkpoint if one was agreed to – creates a paper trail both parties can reference. Managers move between projects, teams get reorganized, and verbal commitments disappear. Your email does not need to be formal. It just needs to exist.

Start building your evidence file for the next cycle immediately. The professionals who consistently get above-median merit increases in IT are almost always the ones who track their impact throughout the year, not the ones who spend two weeks scrambling to reconstruct a case the week before their review.

If you are building your broader career case – whether as a product owner or as a cross-functional analyst – the merit conversation is one data point in a longer professional narrative. The case you make this year shapes the credibility you carry into next year’s conversation.