Six months after you solve a difficult problem at work, the details begin to disappear. You remember staying late, fixing something important, and hearing a relieved thank-you. The dates, numbers, and exact result are usually gone by the time a performance review or job application asks for them.
Your manager may have forgotten too. A busy workplace remembers the emergency in front of it and quickly moves on from the one you handled last spring. This is one reason capable people can reach review season with a vague paragraph about being dependable while someone else arrives with a list of projects, results, and messages from pleased customers.
A work wins file is a private record of useful things you have done. It can be a note on your personal device, a paper notebook kept at home, or a document that follows your employer's rules. You add a few lines while the facts are fresh. Later, those lines become raw material for a review, a raise conversation, an interview, or the unpleasant morning when a job ends without much warning.
Write down the result, not the whole day
Begin with work that left something better than you found it. Perhaps you cleared a backlog, trained a new employee, caught an expensive error, shortened a routine task, kept a customer, improved a document, or took responsibility when a project was wobbling. Ordinary competence counts. You do not need a trophy or a company-wide announcement before a piece of work is worth recording.
Give each entry a date and answer three questions: What was the problem? What did I do? What happened afterward? Two or three sentences are enough. Write the entry for a stranger who understands your field but was not in the room. Acronyms and inside jokes that feel obvious today may be useless a year from now.
| Weak note | Useful note |
|---|---|
| Helped with invoices | Found 18 invoices stalled by a missing approval, worked with purchasing to clear them, and wrote a checklist for the next batch |
| Trained Maya | Built a two-week training plan for a new coordinator and left reusable instructions for the five weekly tasks |
| Fixed report | Found a duplicated input in the monthly report before distribution and added a review step to catch the same error |
| Customer was happy | Resolved a delivery problem the same afternoon; saved the customer's written thank-you with the date and account name allowed by company policy |
The useful notes are still modest. They do not call anyone brilliant or pretend a routine fix transformed the company. They preserve enough detail to show the work and its effect. If you know a number, record it. If you do not, describe the result honestly and leave the number out.
Numbers help only when you can defend them
Money, time, volume, error rates, and response times can make an achievement easier to understand. They can also turn a good record into fiction. Do not claim that a change saved $40,000 because someone made an excited guess during a meeting. Keep the source beside the claim: a report, a project plan, a dated email, or your own clearly labeled calculation using figures you are permitted to retain.
Suppose a weekly task took 75 minutes before you rebuilt the worksheet and 30 minutes afterward. The difference is 45 minutes a week. Across 48 working weeks, that would be 36 hours. Write it as an estimate based on measured task time, not as 36 hours of guaranteed company savings. The distinction is small on the page and important in a conversation.
Some of the best work has no tidy number. Calming an angry client, helping a teammate learn a difficult process, or noticing a safety concern may matter greatly without producing a percentage. Record what happened, who can confirm it, and what changed. A credible sentence is more useful than an impressive statistic you cannot explain.
Save praise without building a shrine
When a customer, coworker, or manager sends a thoughtful compliment, save the date and the relevant portion if workplace policy permits it. The point is evidence, not reassurance on a bad afternoon. A short message can remind you which part of the work another person valued and give a manager a view beyond the projects they personally watched.
Be strict about confidential material. Do not forward private customer information, internal financial reports, health information, source code, trade secrets, or proprietary documents to a personal account. A harmless summary written in your own words is often enough: “June 12: department lead thanked me for catching the scheduling conflict before launch.” Follow the policies and agreements that apply to your job.
Credit other people. If four people finished the project, write what the team accomplished and name your part. Taking sole ownership may make a bullet sound stronger, but it creates an account you may have to defend in front of the people who did the work with you. Accurate credit also helps you remember which colleagues could speak about your contribution later.
Make Friday's last ten minutes do the work
A work wins file fails when it becomes another elaborate system to maintain. Put a repeating ten-minute appointment near the end of the week. Look at your calendar, sent messages, task list, and finished documents. Add one item if something worth keeping happened. Many weeks will produce nothing, and that is fine. Close the file when the timer ends.
- Date the entry so you can find the surrounding project later
- Name the problem in one sentence
- Describe your contribution without borrowing the whole team's work
- Record the result and the source of any number
- Note a person who saw the work, when appropriate
- Remove details you are not allowed to keep outside company systems
Once a month, add a line about work that has quietly expanded. Maybe you now approve orders, answer technical questions, cover a second location, or train every new hire even though none of it appeared in the original job description. A growing list of responsibilities is useful during a pay discussion because it shows how the job has changed, rather than relying on a general feeling that you do more than you used to.
Use the file before the annual review
Do not wait until the formal review to mention every success. Send a concise update when you finish meaningful work, especially when your manager is not close to the project. During regular meetings, ask which results would be most valuable over the next few months. Your record should help you discuss the job while there is still time to change it.
For a raise request, sort the file into three or four themes. You might choose revenue protected, customers served, time saved, and responsibilities added. Select the strongest examples and connect them to the role you are doing now. A giant list of every helpful act can bury the case. Five well-supported examples are easier to discuss than fifty fragments.
The file cannot guarantee more pay. An employer may have a frozen budget, rigid salary bands, or a manager who will not support the request. The record still gives you a clearer conversation. Ask what would justify a higher level, when the decision can be revisited, and what evidence the company uses. Write down the answer and compare it with what happens next.
Turn old entries into better résumé bullets
A résumé written from memory usually becomes a list of duties. A résumé written from a work wins file can describe proof. Choose achievements relevant to the job you want, remove confidential details, and translate internal language into words an outsider can follow. Keep the original entry in your file so you can explain the bullet naturally in an interview.
Imagine that your file says you noticed new employees kept asking the same questions, gathered the answers from three experienced coworkers, and made a one-page guide used during onboarding. A résumé bullet might say, “Created a reusable onboarding guide for five weekly procedures after gathering input from three senior teammates.” If you do not know how much training time it saved, stop there. The concrete work is already worth describing.
Read the whole file every three months. Archive entries that no longer matter, correct anything that sounds larger than it was, and notice which kinds of work keep appearing. The pattern may show that you are already doing the next job, or that months of effort have gone toward duties you do not want to carry forever. Both discoveries can shape the next conversation.
Open a blank note today and recover one useful thing you finished last week. Write the problem, your part, and the result. Then put ten minutes on Friday's calendar. The value will come from a small record kept while the truth is still easy to remember.
Unless I say they are mine, the examples are made up and rounded so the math is easier to follow. Your income, obligations, and risks will be different. This is education, not personal financial advice.
Your turn
What happened at your house?
What piece of useful work from the past month would you want to remember at your next review?
Loading the conversation…