Example Achievement Log for a Content Writer

Marketing & Content

Example Achievement Log for a Content Writer

This Content Writer spent the year moving between fast-turnaround web copy, long-form product guides, and an unexpected pivot to SEO fundamentals when the team's organic traffic dipped. The log shows not just what got published, but what broke, what stuck with readers, and when a process change actually worked.

A year in the life of a Content Writer's log

  • Jan - task: Took over the Help Center backlog from departing Content Writer. 47 articles in various states of review, oldest flagged March 2023. Sorted by priority and reassigned 12 to subject matter experts for final sign-off.
  • Mar - achievement: Rewrote six high-traffic onboarding pages using clearer heading hierarchy and removed jargon. Bounce rate on /getting-started dropped from 52% to 38% within three weeks, Sessions up 19%.
  • Mar - feedback: Maya in Product said in Slack: 'This explainer for the new billing feature is so much easier to follow than our old docs. Users are asking fewer support questions.' Meant a lot.
  • Apr - achievement: Delivered 8000-word integration guide for Slack workflow builder. Included 12 code examples, a troubleshooting matrix, and video timestamps. Published April 15, ranked position 3 for 'Slack workflow automation' by May.
  • Jun - task: Blog traffic flatlined at 2100 monthly readers. Audited keywords we were targeting; found we'd been chasing low-intent terms. Rebuilt keyword strategy around buyer-stage content instead of just feature searchability.
  • Jun - achievement: Published five buyer-stage comparison posts targeting 'X vs Y' keywords. 'Competitor tool vs us' posts captured 340 monthly organic visits by end of August. Cost per lead dropped 24%.
  • Aug - task: Implemented content calendar in Airtable to replace email threads. Broke the system first week by linking to wrong table. Rebuilt relationships correctly and trained the team. Now actual handoff time is 40% faster.
  • Sep - feedback: David from Sales in our 1-on-1: 'That ROI calculator post you wrote closed at least two deals. People send it to me unprompted.' First time someone from Sales mentioned my work directly.
  • Sep - achievement: Finished the Help Center backlog. All 47 articles either published, archived, or formally deprioritized. Updated 18 articles with new API parameters released in v2. Zero flagged items remaining.
  • Nov - task: Attempted to write a technical deep-dive on our data pipeline. Realised mid-draft I didn't understand the tool well enough. Asked Engineering for a session, took three notes, rewrote from scratch. Piece landed accurately but took twice as long.
  • Dec - achievement: Year-end content audit: 89 pieces active, 14 archived, avg. dwell time up to 2m 34s from 1m 18s in January. Organic traffic to content section hit 5800 monthly sessions, up 176% from start of year.

What makes a strong entry

What most people write: Rewrote onboarding pages to improve readability. Bounce rate improved significantly.

What went in the log: Rewrote six high-traffic onboarding pages using clearer heading hierarchy and removed jargon. Bounce rate on /getting-started dropped from 52% to 38% within three weeks, Sessions up 19%.

Adding the specific metric (52% to 38%), the timeline (three weeks), and the secondary outcome (Sessions +19%) transforms a vague claim into something reviewable and something the Content Writer can cite as proof of actual impact.

What most people write: Improved SEO strategy by targeting better keywords. Blog traffic increased.

What went in the log: Blog traffic flatlined at 2100 monthly readers. Audited keywords we were targeting; found we'd been chasing low-intent terms. Rebuilt keyword strategy around buyer-stage content instead of just feature searchability. Published five buyer-stage comparison posts targeting 'X vs Y' keywords. 'Competitor tool vs us' posts captured 340 monthly visits by end of August. Cost per lead dropped 24%.

The strong version names the starting problem and number (2100 flatline), the diagnosis (low-intent terms), the specific solution applied (buyer-stage pivot), which pieces were published (five comparisons), the measurable outcome (340 visits, 24% CPA reduction), and the timeline. A reviewer six months later can see exactly what changed and why.

How this becomes your review in November

This year I shifted the content function from reactive Help Center maintenance toward strategic SEO and buyer-stage positioning. I moved us off low-intent keyword targets onto comparison and integration content, which brought blog traffic from 2100 to 5800 monthly readers and reduced cost per lead by 24%. The onboarding rewrite alone dropped bounce rate by 14 percentage points, and I cleared a 16-month Help Center backlog while adding v2 API updates across 18 existing articles. The work has landed with Sales and Product, David mentioned two deals closed on our ROI calculator post, and Maya said user support questions dropped noticeably after the new billing explainer shipped.

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 Content Writer.