Keep an Achievement Log That Shows Outcomes, Not Just Activity

A list of tasks says what occupied your time. An achievement log explains what changed because of your work. That distinction is useful when preparing a review, updating a résumé, or discussing a larger role.

For each example, record the problem, your contribution, and the result. Use figures when you can verify them, and avoid claiming a whole team’s output as your own. If a result cannot be measured easily, describe an observable improvement and identify who could confirm it.

A short weekly note is often easier than trying to reconstruct a year from memory. Include lessons from work that did not go to plan as well as successes. Do not copy confidential customer information or sensitive internal documents into a personal account.

Use the log to prepare a small selection of examples relevant to the role you want. The point is to make a discussion concrete, not to present every email you sent. CareerOneStop’s career-planning resources can provide background as you decide which skills and experiences to develop next.

Turn one accomplishment into a short record

Take a completed project and describe the starting problem, your particular contribution, and the observed result. Attribute shared work accurately. A reader should be able to distinguish your action from the team’s overall output without needing the full history of the project.

A practical next step

Keep the note in an approved location and omit sensitive customer or internal information from personal records. Add a contact who could confirm the contribution where appropriate. A few relevant examples can support a review more effectively than an exhaustive list of every task you touched.

Before making the decision, use the following points to identify missing information. Record an answer or a follow-up question for each one rather than treating an unknown detail as settled.

• Problem and personal contribution.
• Observable and verifiable result.
• Accurate attribution of shared work.
• Relevant example for the target role.

What if I do not have a numerical result?

Describe an observable change and how it could be checked. Explain what became clearer, easier, or more reliable, without inventing a percentage to sound impressive. The useful standard is whether the example demonstrates the skill being discussed and can withstand a reasonable follow-up question.

Keep the decision in context

Keep development, responsibilities, and the formal advancement decision distinct. A useful plan names the capability to demonstrate, an opportunity to practice it, and a review process. Record shared expectations without treating extra work as an automatic guarantee of a title or pay change. Reassess whether the plan still serves your goals when the organization or role changes.