Example Achievement Log for a Project Manager

Product & Project Management

Example Achievement Log for a Project Manager

This Project Manager kept a running log through the year, capturing delivery milestones, scope changes, and the awkward moments that shaped how they work. When review time came, they had concrete evidence of impact instead of a vague sense of 'staying busy'.

A year in the life of a Project Manager's log

  • Jan - achievement: CRM migration closed two weeks ahead of schedule. Compressed testing phase by running parallel UAT across three environments simultaneously instead of sequential. Live cutover on Feb 14 affected zero end users.
  • Feb - feedback: Sarah from Ops told me after standup: 'That testing plan was smart, we would have lost a week without it.' Caught me off guard because the timeline felt tight all the way through.
  • Feb - task: Took over DevOps roadmap when Marcus left mid-project. Had to learn their 2024 commitments in a week and rebase against two new budget cuts. First month was chaos, second month made sense.
  • Apr - achievement: Delivered Q2 infrastructure budget review three weeks early so finance could reforecast. Broke it into 23 line items instead of the usual eight buckets. CFO asked why we'd never done it that way before.
  • May - task: Payment processing backlog hit 47 open items by mid-June. Started daily 30-minute triage instead of weekly planning. Cut open count to 12 by month end but burned out the team doing it.
  • May - feedback: James pulled me aside before my one-on-one: 'You killed the backlog but people are exhausted. Sustainable pace matters.' Fair hit. Shifted to rolling prioritisation so we hit 80% of the throughput without the sprint.
  • Jul - achievement: Platform security audit scope ballooned from 6 weeks to 12 when compliance flagged legacy systems. Negotiated phased review: critical path in weeks 1-4, deferred non-blockers to Q4. Kept audit live date intact.
  • Aug - task: Rebuilt the roadmap tracker in Sheets after Smartsheet licensing was cut. Clunky but functional. Took six hours to map all 34 cross-team dependencies. Saved the team from a spreadsheet nightmare.
  • Oct - achievement: Closed three stalled vendor contracts by clarifying what success actually looked like on both sides. Contract terms dropped from disputed and unsigned to signed in 18 days. Both vendors said clarity saved weeks of back-and-forth.
  • Nov - task: Year-end reporting hit a snag when stakeholder definitions of 'on-track' diverged. Spent two weeks harmonising three different success metrics into one shared KPI. Won't solve for next year yet, but documented the gap.
  • Dec - feedback: Director mentioned in team standup: 'The way you mapped those vendor conversations actually changed how we're thinking about contracts going forward.' Surprised me, but that framework landed.

What makes a strong entry

What most people write: Improved project delivery times and streamlined testing processes.

What went in the log: CRM migration closed two weeks ahead of schedule. Compressed testing phase by running parallel UAT across three environments simultaneously instead of sequential. Live cutover on Feb 14 affected zero end users.

The strong version names the specific project, the concrete technique (parallel UAT across three environments), the actual timeline moved (two weeks), and the outcome that mattered (zero user impact). Six months later, this is evidence you can point to and explain; the weak version is forgotten.

What most people write: Managed backlog and improved team efficiency under pressure.

What went in the log: Payment processing backlog hit 47 open items by mid-June. Started daily 30-minute triage instead of weekly planning. Cut open count to 12 by month end but burned out the team doing it.

The strong version gives the actual numbers before and after (47 to 12), names the tactic (daily triage instead of weekly), and critically, owns the trade-off (team burnout). This honesty about the unsustainable approach shows judgment, not just speed.

How this becomes your review in November

I delivered visible wins on timeline, the CRM migration shipped two weeks early with zero user impact, and the Q2 infrastructure budget landed three weeks early with detailed line-item breakdown that prompted the CFO to ask why we'd never structured it that way before. I also learned to see the gap between hitting a number and sustaining the team: I crashed the payment processing backlog from 47 to 12 items in one month, but burned people out doing it. James was right to flag it, and I shifted to rolling prioritisation to hit 80% throughput without the sprint. By year-end I was thinking more deliberately about scope, stakeholder clarity, and pace, the vendor contracts closed fast once I clarified what success actually meant for both sides.

Starting your own log

Don't try to reconstruct a year you have already had. Start from today, one line whenever something happens, and let it build. The Perform Review Achievement Log does this for you and can capture wins straight from Slack, and how to start an achievement log covers the wider playbook.

Example Logs for Related Roles

Ready to start your own? Start your Achievement Log free, see how the Perform Review Achievement Log works, or browse performance review phrases for Project Manager.