← All guides

FAQ

What's the Difference Between a Win and an Achievement?

Achievd gives you two ways to capture work, and the difference between them is mostly about timing and polish, not importance.

A win is a journal entry

You debugged the payment issue that was failing 5% of transactions. The VP of Sales liked the Q3 dashboard and said so. The API documentation finally has a first draft. Wins are quick to capture, deliberately low-bar, and frequent; they are the work log your future self will be desperately grateful for, because the single biggest reason resumes undersell people is that the evidence was never written down.

Capture a win the day it happens, in one or two plain sentences, and move on. It does not need a metric. It does not need a verb upgrade. It needs to exist.

An achievement is what a win grows up into

Polished, quantified, written with a result, a metric, and a method, and ready to appear on a resume without further work.

Wins feed achievements

That is the actual relationship. A monthly review of your wins will keep surfacing the same project five times from different angles, and those five small entries usually combine into one strong, fully-evidenced achievement. The win about the bug fix, the win about the positive feedback, and the win about the shipped feature were one story all along.

This is also why the low bar for wins matters. If capturing one requires a metric you do not have yet, you will not capture it, and the raw material for next year's resume quietly stops accumulating.

Which to use, in practice

• Something happened today and you have two minutes: win
• You have a number, a method, and a result: achievement
• Praise, feedback, or a moment worth remembering: win
• A project finished and you know how it turned out: achievement
• You are not sure it counts: win, always, because a win costs nothing to keep and cannot be recovered later if you skip it

When you generate a resume, achievements are what get selected and tailored, because they are already in fighting shape. Wins stay home and keep the record. Both belong in the vault; they just serve different moments.

What this looks like over a quarter

An example worth picturing, because the value of wins is invisible on any single day and obvious across three months. Five entries, captured in about ninety seconds each:

• Week 2: "Support flagged that 5% of checkouts fail. Reproduced it. Race condition on the payment callback."
• Week 3: "Shipped the fix. Failures down to almost nothing overnight."
• Week 5: "Added alerting on the payment path so it can't silently regress."
• Week 8: "Finance says recovered orders are running about $40K a month."
• Week 11: "Ran the postmortem; two other teams adopted the alerting pattern."

None of those is a resume line. Together they are one of the strongest bullets an engineer could write, complete with a metric, a method, a business number, and a scope claim. Every part of it came from a note written the week it happened.

Reconstructed from memory eleven months later, that same story is "fixed some checkout bugs."

The failure this prevents

Most people write their resume during the week they need it, from memory, about work they did years ago. The numbers are the first thing to go, then the methods, then entire projects. Wins exist because the cheapest possible defence against that is two sentences on a Tuesday.