Guide

How to Answer "What Have You Been Working On?"

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

Lead with one finished outcome, then what is in progress, then what is next or blocked. To have that ready, keep a two-line note at the end of each day and a ten-minute Friday roll-up, and use your calendar to fill gaps. If you work on a Mac and forget to log, Dayflow keeps an automatic timeline of your screen you can skim first, then check before sharing.

It is Thursday afternoon and your manager drops into a call a few minutes early. “So, what have you been working on?” You know you have been busy. You can feel the week’s tiredness behind your eyes. But what comes out is “Oh, lots of stuff. A bunch of meetings, the usual,” and you hear how thin it sounds.

Later, walking to the kitchen, it comes back: you fixed that awkward bug on Monday, rewrote half the onboarding doc, and spent an hour getting a new teammate unstuck. None of it was in your head when it mattered. The work was real. The answer just wasn’t ready.

This guide covers why this question goes blank so often, how to shape a good answer, and a handful of low-effort habits that make the answer easy to find. Most need only paper, a calendar or a few minutes on Friday. Near the end there is one section on Dayflow, the Mac app that publishes this blog, and one on when it is the wrong choice. Details about Dayflow come from its own documentation for version 2.2.0, reviewed in September 2026.

The short version

Why does my mind go blank when someone asks?

Part of it is how memory handles ordinary work. A day of email, small fixes, reviews and quick calls has no single memorable moment. Many people find that finished tasks fade fast, while unfinished ones stay loud. So when you reach for “what did I do,” the brain hands you the open loops and the stress, not the wins.

Part of it is that a lot of work leaves no visible trace. Talking a colleague through a problem, reading a long thread so you could make a call, untangling a confusing spreadsheet: these take real time and produce nothing you can point to. If nobody wrote it down, it is easy for you to forget it too.

Context switching makes it worse. When a day is chopped into twenty-minute pieces, each piece is too small to register on its own. You end the day with a vague sense of motion and no clear storyline. If that sounds familiar, where did my day go walks through that feeling in more detail.

Finally, the question itself is fuzzy. A manager in a hallway wants a quick pulse. A standup wants something the group can act on. A performance review wants a pattern over months. Answering all three from the same blank memory is hard. It gets much easier once you know which version you are being asked for and have a few notes to draw on.

None of this means you are disorganized or not working hard. It means the work did not get captured in a form you can retrieve under a bit of pressure. That is fixable.

1. Use a three-beat answer every time

What to do: Give your answer the same shape every time: one outcome you finished, one thing in progress, and what is next or blocked. Lead with the finished thing, because it is the most useful and the easiest to forget. Keep each beat to a sentence.

Illustration: “I finished the pricing page copy and it’s with design now. I’m partway through the data cleanup for the Q4 report, about halfway. Next is the customer interview notes, but I’m waiting on access to the recordings from Priya.”

That took about fifteen seconds and gave the listener three concrete things, including a blocker they might be able to clear.

How to tell after a week: Notice whether people ask fewer follow-up questions like “and where’s that at?” Also notice whether you feel less of a scramble when someone asks. If you still freeze, the shape is fine but you need material, which the next habits supply.

2. Write two lines at the end of each day

What to do: Before you close the laptop, write two lines on paper, in a notes file or wherever you will see them again. Line one: what moved today. Line two: what is next tomorrow. That is it. Not a diary, not a reflection, just two lines. A daily work log template can make this feel less like a blank page.

Illustration: “Moved: fixed date bug in invoices, reviewed Alex’s PR, decided to drop the CSV import from v1. Next: start migration script, reply to legal about data terms.”

How to tell after a week: On Friday, read the five entries. If they let you answer “what did you do this week” without opening anything else, it is working. If you skipped days, move the habit to a moment that already exists, such as right after your last meeting or when you pack up. A sticky note on the laptop lid helps some people.

If you want to go further than two lines, a work journal is the longer version of the same idea.

3. Keep a list of the work nobody sees

What to do: Keep a separate short list, a page in your notebook or a pinned note, for the work that does not show up in tickets or deliverables. Reviews you did. People you helped. Decisions you made or pushed for. Problems you caught early. Add to it the moment it happens, in a few words.

Illustration: A week’s list might read: “Paired with new hire on test setup (1 hr). Caught wrong tax rate before launch. Pushed for dropping the second signup step. Covered support inbox Wednesday.”

How to tell after a week: Look at the list on Friday. If it has three or more entries that would not have appeared anywhere else, it is earning its place. Many people find this list is where the most persuasive material for reviews ends up, because it shows judgment and helpfulness that a task list never captures.

4. Do a ten-minute Friday roll-up

What to do: Every Friday, set a kitchen timer for ten minutes. Read your daily lines and your invisible-work list, then write a short summary: three to five outcomes, what is in progress, and anything blocked. Save these somewhere you can find them in three months. A weekly status report template gives you a ready structure, and how to write a weekly status report covers the craft in more depth.

Illustration: “Week of Oct 5. Done: pricing page copy, invoice date bug, dropped CSV import from v1 scope. In progress: Q4 data cleanup, about halfway. Blocked: interview recordings access. Also: onboarded new hire on test setup.”

How to tell after a week: You will know after the first one. If you can send it to your manager unedited, or paste it into a one-on-one doc, it is working. After a month, check whether you have four of them saved. That stack is what turns a quarterly review from dread into editing.

If you are curious where the week’s hours went in broad strokes, the where does my week go calculator is a quick way to sketch it alongside your roll-up.

5. Rebuild from the trails you already leave

What to do: On weeks when you did not keep notes, do not guess. Open your calendar and walk through each day in order. Then look at your sent messages, recently edited documents, closed tickets and, if you write code, your commits. These are timestamps of your attention. Write one line per block of time as you go.

Illustration: Tuesday’s calendar shows a 10 a.m. design review and a 2 p.m. vendor call. Sent mail shows a long reply about contract terms at 4 p.m. The document history shows you edited the launch checklist that morning. Now Tuesday reads: “Design review, launch checklist updates, vendor call, contract terms reply.” That took two minutes.

How to tell after a week: Time how long it takes to reconstruct one week this way. If it is under fifteen minutes and you trust the result, it is a solid backup. If you find big stretches with no trail at all, usually deep focus work or messy context switching, that is a sign the daily two lines would help more than any reconstruction.

6. Prepare the long answer before you need it

What to do: For the bigger versions of the question, such as a skip-level meeting, a promotion conversation or an annual review, prepare in advance. Pull your Friday roll-ups, group the outcomes into three to five themes, and write one concrete example under each. Practice saying the short version of each theme out loud once. How to prepare for a performance review goes step by step.

Illustration: Themes might be “Made launches calmer,” “Brought on two new teammates,” and “Cut scope where it mattered.” Under the first: “Built the launch checklist that caught the tax rate error before the September release.”

How to tell after a week: Ask a friend or partner to play the manager and ask, “What have you been working on this quarter?” If you can answer for a minute without notes and without saying “um, lots of stuff,” you are ready. If you stall on a theme, it needs a sharper example.

7. Have an honest answer for the slow weeks

What to do: Some weeks really do produce little. Do not pad. Say what took the time, what you learned, and what changes next. Write this version down in your roll-up too, because a pattern of slow weeks with the same cause is useful information to bring to your manager.

Illustration: “Not much shipped this week. Most of it went to the outage on Tuesday and then untangling unclear requirements on the import feature. I’ve written up the open questions and I’m meeting product Monday to settle them, so next week should move.”

How to tell after a week: Notice how the conversation goes. Honest, specific answers with a next step usually lead to help or a reprioritization, not judgment. If you find yourself dreading the question every week, look at your roll-ups for a repeating cause and raise it directly.

Where seeing your actual day helps

Every habit above depends on you remembering to write something down. On busy or scattered days, that is exactly what slips, and the answer falls back on memory, which is the weakest source. An automatic record of what was on your screen means you do not have to start a timer or reconstruct the day afterward. There is more on this in remembering what you worked on.

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. Full recordings and the timeline are stored on your Mac. You choose how screenshots are analyzed: local AI keeps analysis on-device, your own cloud provider processes selected screenshots under its own terms, or Dayflow Pro at $20 a month manages cloud analysis. Under the privacy policy, Pro deletes screenshots after processing and may retain activity data for sync. Local and cloud processing explains the options, and pricing lists the plans.

For this question, the useful part is export: you can export a date range as Markdown from Settings → Export and read it before writing your Friday roll-up. AI summaries can miss or misinterpret work, so treat the timeline as a memory aid and check outcomes before sharing anything.

Dayflow publishes this article, so weigh that when reading this section.

Where Dayflow is the wrong pick

If you would rather track time with manual timers or by project, this guide to Mac time trackers covers tools that take a different approach.

The bottom line

“What have you been working on?” is hard because ordinary work is easy to forget, not because you did not do enough. Give your answer a fixed shape: finished, in progress, next. Then make sure the material exists. Two lines a day, a short list of invisible work and ten minutes on Friday cover most weeks, and your calendar fills the gaps. If you are on a Mac and keep forgetting to write things down, an automatic timeline can give you a draft to check. Either way, the next time someone asks, you will have something specific to say.

Frequently asked questions

How do I answer "what have you been working on?" in a standup?

Use three short beats: one thing you finished, one thing in progress, and what is next or blocked. Keep it under a minute and name outcomes rather than activities, so "merged the export fix" instead of "worked on bugs." If something is blocked, say who or what could unblock it. That gives the group something to act on, which is the point of a standup.

What should I say if I haven't done much this week?

Say what actually happened, plainly. Name what took the time, such as an unexpected outage, unclear requirements or a pile of reviews, then what you learned and what changes next week. A short, honest answer with a plan reads far better than a padded list. If the same thing keeps eating your weeks, raising it early gives your manager a chance to help.

How do I remember what I worked on last week?

Start with the trails you already leave: your calendar, sent messages, edited documents, closed tickets and any code commits. Walk through each day in order and jot one line per block. Going forward, a two-line note at the end of each day removes most of the guesswork, because reading five short notes on Friday is much easier than rebuilding a week from memory.

How long should my answer be when a manager asks in passing?

About thirty seconds. Give the single most important outcome, one thing in progress, and offer more detail if they want it. A hallway or chat question is usually a check-in, not a request for a full report. If they want the long version, they will ask, and you can follow up in writing with the details.

Should I mention meetings and helping teammates when I answer?

Yes, when they led to something. Helping a teammate ship, reviewing a design or making a decision in a meeting is real work that often goes unseen. Describe the result, not the hours: "helped Sam unblock the billing migration" says more than "lots of meetings." Keep a small list of these through the week, since they are the easiest things to forget.

What is the difference between a work log and a to-do list?

A to-do list looks forward at what you plan to do. A work log looks back at what you actually did, including unplanned work, decisions and help you gave. When someone asks what you have been working on, the log is the useful one, because plans and reality drift apart. Many people keep both, with the log taking only a minute or two a day.

Is Dayflow the right tool if I use Windows or need to submit timesheets?

No. Dayflow runs only on macOS 14 or later, so on Windows or Linux a simple written log works better. If your employer needs hours entered for payroll approval or client invoices, the timesheet system your company already uses is the right tool, since Dayflow does not provide invoices, payroll approvals or team reports. Dayflow is a personal record, not a billing system.

Does Dayflow send my screen recordings to the cloud?

Full screen recordings and the timeline are stored on your Mac. With local AI, screenshot analysis stays on-device. If you choose your own cloud provider or Dayflow Pro, selected screenshots are processed off-device. Under Dayflow's privacy policy, Pro deletes screenshots after processing and may keep activity data for sync. Your own provider has its own terms.

Can AI write my status update for me?

It can draft one, but you should not send it unchecked. AI summaries of your activity can miss work or misread what you were doing, and they cannot know which outcomes matter to your team. Use any automatic summary as a memory aid, then rewrite the update yourself around results, progress and next steps. Your judgment about what matters is the part nobody else can supply.

How do I prepare for "what have you worked on this quarter" in a review?

Gather your weekly notes, calendar and finished work, then group them into three to five themes. For each theme, write the outcome, why it mattered and one concrete example. Add work that helped others and anything you learned. This is far easier if you have kept short weekly roll-ups, because you are summarizing notes instead of trying to recall three months at once.

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