Employee Evaluation & Reviews9 min readNovember 17, 2026

Is This IC Ready to Manage? Assessing First-Time Manager Readiness

By Career Ladder Builder

Is This IC Ready to Manage? Assessing First-Time Manager Readiness

The promotion that looks obvious and is not

Dana has been the best support engineer on the team for three years. She closes the hardest tickets, writes the runbooks everyone else uses, and mentors new hires without being asked. When the team lead resigns, the CEO says what everyone is thinking: "Promote Dana." Her skip-level agrees. Dana says yes before she has been told what the job involves.

Six months later the team is quieter and slower. Dana still takes the worst tickets herself because explaining them takes longer than solving them. Her 1:1s are status updates. Two engineers have stopped bringing her problems. She works longer hours than before and tells you privately that she is not sure she is any good at this. Nobody did anything wrong, and the company still lost its best technical contributor and gained a struggling manager in one decision.

The failure was in the evidence base. The decision was made on how well Dana did the old job, and no one had written down what the new job requires or checked her against it. This article shows you how to define the first manager expectation, gather evidence against it before the promotion, and run a structured assessment that ends in a clear "ready" or "not yet" with a plan. Done well, first time manager readiness becomes a documented judgment instead of a hunch.

Why first time manager readiness cannot be read from IC performance

Individual contributor work and first-line management reward different behaviors. An IC is evaluated on the quality of their own output. A first-time manager is evaluated on the output of other people, which means that the habits that made them excellent, such as taking the hard problem and solving it quickly, can become the habits that hold the team back.

The stakes are not small. Gallup reports that managers account for 70% of the variance in team engagement (Gallup, 2024). A promotion that puts the wrong person in that seat affects every direct report, not only the person promoted.

This is why readiness has to be assessed against the manager role itself. Past IC ratings tell you how well someone performs at the level they currently hold. They do not tell you whether the person can delegate, hold a difficult conversation, or give up the satisfaction of doing the work personally. If your company runs separate IC and manager ladders, the crossover between them is a decision point with its own criteria; see how to design the IC vs. manager track for the structure that makes the crossover explicit.

Define the M1 expectation before you assess anyone

First time manager readiness is a gap measured against a standard, so the standard has to exist first. Call the first manager level M1. Write M1 expectations as observable behaviors, in the same style as your other level definitions: a competency name, then a statement of what a person at that level does.

Here is a starting set of six M1 competencies, with sample statement wording:

Competency M1 expectation (sample wording)
Delegation Assigns work with a clear outcome, deadline, and decision rights, and does not take the work back when it is done imperfectly.
Feedback Gives specific, timely feedback on observed behavior, including corrective feedback, without waiting for a review cycle.
One-to-one management Runs regular 1:1s that the report sets the agenda for, and follows up on commitments made in them.
Prioritization for the team Sets team priorities, declines work, and explains trade-offs to the team and to stakeholders.
Performance management basics Recognizes underperformance early, documents it factually, and escalates to HR before it becomes a crisis.
Developing others Knows each report's goals, identifies a development action for each, and checks progress.

Adapt these to your company. A seven-person sales team and a forty-person engineering group will not weight them the same way. What matters is that each statement describes something a third person could see or hear, and that each one has a target score. For M1, a reasonable target on most competencies is 3 on a 1–5 scale, meaning the person does it reliably with occasional support. Mark one or two as critical, such as feedback and delegation, where a gap should block the move rather than just generate a development item.

Gather evidence before the move, not after it

A candidate cannot demonstrate M1 behaviors from inside an IC role, but they can demonstrate the early forms of them. The job of the assessor is to find these, and to be honest when there are none. Good sources of pre-promotion evidence:

  • Informal leadership. Has the person led a project with other people's deliverables on the critical path? Did they assign work, track it, and handle slippage?
  • Mentoring. What did the mentee actually do differently afterward? "Helps new hires" is not evidence. "Walked two new hires through the escalation process and both handled their first escalation alone within a month" is.
  • Feedback given. Ask for a specific instance in which the candidate told a peer something uncomfortable and useful. Ask the peer as well.
  • Stretch assignments. A short acting-lead stint, running the sprint review, or owning an onboarding cohort all produce observable behavior. Treat them as part of the assessment, not as a favor.
  • Upward and lateral input. Ask two or three peers and one stakeholder how the candidate behaves when they disagree, when they are under pressure, and when someone else gets the credit.

Record each piece of evidence against the competency it supports, with a date and a source. The discipline of writing it down is what separates an assessment from an impression. The craft of writing notes that another person could verify is covered in writing evidence notes, and the same standard applies here: a note should say what happened, who saw it, and why it counts.

Be wary of one specific trap. The people most likely to be proposed for management are often the people with the strongest IC track record, and an assessor who already admires the candidate will read ambiguous evidence generously. Have a second person review the evidence file independently before scores are set.

Score each competency and compute the gap

Use the same 1–5 scale you use elsewhere so that the scores are comparable. If you need a refresher on anchoring the scale so that a 3 means the same thing to every rater, see one-to-five evaluation scoring.

Score each M1 competency from the evidence, then subtract the score from the target to get the gap. A positive gap means the candidate is below the M1 expectation. A zero or negative gap means they meet or exceed it.

Worked example (illustrative numbers). The target is 3 on every competency. Feedback and delegation are marked critical.

Competency Target Score Gap
Delegation (critical) 3 2 1
Feedback (critical) 3 3 0
One-to-one management 3 3 0
Prioritization for the team 3 4 -1
Performance management basics 3 2 1
Developing others 3 3 0

The candidate has two gaps, one of them on a critical competency. The strength in prioritization does not cancel the delegation gap, because you do not average across competencies when one of them predicts a specific failure. A simple decision rule for this example: ready means no open gap on a critical competency and no more than one gap elsewhere, each of size 1. Under that rule this candidate is "not yet, 2 gaps," because delegation is critical.

Set the decision rule before you look at any candidate's scores. A rule written after the scores are in is a rationalization, and it will be read that way if the decision is ever challenged.

Reach a decision and write a "not yet" plan that means something

There are three honest outcomes. Ready now. Ready after a defined development period. Not suited to the manager track at this time. The second is the most common and the one most often handled badly, usually with a vague "keep growing and we will revisit."

A useful "not yet" plan has five parts:

  1. The specific gaps, named by competency, with the score and the target.
  2. An action for each gap, tied to a behavior. For a delegation gap, that might be: own a two-person project where the candidate must assign work and cannot do it themselves.
  3. An owner and a date for every action, so that nothing depends on goodwill.
  4. Evidence that will count. State in advance what you will look at when you reassess, such as the outcome of the project and input from the two people the candidate assigned work to.
  5. A reassessment date. A "not yet" without one is perceived as a "no."

Tracking these actions as concrete items with owners is covered in development action items. The conversation matters as much as the document. Tell the person where they stand, what you observed, and what would change the answer. An IC who hears "not yet, and here is exactly why" has something to work with. One who hears nothing, or hears a vague reassurance, tends to leave.

The ready-now outcome also deserves a plan. Even a candidate with no open gaps will be weakest at the things they have never done, so set a 90-day check-in against the same six competencies.

Making the assessment repeatable

A repeatable first time manager readiness process matters more than any single assessment. Doing this once for Dana is useful. Doing it the same way for every IC who is considered for management is what makes the process fair, and it is what lets you explain a decision to the candidate, to their peers, and to a skeptical executive. Keep the competency set, the scoring scale, and the decision rule constant across candidates, and keep the evidence in one place.

If you are building this by hand, a spreadsheet with a tab per candidate will do the job. The First-Time Manager Readiness Assessment Workbook is built for this: you rate an IC against the M1 expectation, evidence each rating, and get a computed "ready / not yet — N gaps" crossover verdict. For the broader question of readiness across any role move, not only the move into management, see how to evaluate employee career readiness.

Whatever tool you use, keep the order straight: define M1, collect evidence, score, compute the gap, apply the rule you wrote beforehand, and only then decide. Dana's promotion could have been the same decision with a different process, and the process is the part you control.

Enjoying this? Get more HR development guides in your inbox.

Related guides

Self vs Manager Rating Gaps: What They Mean and How to Resolve Them
Employee Evaluation & Reviews8 min read

Self vs Manager Rating Gaps: What They Mean and How to Resolve Them

A gap between a self-rating and a manager rating is normal, but an unresolved one undermines the whole evaluation. Here is what the common gap patterns mean and how to close them with evidence.

October 27, 2026Read More
How to Run Better Career Conversations as a Manager
Employee Evaluation & Reviews8 min read

How to Run Better Career Conversations as a Manager

Career conversations fall apart without structure. Here is how to anchor them in the framework and a gap report.

June 19, 2026Read More
How Often Should You Run Performance Reviews?
Employee Evaluation & Reviews8 min read

How Often Should You Run Performance Reviews?

More reviews are not always better. Here is how to pick a review cadence that fits your size and stage.

June 11, 2026Read More