Workflow
How to Remember People at a New Job
Starting a new job means dozens of names in week one. A system to remember colleagues, their roles, and who does what — fast.
To remember people at a new job, capture three things for each person within a day of meeting them: their name, what they own, and one human detail — then review the list at the end of week one. Doing this turns a blur of introductions into a working map of the team before anyone expects you to know it.
The first weeks are the hardest moment of your career to remember people, because you meet the most names while having the least context to hang them on. A light, deliberate system beats a good memory here.
1. Sketch the org as you meet people
Don’t wait for an org chart. Start drawing your own from the first introduction. Each time you meet someone, note where they sit relative to your work: your team, an adjacent team, leadership, or a function you’ll depend on (IT, finance, ops).
You’re building a rough map of who connects to what. The point isn’t an accurate hierarchy — it’s a memory aid. A name attached to a position in your mental diagram sticks far better than a name floating alone. If you like seeing the connections, the ideas in how to organize the people you know translate directly to a new-team setting.
2. Capture a role plus one human fact
Right after a meeting or hallway intro, jot the name, the role, and exactly one personal detail you heard. The human fact is what makes the second conversation warm instead of robotic.
Met Tomás on the platform team today. Owns the deployment pipeline — the person to ask before any release. Just moved back from the Lisbon office, has a toddler, supports Sporting. Said to ping him directly, not the team channel.
That single note means your next exchange with Tomás can open with something real, not “remind me what you do again?” The discipline of writing a role next to the name is the same one covered in how to remember people’s names — pairing the name with meaning is what makes it stick.
3. Note who actually owns what
In week one, the most valuable thing to record isn’t titles — it’s ownership. Who do you go to for access? Who unblocks budget? Who knows why the codebase is shaped the way it is? Titles tell you reporting lines; ownership tells you how work really gets done.
Keep a simple running table as you learn it:
| Person | Official role | What they actually own | Go to them for |
|---|---|---|---|
| Tomás | Senior engineer | Release pipeline | Anything shipping to prod |
| Aisha | Office manager | Vendors, facilities, the “real” calendar | Logistics, who-knows-who |
| Devon | Eng manager | Roadmap priorities | What’s worth working on |
| Priyanka | Finance partner | Team budget | Spend approvals |
This table becomes your fastest reference when you’re stuck and don’t yet know who to ask.
4. Learn the informal map, not just the formal one
Every organization has a hierarchy on paper and a different one in practice. The person who quietly makes decisions isn’t always the one with the senior title. The colleague everyone trusts for context may be three levels down.
Watch for the informal signals in your first weeks:
- Whose name comes up when something needs to actually get done?
- Who do senior people check with before deciding?
- Who has been there long enough to know the history?
- Who connects different teams socially?
Add these observations to your notes as you spot them. Knowing the informal map early is what separates a fast start from a slow one.
5. Review everyone at the end of week one
On Friday of week one, spend ten minutes reading back through every person you captured. Say the names. Re-read the human details. Fill the gaps — the people whose roles you still can’t place go on a short list to clarify next week.
This single review is the highest-leverage habit in the whole system, because it converts a week of fragmented introductions into durable memory while the encounters are still fresh. Repeating a light version weekly for the first month locks it in. The broader version of this practice is laid out in how to remember everyone you meet, which applies well beyond onboarding.
Key takeaway: Remembering a new team isn’t about a great memory — it’s about capturing a role and one human detail per person, mapping who owns what, and reviewing once before the week ends.
A note on doing this discreetly
You don’t need to take notes while someone is mid-sentence introducing themselves. Capture afterward — in the two minutes after a meeting, on a walk back to your desk, or by speaking a quick voice note. New colleagues never see the system; they only experience you remembering their name and their kid’s name a week later, which reads as attentiveness, not surveillance.
A tool like Intriq is built for exactly this: you save quick notes about each colleague, typed or spoken, and it organizes them into searchable, person-by-person memory you can pull up before your next one-on-one. Its AI works only from what you’ve actually saved, so a quick “what does Devon own again?” returns your own note, not a guess. See how it fits onboarding and beyond in relationship memory.
FAQ
How many names should I expect to learn in my first week?
At most new jobs you’ll be introduced to twenty to fifty people in week one, but you only need to firmly remember your immediate team and the handful of people you’ll depend on. Capture everyone lightly; commit the core dozen to memory first.
Is it weird to take notes about coworkers?
Not if you do it privately and afterward, not in front of them. Jotting “Tomás owns releases, just moved from Lisbon” is no different from any professional keeping track of their work — it helps you show up informed, which colleagues read as respect.
What if I forget someone’s name after we’ve already met?
Re-introduce yourself by name first (“Hi, I’m Sam from the data team”) — it gives them an easy opening to offer theirs back without anyone feeling awkward. Then capture it immediately so it doesn’t happen twice.