Writing a Self-Review That Gets Noticed
让老板看见的绩效自评模板
绩效自评不是谦虚大赛,而是帮老板给你写晋升理由的素材库。用『动作+量化结果+业务影响』三段式描述成绩,主动认领一个成长项并写清改进计划,再点出下一档位的贡献。照着这四组模板改写你自己的数字和项目,你的自评就会从『干了很多活』变成『值得被提拔』。
当前浏览器暂不支持语音朗读
Here is a self-review section you can copy and adapt: "In the first half, I led the migration of our billing system to the new platform. I coordinated three teams, shipped the project two weeks ahead of schedule, and cut monthly reconciliation errors from about 40 to under 5. This reduced the finance team's manual work by roughly 12 hours a week and removed a recurring source of customer complaints."
Notice the shape of that paragraph. It names the action, gives a hard number, and then connects the number to business value — saved hours, fewer complaints. Do not write "I worked hard on the billing project." Everyone works hard. Managers are looking for impact they can defend in a room full of other managers. When you swap in your own numbers, always ask: so what did this change for the company?
Use this template when you improved something you cannot easily measure: "I rewrote our onboarding documentation after noticing new hires kept asking the same setup questions in chat. Since then, three new engineers have told me they got productive on day one instead of day three, and the number of setup questions in our channel has clearly dropped."
When you lack a clean metric, reach for proxies: direct quotes from colleagues, before-and-after comparisons, or a visible drop in some annoying pattern. "Three new engineers told me" is softer than a percentage, but it is still evidence. Keep the specifics — the names of the systems, the rough size of the change. Vague praise of yourself convinces nobody; concrete detail does the persuading for you.
Do include a growth area, and frame it like this: "One area I want to strengthen is delegation. On the migration project I took on too much of the testing myself, which created a bottleneck near the deadline. Next quarter I plan to hand off test ownership earlier and coach a junior engineer to run it, so the team is less dependent on me."
A good growth area is honest but not damaging, and it always comes with a plan. Choose something real that you are already fixing, not a weakness that makes people question whether you can do the job. The pattern is: name the gap, show you understand its cost, and describe the concrete next step. This reads as self-awareness — one of the clearest signals that you are ready for more responsibility.
Finally, plant a flag for the next level: "Beyond my own deliverables, I increasingly acted as a technical point of contact for two partner teams, unblocking their integrations and reviewing their designs. I would like to formalize this scope and take on more cross-team ownership in the next cycle." This quietly tells your manager you are already doing the next job, and only need the title to catch up.