Your first one on one with a new employee

The first 1-1 with a new hire is the meeting managers most often waste. Mine used to be a forty minute monologue about team structure, roadmap, and how we do code review, which is information that exists in documents and which nobody retains on day three anyway.

What the first meeting is actually for is setting the working contract between two people. How we will talk, how often, what I need from them, what they need from me, and what is safe to say out loud. Everything else can wait a week.

What the first 1-1 is not for

It is not the place for feedback of any depth, because there is nothing to give feedback on yet. It is not an onboarding checklist review, that belongs in a doc with their buddy. It is not the moment to explain your management philosophy at length. I once spent twenty minutes on mine with a new senior engineer and I could see him waiting for me to finish so he could ask where the staging credentials were.

Thirty minutes is enough. If it runs to forty five because they are talking, that is fine. If it runs to forty five because I am talking, something has gone wrong.

What to cover

Four areas, in roughly this order. Together they take about twenty five minutes if I keep myself in check.

How they like to receive feedback. Immediately or later, verbally or in writing, direct or wrapped. This sounds like a small logistical detail and it is one of the highest value things you can learn in week one. Sofia told me in her first 1-1 that public praise made her uncomfortable and that she would rather hear good things privately. I would have got that wrong for six months otherwise, and it would have read as me not noticing her.

What their previous manager did that worked, and what did not. People answer this honestly more often than you expect, and it is the closest thing to a manual for working with them. The complaints are the useful half. When someone tells you their last manager only spoke to them when something was wrong, you have just been handed a specific thing to avoid.

What worries them about the new role. Everybody has something. Unfamiliar stack, a domain they have never touched, being the only person in their timezone, being more senior than they feel. Asking directly in week one gives them permission to say it before it has hardened into something they are hiding.

Practical logistics. Working hours and timezone overlap, when they prefer meetings, how they want to be reached for something urgent versus something that can wait, and any fixed commitments in their week. Two minutes here prevents a lot of small friction later.

Ten questions for the first meeting

I do not ask all ten. I pick six or seven depending on how the conversation moves, and I keep the rest for week two.

• How do you like to get feedback, and how quickly after the thing itself.
• What did your last manager do that you would want me to keep doing.
• What did your last manager do that you hope I will not do.
• What are you most unsure about in this role right now.
• What does a good week look like for you.
• How do you prefer to be reached when something is urgent.
• What kind of work do you want more of over the next year.
• Is there anything about how you work that people usually misread at first.
• What would make the first month here feel like a success to you.
• What do you need from me in the next two weeks specifically.

That last question is the one I never skip. It turns an abstract meeting into two or three concrete things I owe them by the middle of the month, which is the fastest way to show them what I am like as a manager.

What not to do

Do not interrogate. Ten questions asked in sequence with no room between them is an interview, and they already had one of those to get here. Ask one, listen, follow the thread wherever it goes, and drop the rest if the conversation is better than your list.

Do not oversell the company. New hires arrive with a fairly clear picture from the interviews, and a first 1-1 spent on how special the culture is sets an expectation you will have to correct in month two. I would rather say plainly that our test suite is slow, our on call is heavier than I would like, and here is what we are doing about both.

Do not promise things outside your control. Promotion timelines, headcount, a specific project six months out, remote policy. The temptation is strong because you want them to feel good about the choice they made. A promise you cannot keep costs far more in month five than an honest I do not know costs on day three.

And do not take notes so intensely that the meeting turns into a transcript. I write three lines after the meeting, not during it.

Weeks two, three, and four

The first month has a shape. Trust does not appear because you were friendly once, it accumulates from a small number of predictable interactions.

Week two is about first impressions of the work. What has surprised them, what is confusing in the codebase, whether the onboarding docs are lying anywhere. New people can see things the rest of us stopped seeing a year ago, and that clarity lasts about a month before they normalise too. I ask what looks strange here that everyone else seems fine with, and I write the answers down.

Week three is usually where the first real friction shows up. A review that felt harsh, a meeting where nobody explained the context, a piece of work that turned out bigger than described. This is the week to ask how the first three weeks compare to what they expected, because the gap between expectation and reality is at its widest and they are still willing to say so.

Week four is the first checkpoint. I ask what is working, what is not, and whether they have what they need. This is also the earliest point where light feedback from me is useful, and it should be small and specific rather than a verdict.

Across all four weeks, the thing I care about most is whether they are bringing me problems unprompted by the end of the month. If they are, the contract is working. If everything is still fine, I have not made it safe enough yet.

Week one is the context you will need in month three

Everything a new person tells you in the first month is exactly the material you will need much later, and it is also the material you are least likely to remember, because in week one you have no hooks to hang it on.

A concrete example. In his first 1-1 in March, Daniel mentioned that in his previous job he had been moved off a project he cared about with no explanation and that it was the reason he left. In June we reshuffled teams. Because that line was written down and in front of me, I spent ten minutes explaining the reasoning to him before the announcement and asked what he wanted next. It cost almost nothing and it was the difference between a change he understood and the exact pattern that had made him quit somewhere else.

I only had that line because I wrote it down on day three, and these days LeaderCues is what surfaces those old notes back to me before the meeting where they matter, without me having to remember that they exist.

For the questions I use once the first month is over, there is one on one meeting questions that get people talking. For the ongoing practice, cadence, preparation, and follow through, see how to run one on one meetings.

Thirty minutes, six questions, and three lines written down afterwards. That is the whole first meeting, and it will still be paying you back a year later.