Your First 1:1 with a New Employee: Script and Questions

When to schedule it (and how long)

Book it for day one or day two. Not the end of week one, not "once they've settled in." A new hire's anxiety peaks in the first 48 hours — that's when a calm, personal conversation with their manager does the most good. If you wait a week, they've already formed a story about what kind of manager you are, and you didn't get a vote.

Make it 45 minutes, not 30. The first meeting carries more weight than a normal one, and you don't want to cut off the get-to-know-you part to squeeze in logistics. Every 1:1 after this can drop to your regular cadence and length — if you're not sure what that should be, here's how to think about one-on-one meeting frequency. For a new hire, start weekly. Non-negotiable for at least the first 90 days.

The opening script, nearly word for word

Most managers wing the opening and end up rambling about the org chart. Don't. The first two minutes should do exactly three things: lower the stakes, define what 1:1s are for, and hand them ownership of the meeting. Here's a script you can use almost verbatim:

"Before we get into anything work-related, I want to explain what this meeting is, because we'll have it every week and it's probably the most important recurring thing on both our calendars. This is your meeting, not mine. It's not a status update — I can get status from standups and tickets. This is time for whatever's on your mind: things that are confusing, things that are blocking you, feedback for me, career stuff, or just thinking out loud. You'll own the agenda. Some weeks you'll have a lot, some weeks less, and both are fine. My only ask is that you never sit on a problem until it's big. Bring me the small weird stuff early — that's literally what I'm for."

Then add the trust line, which matters more than anything else you'll say: "For the record: in your first few months, questions are free. There is no question too basic. Around here, asking early is a sign of competence, not weakness. The only thing that worries me is silence."

That's it. Ninety seconds. Then you shift to questions — and you spend the rest of the meeting mostly listening.

Questions that build trust in meeting one

Your goal in the first meeting is not information transfer — it's demonstrating that you're genuinely curious about them as a person and a professional. Pick 4-5 of these; don't run all of them like an interrogation:

• "What made you say yes to this job? What are you hoping is true about it?" — tells you their expectations so you can manage them early.
• "Think about the best manager you've ever had. What did they do that worked for you?" — this is them handing you the instruction manual for managing them.
• "And the flip side — what has a past manager done that drove you crazy?" — people answer this one with surprising honesty, and it's gold.
• "How do you like to receive feedback — in the moment, written, in private?" — sets up every future feedback conversation.
• "When you get stuck on something, what do you tend to do?" — tells you whether they're a silent struggler or an early asker, so you know what to watch for.
• "What's something you're good at that might not be obvious from your resume?" — a genuinely fun question that surfaces hidden skills.
• "Outside of work, what's important to you that I should know about?" — asked openly, with zero pressure to share. Some people mention kids, sports, side projects; some don't. Both fine.

Write their answers down. Not because it looks attentive (though it does), but because you'll need them. "Prefers written feedback before verbal" is the kind of detail that pays off for years — and it belongs in your one-on-one meeting notes, not in your memory.

The user manual exchange

The trust-building move most managers skip: go first. Before you ask your new hire how they work, tell them how you work. It's disarming, it models vulnerability, and it saves them weeks of guessing.

Cover four things about yourself, in about three minutes:

• How to reach you. "Slack me anytime; if it's urgent, call. I batch email twice a day, so don't use it for anything time-sensitive."
• Your quirks, honestly. "I think out loud in meetings — if I muse about an idea, that's not a directive. If I actually want you to do something, I'll say so explicitly and put it in writing."
• What worries you. "The only thing that genuinely stresses me is finding out about a problem late. Bad news early is always welcome news."
• How you'll give them feedback. "You'll hear small course-corrections from me often and casually — that's normal and doesn't mean you're in trouble. Anything serious, we'll discuss properly in a 1:1, never by surprise."

Then invite theirs: "Over the next week, think about your version of this — how you work best, what drains you, what your ideal week looks like. We'll compare notes next 1:1." Giving them a week to reflect gets you a far better answer than putting them on the spot in meeting one.

Frame the first 90 days out loud

New hires quietly torture themselves with one question: "Am I ramping fast enough?" You can defuse most of that anxiety in two minutes by saying your expectations out loud. Most managers have a 30/60/90 picture in their head and never share it. Share it.

• First 30 days: absorb. "Success this month is learning — meeting people, understanding how we work, asking lots of questions. I do not expect meaningful output. If you ship something small, that's a bonus, not the bar."
• Days 30-60: contribute with support. "You'll start owning real tasks, with training wheels. Expect to lean on the team constantly — that's the design, not a failure."
• Days 60-90: own something. "By the end of month three, you'll fully own at least one meaningful piece of work end to end. That's when we'll sit down and do a proper ramp-up review together."

Two caveats. First, adjust the timeline to the role — a senior director hire and a junior IC ramp very differently, and pretending otherwise helps no one. Second, be explicit that this framing is about calibration, not evaluation: "This isn't a test you can fail in week two. It's so you always know where the bar is and never have to guess."

What NOT to cover in the first meeting

Restraint is half the skill here. Three things stay off the table:

• Performance goals and OKRs. They have zero context yet. Setting goals in week one produces either sandbagged goals or panic. Wait until week three or four, when they can actually negotiate them intelligently.
• Team gossip and history. Don't brief them on who's difficult, past drama, or "things to watch out for" with specific people. It poisons relationships before they've formed, and it teaches your new hire that you talk about people behind their backs — which means you probably talk about them too.
• Long-term career planning. Asking "where do you see yourself in five years?" on day one gets you a rehearsed interview answer, not the truth. Plant the seed — "in a couple of months, once you're settled, I'd love to talk about where you want to grow" — and have the real conversation later. When you get there, here's how to run career development conversations properly.

Also resist the urge to fill silence with your own talking. A good first 1:1 is roughly 70% them talking, 30% you. If you catch yourself monologuing about the company strategy, stop and ask a question.

A 45-minute agenda you can steal

Putting it all together:

1. Minutes 0-2: The opening script — what 1:1s are, who owns them, questions are free.
2. Minutes 2-20: Get-to-know-you questions. Listen, take notes, follow curiosity instead of the list.
3. Minutes 20-27: Your user manual — how you communicate, your quirks, how feedback from you works. Assign theirs as homework.
4. Minutes 27-35: The 30/60/90 framing, said out loud, with the "calibration not evaluation" caveat.
5. Minutes 35-42: Their questions. Ask twice — "what else?" reliably surfaces the real one they were sitting on.
6. Minutes 42-45: One action item each, confirm next week's meeting, done.

After this first meeting, your weekly 1:1s shift to a normal rhythm — their agenda, your questions, running notes. If you want the fuller picture of what that steady-state meeting looks like, start with how to run a one-on-one meeting and keep a bank of good questions handy for the weeks when their agenda is thin. A tool like Teammons keeps the running agenda and those first-meeting notes in one place, so "prefers written feedback" doesn't vanish into a notebook you'll never reopen.