Every self-evaluation form has a box called "Areas for improvement," "Opportunities for growth," or "What would you do differently?" It's often the hardest box to fill out. Write something fake like "I work too hard," and your manager rolls their eyes. Write something too harsh, and you worry you're talking yourself out of a good rating.
The trick is simple: name a real work habit that caused friction earlier in the review period, and pair it with the adjustment you've already started making.
Below is the three-step formula, 15 copy-and-paste examples grouped by theme, and what to avoid.
The formula: friction, lesson, adjustment
A strong "area for improvement" answer has three sentences:
- The friction: A specific pattern or moment that didn't go as well as it could have.
- The impact: Why it mattered to the work or the team.
- The adjustment: The concrete habit or process you changed (or are changing now).
Example: "In the first half of the year, I said yes to too many small ad-hoc requests, which slowed down our main Q2 migration. I started tracking incoming asks in a shared backlog and reviewing priorities with my manager every Monday, which kept our Q3 deliverables on schedule."
Notice why this works: it's honest, it doesn't blame anyone else, and the problem is already being solved.
Instead of humblebrags or self-sabotage
| Don't write this | Write this instead |
|---|---|
| I'm too much of a perfectionist. | On early drafts, I sometimes held specs too long before sharing. I now share a rough one-pager within two days to get feedback earlier. |
| I'm bad at time management. | When juggling multiple projects in Q2, I waited too long to flag a scheduling conflict. I now block weekly planning time every Friday and flag timeline risks at least a week out. |
| Other teams were slow to reply to me. | Some cross-team handoffs stalled when I only followed up in Slack. I started setting clear due dates and owners in a shared tracker and escalating blockers in our weekly sync. |
| I don't speak up enough in meetings. | In large group meetings I often held back questions until afterward. I now review the agenda ahead of time and bring at least one written question or recommendation to the call. |
15 areas for improvement examples by category
Adapt the details below to match your actual work this year.
1. Prioritization and saying no
- "Earlier this year, I took on too many urgent side requests without trading off existing work, which stretched turnaround times on my main project. I now ask requesters for their deadline and check priority trades with my manager during our weekly 1:1."
- "I tended to jump straight into easy tasks when my queue got busy instead of tackling the hardest blocker first. I've started blocking the first 90 minutes of my morning for deep project work before checking chat."
- "I underestimated how long cross-team reviews would take on the Q2 rollout. For Q3 and Q4 projects, I built a full week of review buffer into the schedule up front."
2. Communication and stakeholder updates
- "When a project was on track, I sometimes went quiet instead of sending regular updates, which left stakeholders wondering where things stood. I now send a short written weekly status update every Friday even when nothing is blocked."
- "My early project specs were too long for busy reviewers to skim, which slowed down sign-offs. I moved to a one-page format that puts the decision needed and the trade-offs at the very top."
- "When I hit a technical blocker in Q1, I spent three days trying to solve it solo before asking for help. I now follow a half-day rule: if I'm stuck for more than four hours, I post what I've tried and ask the team."
3. Delegation and documentation
- "Because I knew our legacy process well, I kept handling edge cases myself instead of documenting them, which made me a bottleneck when I took PTO. I've started turning every recurring question into a short checklist in our team wiki."
- "On the summer launch, I reviewed every small task myself instead of trusting the checklist. Next quarter I'm focusing on defining clear acceptance criteria up front so teammates can ship without waiting on my final check."
- "I took on most of the new-hire questions in chat rather than pointing people to written docs. I'm updating our onboarding FAQ each month so answers live in one shared place."
4. Scoping and estimation
- "On the reporting rebuild, I agreed to add three late feature requests mid-sprint, which pushed our release back by a week. I now keep a 'v2 follow-up' list during builds so we can ship the core change on time first."
- "My initial timeline estimates only counted build time and missed QA and documentation. I now include testing, docs and rollout steps as separate lines whenever I scope a project."
- "I started two process changes this year without defining how we'd know they worked. Going forward, I'm writing down the 'before' baseline and one clear success check before kicking off a change."
5. Strategic visibility and cross-team context
- "I focused heavily on executing my own queue this year and spent less time sharing what our team learned with adjacent groups. Next quarter I plan to share a short monthly recap of customer themes with product and sales."
- "During planning, I sometimes accepted requirements at face value without asking enough questions about the underlying customer problem. I'm making a habit of asking 'what problem are we solving and what happens if we wait?' before starting work."
- "I want to get more comfortable presenting trade-offs to leadership. I've asked to lead the monthly readout for my project area starting next quarter to get more reps."
Fill-in template
Copy this structure and fill in the brackets with one or two real examples from your year:
Area for improvement: [Skill or habit, e.g., Flagging timeline risks earlier]
What happened:
Earlier in [quarter/project], I [specific habit, e.g., waited until we were sure a deadline would slip before updating stakeholders], which caused [real effect, e.g., a last-minute rush on the launch checklist].
What I changed:
Since [month], I started [specific new habit, e.g., sending a Friday status update with a 'risks' line and flagging dependencies as soon as they slip by more than two days].
Next step:
In the next review period, I want to build on this by [one concrete goal for next quarter].
Make the next review easier
Notice how the strongest answers above rely on specific memories—what slipped in Q1, what you changed in Q3, and how Q4 went better because of it. When you try to remember all of that from scratch in November, you end up writing generic filler.
When you keep a short weekly note—even two sentences every Friday—you capture both your wins and the small process adjustments you made along the way. See our weekly status update template or our guide on writing a self-review when you can't remember what you did.
For the accomplishments half of your form, browse our role guides for Operations, Project Managers, Product Managers, and Customer Success, or paste a rough work note into the free STAR method generator.
To log your week in a minute and turn your real notes into a brag sheet and STAR stories at review time, start free on WinStash.