Example Achievement Log for a Program Manager

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

• Feb - task: Took over CRM consolidation programme from outgoing PM. Inherited 14-week timeline with no charter, four vendor proposals still unsigned, and finance team looped in informally. Started from zero context.
• Feb - feedback: Finance lead Maria said in the kickoff, 'This is the first time someone's actually asked us what we need instead of telling us.' Set the tone for the year.
• Apr - achievement: Signed vendor contract and locked scope. Cut proposed modules from 11 to 7, which cut go-live slip from estimated 8 weeks to 2 weeks. Saved £40k in licensing year one.
• May - task: Ran weekly triad meetings with tech lead James and ops sponsor Patricia through build phase. Caught schema mismatch in legacy customer data during design, not cutover. Pushed testing back two weeks, saved the cutover date.
• Jul - achievement: CRM went live on 15 July with zero critical incidents in first 48 hours. 94% of staff completed training beforehand. Cutover plan we'd drilled three times worked.
• Aug - task: Post-go-live support stretched into month two. Handled three data reconciliation issues that weren't caught in UAT. Each one took a day. Revised our UAT checklist for next programme.
• Sep - feedback: James told me in the debrief, 'You actually listened when we said things were at risk instead of pushing the date.' Said it in front of the steering committee.
• Oct - task: Brought a small finance automation project back from red to on track. Inherited it mid-stream when original PM left. Slashed the scope of reporting features, bought us four weeks.
• Oct - achievement: Staffing and contractor burn rate across both active programmes came in 12% under budget. Tightened forecasting process in August, caught the overspend early.
• Nov - achievement: Built risk register template that other PMs now use. After CRM cutover issues, started tracking risk appetite per workstream. Patricia's team adopted it for next year's roadmap.
• Dec - task: Closed out both programmes. Created handover guides for ops support team covering the CRM's quirks and the automation tool's gaps. Documented what we'd skip next time.

What makes a strong entry

How this becomes your review in November

I took on the CRM consolidation programme mid-flight with no charter and unsigned vendor contracts, then locked scope by cutting seven low-value modules, which halved the predicted go-live slip and saved £40k in licensing costs. Throughout build, I caught a critical legacy data issue early enough to push testing back two weeks instead of slipping the cutover, and the programme went live on schedule with zero critical incidents. Both active programmes finished 12% under budget on staffing burn, and the risk tracking template I built is now being adopted across the department for next year's roadmap.

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

• Technical Program Manager achievement log example
• IT Project Manager achievement log example
• Delivery Manager achievement log example
• Project Manager achievement log example
• Product Manager achievement log example
• Project Coordinator achievement log example