How to learn everyone's name at a new job

Everyone at your new job knows your name. There was an announcement. There was possibly a cake. Meanwhile you are three weeks in, greeting half the team with "hey — you!" and rerouting to the far kitchen to avoid the tall man from finance whose name you've now been too embarrassed to ask about for eighteen days.

This is the most solvable name problem there is, for one reason: it has a deadline and a finite list. You aren't trying to remember everyone you'll ever meet. You're trying to remember roughly forty specific people whose names are, conveniently, written down somewhere.

The politeness window is real, and it's about two weeks

Here's the rule nobody tells you on day one.

For roughly the first two weeks — three if you're lucky, or if the company is large — asking someone's name is completely free. It is expected. "Sorry, remind me of your name?" costs you nothing, because the whole organisation has silently agreed that the new person cannot possibly have learnt forty names yet.

After that, the same question quietly changes meaning. At week five it stops being "I'm new" and starts being "you were not memorable to me."

So the biggest mistake new starters make is politeness. You don't ask in week one because you don't want to seem like you weren't listening, and then you spend eight months conducting an elaborate avoidance operation around a man called Dave.

Ask early, ask often, ask shamelessly. Week one is the cheapest that question will ever be. Spend it.

Get the list before you need it

You have an advantage almost no other name situation offers: somewhere in this company there is a document with everyone's face and name on it.

Go and find it in your first few days:

• The intranet directory or team page. Faces and names, usually with job titles — exactly the meaningful hook that names lack on their own.
• The org chart. Better still, because it gives you structure: names attached to teams attached to a shape you can picture.
• The internal chat tool. Channel member lists are effectively a photo directory sorted by who works together.
• Meeting invites. A recurring meeting's attendee list is a pre-filtered list of the people you most need to know.
• The seating plan, if one exists. If it doesn't, draw one.

Screenshot the lot. This is the whole reason a new job is easier than a party: you get the answer sheet in advance.

Draw the seating map yourself

If you're in an office, this is the highest-value twenty minutes of your first week.

Sketch the floor — desks as boxes — and write names in as you learn them. Location is a powerful memory cue: your memory is far better at where than at what. "The Marcus by the window" is much stickier than "Marcus."

It also exposes what you don't know. Fifteen filled boxes and six empty ones is a to-do list telling you exactly who to ask about while asking is free.

For hybrid teams the equivalent is the video-call grid — same trick, and you start remembering people by their position and background.

Learn in batches, by team

Don't learn the company alphabetically, or in the order you bump into people. Learn one team at a time.

Batching gives you a second hook alongside the name. You're not learning "Priya" in isolation, you're learning "Priya, logistics, sits with Marcus and Sam, the three of them do the Wednesday stand-up." The team is a container, and containers make things easier to find. Nail your immediate team first, then the teams you work with, then the wider floor. Faces you see daily will half-learn themselves.

A useful side effect: people are far easier to remember once you know what they do, because a job is meaningful in a way a name isn't. "Kwame — he's the one who owns the deployment pipeline" is a name with a handle on it.

Two people with the same name

Every workplace has two Sarahs and, at some point, three men with beards. One of the hardest parts, and worth handling deliberately rather than hoping.

Learn them together, not separately. Trying to learn Sarah-in-finance while pretending Sarah-in-design doesn't exist is how you end up confidently calling both the wrong thing. Put them side by side and find the difference: Sarah C has the Yorkshire accent, Sarah M has the dog under her desk.

Attach the distinguishing feature to the name, not the person. "Finance Sarah" is a phrase you can retrieve under pressure. "The other Sarah" is not.

Don't practise them back to back. Keep similar names apart when you test yourself. Two Sarahs in a row teaches you the confusion rather than the names.

And if you can't tell them apart yet, don't guess. A wrong guess is far more memorable to them than a friendly "sorry, I'm doing terribly with the two Sarahs — which one am I talking to?" in week one.

Use the name the first four times you see them

Learning the name in the directory is only half of it. It has to survive contact with the actual person.

So the first few times you pass Marcus in the corridor, say "morning, Marcus" rather than "morning." It does two jobs: it drags the name out of memory under real conditions, which is the effort that makes it stick, and it lets you find out early if you've got it wrong — while that's still free.

If nothing comes when you reach for it, that's useful information. Put them at the top of tonight's list.

Do a five-minute pass each evening for the first fortnight

At the end of each day, go through your list and try to recall each name from the face before you check. That effortful reach usually supports longer retention better than reading the directory again; recognising and retrieving are not the same task.

Then keep coming back to the shaky ones over the following days and weeks, with the gaps getting longer as they get stronger. This is spaced repetition, and it's why five focused minutes a night for a fortnight comfortably beats an hour staring at the org chart on Sunday. Full plain-English explanation in spaced repetition, explained without the jargon.

The individual techniques — hooks, visual links, asking about a name properly — are in 7 techniques that actually work.

A realistic two-week plan

• Days 1–2: Screenshot the team page and org chart. Sketch the seating map. Learn your immediate team, ten people maximum.
• Days 3–5: Ask everyone you interact with, while it's free. Add a note for each: team, what they do, one detail from the conversation.
• Week 2: Widen to adjacent teams. Sort out your duplicate names. Use names out loud in the corridor.
• Ongoing: A short recall pass most evenings, with longer gaps as names get solid.

By week three you're the new person who somehow already knows everyone — a disproportionate amount of goodwill for the effort involved.

The shortcut

This is the situation Namefinity was built for, because the inputs are already digital.

Screenshot the team page and the app reads the names and faces out of it for you. Drop in a group photo from the offsite and tap each face to keep it as its own person. Or pull people straight in from contacts. Add a note — team, desk, what they do — and you've built your floor in about ten minutes.

Then the daily practice is around two minutes: a face appears, you reach for the name, tap to reveal, and say how it went. The five memory boxes tell you where everyone stands — brand new, shaky, getting there, solid, locked in — so before Thursday's stand-up you can see who needs a quick refresh.

To be clear about what it does and doesn't do: it finds where a face is in a photo so it can crop a tidy picture. It never works out who anyone is — there's no face recognition. And your colleagues' photos and your notes stay on your iPhone. No account, no cloud, no ads, free; export a readable copy of your names and notes whenever you like — which matters more than usual when the notes are about people you work with.

Now go and ask the tall man from finance. You've still got a few days.