📋 Contents
- Why a manager self-assessment is a different document
- What reviewers look for in a manager’s self-review
- A one-page structure that works
- Team results: example phrases
- Coaching and developing people: example phrases
- Hiring, decisions and cross-team work: example phrases
- Team health: what to say and what to leave out
- Growth areas: honest examples for managers
- Rating yourself and common mistakes
PART 1
Why a manager self-assessment is a different document
As an individual contributor, your self-review answers one question: what did you deliver? As a manager, the question becomes harder to answer in a sentence: what did your team deliver, and what part of that would not have happened without you? Your own boss, often a director or senior manager, will read your self-assessment looking for both.
It also gets read differently. At companies that run calibration, a manager’s rating is usually discussed by a room of more senior leaders who know your team’s results only vaguely. They will look for evidence that you raised the bar, grew people, made sound calls with incomplete information and kept the team healthy under pressure. Your self-assessment is the most detailed source they will have.
The trap most new managers fall into is writing an individual contributor review with "my team" pasted in front of each line. That reads as either taking credit for others’ work or not understanding the job. The fix is to describe your decisions and interventions, then the team outcome they led to.
💡 One test for every sentence
Ask: "Could one of my direct reports have written this exact line about themselves?" If yes, it describes their work, not yours. Rewrite it to show the choice, the coaching or the structure you put in place.
PART 2
What reviewers look for in a manager’s self-review
Most US companies evaluate people managers on some mix of the same five or six areas, even if the competency names differ. Map your material to these before you write.
| Area | What they want to see | Typical evidence |
|---|---|---|
| Team results | Did the team hit its goals or OKRs? | Goals met, launches shipped, service levels held, budget kept |
| People development | Are your people growing? | Promotions supported, new scope given, skills built, feedback cycles run |
| Hiring and team building | Did you build the right team? | Roles filled, quality of hires, onboarding, diverse pipelines, backfills handled |
| Execution and judgment | Do you make good calls and manage risk? | Priorities you set or cut, risks raised early, trade-offs explained |
| Cross-functional influence | Do other teams want to work with yours? | Shared plans, resolved conflicts, dependencies unblocked |
| Team health | Is the team sustainable? | Retention, workload balance, engagement survey follow-up, on-call fairness |
Your company’s leadership competencies may use different names. Use their exact wording as section headings so your reviewer can match them.
PART 3
A one-page structure that works
Opening summary (3–4 sentences)
The team’s headline results, the biggest management challenge you faced and how you handled it. Write it last.
Team outcomes against goals
Each team goal or OKR with its status, and one line on what you did that shaped the result.
People: growth, feedback, hiring
Who grew and how, hard conversations you had, roles you filled and how new hires ramped.
Decisions and trade-offs
Two or three calls you made, what you gave up, and how they turned out.
Working across the company
Partnerships, escalations resolved, shared processes you set up.
Your growth areas and next period
One or two honest patterns with a plan, and what you want to take on next.
Keep names of direct reports out of anything that sounds like a judgment of them. "Supported one engineer through a promotion case" is fine; detailed assessments of individuals belong in their own reviews, not yours.
PART 4
Team results: example phrases
Lead with the outcome, then name the management move behind it.
- The team delivered three of four quarterly OKRs. I cut the fourth in Q2 after it became clear it depended on a platform change that would not land this year, and redirected two people to the onboarding project, which then shipped a month early.
- Held our support team’s first-response target through the holiday peak by rebuilding the shift schedule with the team instead of adding overtime.
- Took over a team mid-project with no shared plan; within three weeks we had a single tracker, weekly demos for stakeholders and a revised date we then met.
- Reduced unplanned work by introducing a weekly intake review, so requests from other teams were prioritized together instead of landing directly on individuals.
✍️ Before → after
Before: My team launched the new billing system on time.
After: I split the billing launch into three releases after the first risk review, assigned each to a different lead so two people got their first ownership experience, and the team delivered all three on the agreed dates.
PART 5
Coaching and developing people: example phrases
This is the section that most separates strong manager reviews from weak ones. Show specific growth, not that you "care about development."
- Held weekly 1:1s with all six direct reports and moved them from status updates to development topics by sharing a running agenda doc each person owns.
- Supported two team members through promotion: helped each build a case from their own project record and gave them stretch scope six months ahead of the cycle.
- Gave one underperforming team member clear, written expectations and a 60-day plan with HR’s guidance; they met the plan and now lead our release process.
- Delegated client-facing quarterly reviews to a senior team member for the first time and coached them through the first two; they now run them independently.
- Asked every report for upward feedback twice this year and acted on the most common request: fewer last-minute priority changes.
⚠️ Don’t take credit for promotions
Write "supported" or "helped build the case for," not "promoted." Promotions are usually decided by a committee, and claiming them reads badly to the people who sat on it.
PART 6
Hiring, decisions and cross-team work: example phrases
Hiring and team building
- Filled two open roles and one backfill this year; rewrote our interview loop around a work sample so candidates were assessed on the same tasks.
- Built a 30-60-90 day onboarding plan that new hires now get on day one; the last two hires shipped their first change in their first two weeks.
Decisions and judgment
- Pushed back on adding a fifth integration to the Q3 plan, explained the risk to the VP with the team’s capacity numbers, and we agreed to move it to Q4.
- Called an early stop to a vendor pilot when the data showed it would not meet our requirements, which freed the budget for the reporting rebuild.
Cross-functional influence
- Set up a monthly planning sync with the product and sales leads, which ended the pattern of sales promising dates the team had not seen.
- Resolved a long-running ownership dispute over the customer data pipeline by drafting a RACI with the other manager and getting our directors to sign off.
PART 7
Team health: what to say and what to leave out
Team health is increasingly part of manager evaluations: attrition, burnout, engagement survey results, and whether the work is spread fairly. Write about it, but stick to what you did.
- Shared our engagement survey results with the team, picked the two lowest-scoring items together and made one change for each (clearer promotion criteria and a protected no-meeting afternoon).
- Rebalanced on-call so it no longer fell mostly on the two most experienced engineers.
- Lost one team member to an external move this year; held a candid exit conversation and changed how we assign project lead roles as a result.
Avoid sharing confidential details about anyone’s health, leave or personal situation, even in a positive light. "Covered a six-week absence on the team without missing deadlines" says enough.
PART 8
Growth areas: honest examples for managers
Senior readers are wary of managers who list no weaknesses. Pick one or two real patterns and pair each with what you are changing.
- I stayed too close to the technical work in the first half and became a bottleneck on reviews. I now review only design-level decisions and have two senior engineers sign off on the rest.
- I waited too long to address a performance concern, hoping it would resolve on its own. I now raise concerns in writing within two weeks of noticing a pattern.
- My updates to leadership were detailed but did not lead with decisions needed. I now open every update with "asks" and "risks."
- I said yes to too many cross-team requests on behalf of the team. I now check new commitments against our quarterly priorities before agreeing.
💡 Tie the growth area to your next goals
If your growth area is delegation, make one of next year’s goals "two team members independently own a quarterly deliverable." It shows the reflection is real.
PART 9
Rating yourself and common mistakes
If your form asks for a self-rating, base it on the team’s results and your contribution to them. A team that missed goals because of your call to reprioritize can still support a strong rating if the call was right and well communicated. Say so explicitly.
☐ Every team result is paired with a management action you took.
☐ You described at least two people who grew, without naming private details.
☐ You included one decision that cost something, and why it was worth it.
☐ Your growth areas are specific and have a next step.
☐ You did not blame individuals on your team for missed goals.
☐ You used your company’s competency names as headings.
⚠️ Mistakes that weaken manager self-reviews
Listing your own individual tasks; writing "we" for everything so your role disappears; overstating credit for promotions or wins; ignoring attrition or survey results your boss already knows about; and turning the growth section into a list of complaints about resources.
Frequently asked questions
Q. What should a manager write in a self-evaluation?
Team results against goals and what you did to shape them, how your people grew, hiring and onboarding, key decisions and trade-offs, cross-team work, team health, and one or two growth areas with a plan.
Q. How is a manager self-assessment different from an employee self-assessment?
It focuses on outcomes delivered through others. Instead of describing tasks you completed, you describe the structures, coaching and decisions that helped your team succeed.
Q. Should I mention my direct reports by name?
Use names sparingly and only for positive, non-confidential facts like "supported Jordan’s first project lead role." Keep any assessment of individuals in their own reviews.
Q. What are good weaknesses for a manager self-review?
Real patterns such as delegating too little, addressing performance issues late, staying too hands-on, unclear communication of priorities, or overcommitting the team. Pair each with a concrete change.
Q. How do I write a self-review as a new manager?
Focus on the transition: what you took over, how you built trust and routines like 1:1s, the first decisions you made, and what you are still learning. It is fine to say you are early in the role.
Q. How long should a manager self-assessment be?
One to two pages is typical. Follow your review tool’s character limits, and lead each section with your strongest sentence because senior readers skim.
Q. What if my team missed its goals?
State it plainly, explain the cause, describe what you did once you saw the risk, and what you changed afterward. Clear judgment under a miss often counts more than a vague claim of success.
This article is general guidance. Review formats, rating scales and expectations vary by company — check your own company’s guidelines alongside it.
PLAN2FOLIO
Evidence for reviews, raises and job moves — starting with one line today
Write what you did today in one line. PLAN2FOLIO sorts it into the outcomes of your role, drafts your weekly report on Fridays and gathers evidence by outcome at review time. Free to start.
Start free →📄 Career & Reviews
Keep reading