Guide

How to show impact as an engineer when your work is hard to see

Updated November 2026 · by Jerry Liu, Dayflow's founder

Write down what changed, not only what you did. Keep a five-line daily log on paper or in a text file, turn finished work into before-and-after statements, name invisible work like reviews and incidents, and send your manager a short weekly note. If you keep forgetting to log on a Mac, Dayflow can show what was on your screen so you can fill the gaps.

It’s review season and you open the self-assessment form. The first box says “Describe your impact.” You remember the launch. You don’t remember the three weeks before it, when you chased a flaky test across two services, rewrote the deploy script so nobody had to babysit it again, and spent most afternoons answering the new hire’s questions.

Meanwhile a teammate who demoed one feature gets thanked at the all-hands. Nobody did anything wrong. Work that prevents fires leaves no smoke, and work that helps other people ship shows up under their names, not yours.

This guide covers why that happens, six habits that make your work easier to see (most need only a notebook or a text file), where an automatic record of your day can help, and where it can’t. Dayflow, which publishes this guide, comes up once near the end.

The short version

Why does good engineering work go unnoticed?

A few things happen at once, and none of them are about effort.

Prevention has no event. When you fix the thing that would have caused an outage, the outage never happens. There is nothing to point at, only an ordinary quiet week.

Credit follows the demo. Visible features have a moment: a launch post, a screenshot, a thank-you thread. Infrastructure, refactors, test fixes and tooling make other people faster without anyone seeing who did them.

Your manager sees your work through tools. They see merged pull requests, closed tickets and calendar invites. They don’t see the two hours you spent reading logs, or the call where you talked a teammate out of a bad schema.

Memory favors the recent and the dramatic. Many people find that by Friday, Monday is already blurry. By the end of a review cycle, most of what you did has been flattened into “worked on the platform.”

Engineers tend to describe activity, not change. “Refactored the auth module” is accurate, but it doesn’t tell a reader why anyone should care. The outcome is in your head, and nobody else can see it.

Glue work doesn’t fit in a ticket. Code review, on-call, mentoring, writing the doc everyone links to and running the planning meeting all keep the team working. They rarely have a ticket number, so they rarely get counted.

None of this means you need to self-promote harder. It means the record is missing, and you are the person best placed to write it.

What should you write down each day?

Keep a tiny daily log. Use paper, a text file, or a note pinned to your desktop. At the end of the day, before you close the laptop, write three to five lines:

Keep it short so you’ll actually do it. Write it the way you’d text a friend, not the way you’d write a design doc. If you want a structure to start from, the daily work log template has one, and the guide to work journals goes deeper on formats.

Illustration: “Tues. Tracked the flaky checkout test to a shared fixture leaking state. Fix in review. Paired 40 min with Sam on his first migration. Surprise: staging DB is two versions behind prod.”

After a week: count how many days have an entry. If it’s four or five, the habit is working. If it’s one, the log is too long or too late in the day. Cut it to two lines, or move it to right after your last meeting.

How do you turn tasks into impact?

A task says what you did. Impact says what is different now. The easiest way to get from one to the other is a before-and-after sentence:

Before: what was true, and who it bothered. After: what is true now. How: one line on what you did.

Use comparisons you can check yourself: steps in a process, minutes a build takes on your machine, how often a question comes up in chat. If you’re estimating, say “roughly.” Never round up to sound bigger. A modest result stated plainly is more credible than an inflated one. If you removed or shortened a recurring meeting, the meeting cost calculator gives a rough figure for the time it used to take.

Illustration: “Before: releases needed one engineer watching the deploy for about an hour, and it was usually whoever was on call. After: the deploy retries the known failure on its own and pings only if the retry fails. How: rewrote the deploy script’s health check.”

After a week: look at your daily log and try to write one before-and-after sentence for each finished item. If you can’t, that’s useful to know. You may not know the outcome yet, and you can ask whoever requested the work.

What counts as invisible work?

Make a short list of the work you do that doesn’t produce a ticket, and start writing it down by name. Common examples for engineers:

You don’t need to treat every review as a win. Just stop leaving these out. When they take a real share of your week, say so. “About half my week went to the incident and its follow-ups” is useful for a manager to hear, because it explains why the planned work moved.

Illustration: a log line that used to read “slow week” becomes “Reviewed four PRs on the billing rewrite, caught a double-charge path in one. Wrote the runbook for the queue backlog alert after Tuesday’s page.”

After a week: reread your log. If at least one non-ticket item shows up most days, you’re capturing it. If your log is all tickets, that probably doesn’t mean you did no glue work. It means you’re still filtering it out.

How often should your manager hear from you?

Send a short written note at the end of every week. Five to ten lines, in the same shape every time:

  1. What changed this week (before-and-after where you can)
  2. Invisible work worth knowing about
  3. What’s next
  4. Anything blocked or at risk

A repeated format is easier to write and easier to read. Your manager can skim it in under a minute, and over time it becomes a record they can point to when someone asks what you’ve been doing. The weekly status report template and the guide on how to write a weekly status report both work for this. If you already give daily standups, your Friday note can just roll those up.

Illustration: “Changed: checkout test is no longer flaky (was failing about one run in five on my branch). Also: onboarded Sam, his first migration is merged. Next: staging DB upgrade. Risk: upgrade needs a maintenance window, haven’t got one yet.”

After a week: did you send it? Did your manager reply, or bring anything from it up in your one-on-one? A reply of any kind means it’s being read. If there’s silence for three weeks, ask directly whether the format is useful or whether they’d rather have something else.

What goes in a review evidence file?

Keep one file, separate from your daily log, that only collects things worth mentioning at review time. Each entry gets:

Move items in from your daily log or weekly note when they finish, not months later. Once a month, read it from the top and group entries into themes (“made releases boring,” “helped two new engineers ramp up”). Those themes become your self-review headings. When review season comes, the guide on preparing for a performance review walks through turning the file into a write-up, and the monthly status report template works as a monthly checkpoint.

Illustration: “Mar 14. Before: new services took about a day to wire into monitoring. After: a template repo does it in one PR. Links: PR, the doc, Priya’s message saying her team used it twice. Worked with: platform team.”

After a week: the file should have zero to two entries. That’s normal. The test is whether you added one the day something finished, or whether you’re already planning to “catch up later.” Catching up later is usually how the file ends up empty.

Can someone else tell your story better?

Once a month, explain one piece of your recent work to someone outside your team: a friend, a peer in another org, a partner over dinner. Give it two minutes. Then ask them to say back what you did and why it mattered.

What they repeat back is roughly what a skip-level manager or a promotion committee will take from your write-up. If they say “you fixed some tests,” your story is still about activity. If they say “you made it so releases don’t need a babysitter,” you’ve got it. This takes no software, just a conversation.

It also works in reverse. Offer to do the same for a teammate. People are often better at seeing the impact in someone else’s work than in their own, and a peer who understands your work is more likely to mention it when it counts.

Illustration: you explain the deploy script rewrite to a friend who works in sales. They ask “so what happened before?” That question tells you the “before” part was missing from your explanation.

After a week: if you had the conversation, write down the one sentence they repeated back. Compare it to your evidence file. If their version is clearer than yours, use theirs.

Where seeing your actual day helps

Every habit above has the same weak spot: you have to remember to do it. On a heavy week the log stops on Tuesday, and by Friday you’re piecing the week together from commit messages and a vague sense of where your day went. If that’s the part that keeps failing, an automatic record can fill the gap.

Dayflow is a free, MIT-licensed Mac app for macOS 14 or later. It records the screen at one frame every 10 seconds and has AI write the day into a readable timeline. Recordings and the timeline are stored on your Mac. You choose how analysis runs: local AI through Ollama or LM Studio keeps screenshot analysis on-device, your own cloud provider receives selected screenshots under its own terms, or the optional Pro plan at $20 a month manages cloud analysis. Under the privacy policy, Pro deletes screenshots after processing and may retain Activity Data for sync. The local and cloud processing page has the details. You can export a date range as Markdown from Settings → Export (see exporting your work history) and use it as raw material for a weekly note.

Treat it as a memory aid, not a writer. AI summaries can miss or misinterpret work, so check anything before it reaches your manager.

Dayflow publishes this article. The Dayflow details here come from its documentation for version 2.2.0, reviewed on 2026-09-06.

Where Dayflow is the wrong pick

You aren’t on a Mac. Dayflow is Mac only and needs macOS 14 or later. A text file does the job on any machine.

Your work happens off-screen. It sees only the screen. Whiteboard sessions, hallway conversations, phone calls and the walk where you figured out the bug don’t appear. That off-screen time is often where the most important work happens, so you still need to write it down.

You need the why, not the what. A timeline can show you spent Wednesday in the deploy script. It can’t tell anyone that this meant releases stopped needing a babysitter. Writing the impact is still your job.

Your employer doesn’t allow screen recording. Many companies restrict what can run on work machines. Check your policy first. The paper habits above don’t need anyone’s permission.

Your manager wants a team dashboard. Dayflow has no team reports. It’s a personal record, and your team’s issue tracker is the better shared source.

You bill clients by the hour. Dayflow has no invoicing or payroll approvals. A dedicated time tracker for Mac built for billing fits better.

You’ll actually keep the paper log. If the daily habit sticks, you don’t need software at all.

The bottom line

Engineering work goes unnoticed because good outcomes look like quiet weeks, and the people deciding your review weren’t there. You can fix that without becoming a self-promoter. Write a few lines a day, turn finished work into before and after, name the glue work, send a short Friday note, and keep one evidence file with links. Start with the daily log tonight. If remembering is where it breaks down, an automatic record can help with the details, but the story about why the work mattered still has to come from you.

Frequently asked questions

How do I show impact as a software engineer if I mostly fix bugs?

Describe the bug from the user's or the team's side. Say what was going wrong, who it affected, and what is true now that it is fixed. Group related fixes into one story, such as "checkout errors on slow networks", instead of listing ticket numbers. A run of small fixes that made one area reliable is a clear result once you name the area and the change.

What is a brag document for engineers?

A brag document is a running file of your work and its effects, kept all year so you are not rebuilding it from memory at review time. Each entry has a date, what you did, why it mattered, and where the evidence lives, such as a pull request, a design doc or a thank-you message. It is private notes, not a public boast, and you pull from it when writing a self-review.

How do I quantify impact when I don't have metrics?

Use counts and comparisons you can check yourself. How many steps did a process have before and after? How long did a build take on your machine before and after the change? How many people stopped asking the same question once you wrote the doc? Plain before-and-after statements are honest and specific. Do not invent numbers, and say "roughly" when you are estimating.

Should I tell my manager about code reviews and mentoring?

Yes. Code review, onboarding help, incident response and answering questions are real work, and they rarely show up in the places managers look. Mention them briefly in your weekly note with an outcome where you can, such as "paired with the new hire until her first change merged". If a large share of your week goes to this kind of work, say so directly so it can be counted.

How often should I update my manager on my work?

Weekly works for most engineers. A short written note at the end of the week, with what changed, what is next, and anything blocked, gives your manager a record they can point to later. Daily standups cover coordination but are easy to forget. A monthly summary on top of weekly notes helps when your manager has to explain your work to people who do not see it.

How do I remember what I worked on for my performance review?

Write it down as you go. A few lines at the end of each day, collected into a weekly summary, gives you a year of material by review time. If you missed that, rebuild from your merged pull requests, closed tickets, calendar, sent messages and design docs, then write one paragraph per project. Start with the outcome of each project and add the supporting details afterward.

Is it bragging to write down my accomplishments?

No. Writing down what you did and what changed is record keeping. Your manager has many people to track and cannot see most of your day, so a clear written account helps them represent your work fairly. Keep it factual: what was true before, what you did, what is true now. Facts stated plainly read as useful information, not self-promotion.

Can Dayflow write my self-review for me?

No, and it should not. Dayflow records your screen at one frame every 10 seconds and has AI write a timeline of your day, which can remind you what you spent time on. It cannot tell you why the work mattered, and AI summaries can miss or misinterpret work. Use an exported timeline as raw notes, then write the review yourself and check every claim.

Is Dayflow better than my team's issue tracker for showing impact?

Usually not. Your team's issue tracker and code history are the better record of shipped outcomes, because they show what was planned, what merged, and who reviewed it, and your manager already trusts them. Dayflow shows where your screen time went, which helps with the unplanned work that never got a ticket. Lead with the tracker and use a screen timeline only to fill gaps.

Does Dayflow work on Windows or Linux?

No. Dayflow is a Mac app that needs macOS 14 or later. If you work on Windows or Linux, a plain text file or paper notebook for a daily work log will serve you better than any Mac app. The habits that make engineering work visible, like writing before-and-after statements and sending a weekly note, do not depend on software at all.

See where your day actually went

Dayflow is $0 and open source. Full recordings stay on your Mac, with local AI available for on-device analysis.

Download for MacOS macOS 14+ · MIT licensed · no account required