Two things are true in your first month and false forever after.
You can see what is confusing. In three months the acronyms will be invisible to you, the strange deployment process will feel normal, and you will have lost the ability to notice any of it. That perception is a genuinely scarce asset, and it evaporates on a schedule.
And you are allowed not to know. The window where "sorry, what does that stand for?" costs you nothing is real and it closes.
Notes in a new job should be built around both facts.
Four files, started on day one
Keep these separate. Merging them is why most onboarding notes turn into an unreadable chronological blob.
| File | Contents | Lifespan |
|---|---|---|
| Glossary | Acronyms, internal product names, team names, systems | Forever, and it becomes a gift to the next hire |
| People | Who does what, who to ask about what, who reports where | Ongoing |
| How things actually work | The real process, not the documented one | Ongoing |
| Confusions | Everything you did not understand, dated | Weeks 1–8, then it converts |
The glossary is the one people skip and later wish they had. Every organisation has forty terms that mean nothing outside it, and you will meet most of them in the first fortnight, each mentioned once, in passing.
The confusions file is the valuable one
Write down every single thing you do not understand, immediately, without judging whether it matters. Why does this team have two standups. What is "the migration" everyone refers to. Why does nobody use the tool we pay for.
Two reasons this beats simply asking:
You cannot ask forty questions in a meeting. But you can ask five of them at your next one-to-one if you have a list. Without the list you will remember two and misremember one.
It is a record of the onboarding experience that will not exist in a month. This is the raw material for improving onboarding for the next person, and you are the only one who can produce it. It is a direct antidote to the curse of knowledge, which is why documentation written by long-tenured people is so often useless.
Then convert it. Around week six, turn the answered confusions into a short onboarding document and hand it to your manager. It costs you an hour, it demonstrably improves things, and it is one of the highest-return visible contributions available that early. See note-taking for teams.
Capture in meetings you do not understand
Early meetings are largely incomprehensible, which changes what you should write.
Do not try to summarise the discussion. You lack the context to know what mattered, and the attempt will produce pages of nothing. Instead capture:
- Names of people, systems, and projects, exactly as spoken, even if you have no idea what they are.
- Decisions, marked as decisions, even without understanding them.
- Anything said with unusual emphasis, which is a reliable signal of what is politically or technically load-bearing.
- Your questions, in a distinct column or bracket.
Fragments are correct here. Speed matters and comprehension will arrive later. See bullet points vs full sentences and how to take meeting notes once you can follow along.
The written and unwritten process
Every organisation has a documented process and an actual one, and the gap between them is most of what "being onboarded" means.
Record both, separately and without editorialising. "Docs say file a ticket. In practice everyone messages Dan." That note is useful immediately, and it is also the most valuable thing you could show someone trying to fix the process. Do not write it in a tone you would mind being read.
Notes on people, carefully
You will form impressions fast, and they will be substantially wrong. Early impressions of colleagues are formed with no context about their constraints, history, or workload.
Keep a people file for structural facts: who owns what, who to ask, what they care about, what they are responsible for. That is genuinely useful and improves for years.
Be much more careful with judgements. They are unreliable this early, they are not private in any meaningful legal sense, and they are hard to revise once written down. If you record an impression, date it and mark it as an impression, so that later you can see how wrong you were, which is itself informative.
The 30-day snapshot
At the end of your first month, write one page you will not look at again for a long time: what surprised you, what seems broken, what seems unusually good, what you would change.
Then diarise it for six months out. By then you will have adapted to the things that surprised you and will no longer believe you ever found them strange. That page is the only evidence you will have of what an outsider saw, and it is disproportionately useful when you are eventually the one onboarding someone else.
Keep it yours
Your personal notes should live somewhere you control and are comfortable being candid in, distinct from anything shared. That is not secrecy, it is the condition for writing honestly, and honest early notes are the whole point.
Be aware of the other direction too: notes on a work device or work account are generally your employer's, and confidential material should not leave their systems. Keep the judgement calls in a personal space and the company's information in the company's.
More in how to take notes as a manager, how to take 1:1 notes, and how to keep a work journal.