Guide

How to keep track of what you learn and ship in your first 90 days at a new job

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

Keep a two-line daily log on paper or in a notes app, write a short Friday note for yourself, and keep a separate list of what you shipped with links. That covers most people. If you work on a Mac and your employer allows screen recording, Dayflow can add an automatic timeline of your day so gaps in your notes are easy to fill.

It is week five. Someone in a meeting asks what you have been working on, and your mind goes oddly blank. You know you have been busy. You set up your laptop, sat through a dozen intro calls, read a wiki that contradicted itself, fixed a small thing nobody asked you to fix, and learned that “the migration” means three different projects depending on who says it. None of that is written down in one place, and most of it is already going soft around the edges.

Then the 90-day check-in arrives. You are trying to rebuild two months from a calendar full of meetings and a chat history that is hard to search. The work you did is real. The record of it is thin.

This guide covers why the early weeks blur together, six small habits for keeping track of what you learn and what you ship, and how to turn them into something useful when your first review comes around. Most of it needs paper or a plain notes file. It is published by Dayflow, which makes a Mac app that comes up once, near the end.

The short version

Why does the start of a new job blur together so fast?

When everything is new, nothing stands out. In a job you know well, days have landmarks: the release on Tuesday, the client call that went sideways. In a new job every day is full of unfamiliar names and tools, so the days run together and memory has fewer hooks to hang things on.

A lot of early work also leaves no trace. Reading documentation, getting access to systems, figuring out who to ask, learning how decisions really get made: this is most of the first month for many people, and none of it produces a document or a pull request or a deck. It is easy to finish a week feeling like you did nothing when you actually did a great deal of quiet groundwork.

The visible wins are scattered. A fix lives in one tool, a helpful answer lives in a chat thread, a draft lives in someone else’s folder. Nothing gathers them up for you.

You also do not yet know what matters. In an established role, you know which work your manager cares about. In a new one, you are still guessing, so it is hard to know what is worth writing down.

And you are tired. Learning a new place takes real effort, and by six in the evening there is not much left for reflection. That is why every habit below is deliberately small. A system that needs energy you do not have will not last past week two.

Keep a two-line daily log

What to do: Before you close your laptop, write two lines. The first is one thing you did. The second is one thing you learned. Use a paper notebook, an index card, or a plain text file. Date each entry. If you can add a link to what you did, add it.

An illustration: “Tue 14 Oct. Did: fixed the broken export filter on the admin page (link). Learned: anything touching billing needs a sign-off from the finance team, even small changes.”

That is the whole habit. Resist turning it into a full journal on day one. You can always write more on a day you feel like it, but the floor is two lines. If you want a ready-made layout, the daily work log template gives you a simple page to fill in, and the guide to what a work journal is covers longer formats once the habit sticks.

How to tell after a week: Count the entries. If you have four or five, it is working. If you have one or two, the habit is too big or happening at the wrong moment. Try writing at lunch instead, or keep the notebook physically on top of your keyboard so you see it before you leave.

Build a glossary and a who-owns-what page

What to do: Start one page with two columns: the word or name, and what it means. Every time someone says an acronym, a project codename or a system name you do not recognize, write it down, even before you know the answer. Fill in the meaning later when you find out. On a second page, keep a list of areas and the person who owns or knows each one.

An illustration: “ARR: annual recurring revenue, the number leadership watches most. Nightly sync: the job that copies orders into the warehouse system. Ask Priya if it fails. Design reviews: Thursdays, need a doc posted by Wednesday noon.”

This page does two jobs. It saves you from asking the same question twice, which many new hires feel self-conscious about. And it becomes visible proof of how much you learned, which is easy to forget once the knowledge feels obvious.

How to tell after a week: Read the page from the top. If there are entries you now understand without looking, that is your learning curve on paper. If the page is nearly empty, you are probably hearing new terms and letting them pass. Keep a sticky note next to you during meetings and copy them over at the end of the day.

Write yourself a Friday note

What to do: Once a week, set a ten-minute kitchen timer and read back through your daily lines. Then write a short note to yourself with three headings: what I finished, what I learned, what is next. Keep it to a few sentences under each. When the timer goes off, stop.

An illustration: “Finished: export filter fix, first on-call shadow shift. Learned: the release process, where the real roadmap lives (not the wiki). Next: pair with Sam on the reporting bug, ask about the billing sign-off rule.”

The point is to compress five days into something you can still read in two months. Daily lines are raw. The Friday note is where patterns show up, like noticing you spent most of the week waiting on access, which is worth raising.

If your manager wants a weekly written update, this note is most of the work already. The weekly work log template fits this format well, and the guide on how to write a weekly status report covers trimming it into something for someone else to read.

How to tell after a week: You will only have one note after the first week, so look at it this way instead: could someone else read it and roughly understand your week? If yes, it is detailed enough. If it says “lots of meetings, some progress,” go back to your daily lines and pull out specifics.

What to do: Start a separate list that holds only finished things that someone else can see or use. Each line gets a date, a short description and a link. Include small things: a corrected doc page, a script that saved a teammate twenty minutes, a meeting you ran. Leave out work in progress. That belongs in your daily log.

An illustration: “Oct 9: Rewrote the onboarding checklist for new support hires (link). Oct 16: Fixed export filter (link). Oct 22: Ran my first sprint demo.”

Keeping this separate from the daily log matters. When review time comes, you want one clean list of outcomes, not a hunt through every entry. Links matter too. A month from now, “fixed a bug” is vague. A link to the actual change is specific and checkable, and it lets your manager see the work instead of taking your word for it.

How to tell after a week: Look at whether every item has a link. If several do not, ask yourself whether they were really finished, or whether the link just lives somewhere you have not found yet. An empty list in week one is normal. An empty list by week four is a signal to ask for something small you can finish.

Write down what “good at 90 days” means, in your manager’s words

What to do: In your first or second one-on-one, ask a plain question: “What would a good first 90 days look like to you?” Write down the answer as close to word for word as you can. If it is vague, ask a follow-up: “What would make you think, at the end of three months, that this hire worked out?” Then check against it about once a month.

An illustration: Your manager says, “Be able to handle tier-two tickets on your own, own the reporting dashboard, and know the team well enough to know who to ask.” You write those three lines on the first page of your notebook. At day 30, you mark each one: not started, in progress, or done.

This turns a fuzzy feeling of “am I doing okay?” into three things you can actually check. It also tells you which parts of your log and shipped list matter most at review time. The monthly status report template works well for the 30 and 60-day check-ins, and the guide on preparing for a performance review covers pulling it all together when the formal review comes.

If your manager does not have a clear answer, that is useful to know too. You can offer a draft of three goals and ask them to adjust it.

How to tell after a week: Can you name the three goals without looking? If not, put them somewhere you see every day. If something you did this week does not connect to any of them, that is fine, but notice whether most of your week did.

Save the kind words as they arrive

What to do: Make one folder, in your email or a notes file, and drop in every thank-you, every “this was really helpful,” every positive comment in a review thread. Take a screenshot or copy the text with the date and who said it. It takes a few seconds per item.

An illustration: A teammate writes, “Your checklist rewrite made my first shift so much easier.” You copy it into the folder with the date and their name, next to a link to the checklist.

New jobs come with a lot of quiet doubt, and on a hard week it helps to have something concrete to reread. At review time, a comment from a peer in their own words often says more than anything you could write about yourself. It also tells you which of your work landed with other people, which is not always the work you expected.

How to tell after a week: You may have nothing in the folder yet, and that is fine. What matters is that you would know where to put something if it arrived. If you notice yourself reading a kind message and thinking “I’ll save it later,” save it now.

Where seeing your actual day helps

Every habit above depends on remembering to do it, and some days you will not. A long day of meetings, a late fix, a Friday you leave early: the log has a hole, and you are back to rebuilding the day from memory. If that happens a lot, where did my day go covers the general problem in more detail.

Dayflow is a free, open-source Mac app that records your screen at one frame every 10 seconds and uses AI to write the day into a readable timeline. Nothing needs starting or stopping. The recordings and timeline are stored on your Mac. You can run a supported AI model locally so screenshot analysis stays on-device, connect your own cloud provider, or use the optional Pro plan at $20 a month, which handles cloud analysis for you. The local and cloud processing page explains the difference.

For a new job, the useful part is filling gaps. When your two lines are missing for Wednesday, the timeline shows what you were actually looking at. You can export a date range as Markdown from Settings and use it to draft a Friday note or a 30-day summary, as described in export your work history. The AI summaries can miss or misinterpret work, so check them before anything goes to your manager. There is more on this in how to remember what you worked on.

Dayflow publishes this article. The details here come from Dayflow’s own documentation for version 2.2.0, reviewed in September 2026.

Where Dayflow is the wrong pick

Your work computer is not a Mac. Dayflow runs on macOS 14 or later only. On Windows or Linux, or on an older Mac, a notebook and the habits above are the whole system, and they work fine.

Your employer does not allow it. This matters more at a new job than almost anywhere else. Work laptops show confidential information, and many companies restrict screen capture or software installs. Check the policy and ask IT before installing it. If you choose cloud processing, selected screenshots leave your Mac, which your employer may not permit. Starting a new role by breaking a security rule is a bad trade for a nicer timeline.

Most of your learning happens off-screen. Dayflow sees only the screen. It does not hear the hallway conversation where someone explained why the system works the way it does, or the whiteboard session where your team sketched the plan. For the learning half of your first 90 days, a paper notebook is often better.

You want guidance, not a record. Dayflow does not tell you what matters, what to learn next, or whether you are on track. Your manager, a mentor or a peer who joined a year ago will do that far better.

You need billing or team features. Dayflow has no invoicing, payroll approvals, team reports or website blocking. If your new job involves billing clients by the hour, a dedicated time tracker for Mac built for billing, or whatever tool your firm already uses, is the right choice.

Two lines a day is enough for you. If the daily log is working, you may not need anything else. That is a good outcome.

The bottom line

The first 90 days of a new job are full of real work that leaves almost no trace, and memory alone will not hold it. You do not need an elaborate system. Two lines a day, a glossary, a ten-minute Friday note and a shipped list with links will cover most of what you need for any early check-in.

Add the one conversation that makes the rest useful: ask your manager what a good first 90 days looks like, and write it down. Then save the kind words when they come, because you will want them on the harder weeks.

If you are on a Mac, your employer allows it, and you keep finding holes in your log, an automatic record of your screen can fill them in. Start with the paper, though. The habit matters more than the tool.

Frequently asked questions

What should I keep track of in my first 90 days at a new job?

Track two things separately: what you learned and what you shipped. Learning covers systems, acronyms, people and unwritten rules. Shipping covers anything finished that someone else can see, with a link. Add the goals your manager set for your first 90 days, written in their words. Those three lists give you most of what you need for a 30, 60 or 90-day check-in.

How do I remember what I did at work each day?

Write it down before you close your laptop, while it is still fresh. Two lines are enough: one thing you did and one thing you learned. Many people find a tiny habit they actually keep beats a detailed journal they abandon by week two. If you forget a day, your calendar, sent messages and recent files can help you rebuild it the next morning.

How do I prepare for a 90-day review at a new job?

Start with the goals your manager gave you early on and go through them one at a time. For each, pull matching items from your shipped list and your Friday notes. Add what you learned that will make the next quarter faster, and one or two things you want to do next. Bring links, not adjectives. A single page is usually plenty.

Should I send my manager a weekly update when I am new?

Ask them. Some managers love a short written update, others prefer to talk in one-on-ones. If they say yes, your Friday note to yourself is most of the work already. Trim it to what you finished, what you are working on next, and anything you are stuck on. Keep it short enough to read in under a minute.

Is it okay to run a screen recording app on a work laptop?

Check your employer's policy and ask IT before installing anything that records the screen. Work laptops often show confidential information, and some companies restrict screen capture. Dayflow stores its recordings and timeline on your Mac, and its local AI option keeps screenshot analysis on-device. Cloud options send selected screenshots off the Mac, which your employer may not allow.

Is Dayflow better than a paper notebook for a new job?

Often not. A notebook wins for the learning half: diagrams, half-understood acronyms, names and why things work the way they do. It also works on any computer, including Windows laptops where Dayflow cannot run, and needs no approval from IT. Dayflow is better at recording what was on your screen when you forgot to write anything down.

What should I use instead of Dayflow to track billable hours at a new consulting job?

A dedicated time tracker with client and project billing will serve you better. Dayflow does not provide invoices or payroll approvals, and its AI summaries can miss or misinterpret work, so they need checking before anything goes to a client. Ask your new firm which tool they already use. Most consultancies have one and expect you to log into it.

How long should a daily work log take?

Two to three minutes. If it takes longer, it will not survive a busy week. Write one thing you did and one thing you learned, in plain words, with a link if there is one. Save the longer reflection for a ten-minute Friday note, where you can spot patterns across five days instead of reliving one.

What if I feel like I have not accomplished anything in my first month?

That feeling is common, because much early work leaves no artifact: reading, setup, meeting people, learning where things live. Look back at your log and count the questions you can now answer that you could not on day one. That is real progress. If the gap still bothers you, ask your manager what a small, finishable task would be.

Does Dayflow cost anything?

Dayflow is free at $0 and open source under the MIT license. There is an optional Pro plan at $20 a month, which handles cloud analysis for you. Without Pro you can run a supported AI model locally on your Mac or connect your own provider, whose charges and terms apply. It runs on macOS 14 or later only.

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