New Manager at Google: First 1on1 with Direct Report Template

New Manager at Google: First 1on1 with Direct Report Template

TL;DR

The first 1:1 at Google is not a relationship-building exercise. It is a test of whether you can create clarity, safety, and cadence in 30 minutes.

If the direct report leaves without a shared view of priorities, blockers, and next steps, the meeting failed even if it felt pleasant. After a 4-round interview loop, people often overestimate their leadership readiness; the first 1:1 exposes whether they can run an operating system, not just sound polished.

Use the meeting to establish a contract: what matters, how you work, and when you will check in again. Not warmth first, but structure first.

Who This Is For

This is for a new manager at Google who inherited a direct report after a reorg, moved from IC to manager, or arrived as the external hire whose credibility is still untested. It is also for leaders who know they should not improvise the first 1:1, but are tempted to because they think empathy can replace structure.

If you are in the first 7 to 14 days of the transition, this template matters more than your onboarding deck. The first meeting decides whether your direct report sees you as a manager with judgment or just another person with a title.

What should the first 1:1 actually accomplish?

The first 1:1 should create an operating contract, not a rapport performance.

In a Q3 manager debrief, I watched a new lead spend 20 minutes on background and 10 on generic encouragement. The direct report stayed polite, then started escalating basic decisions through the skip manager because nothing in the first meeting made authority, priorities, or escalation paths legible. That is the failure mode: not conflict, but ambiguity.

The judgment signal is simple. The direct report should leave knowing what matters this month, what kind of manager you are, and what kind of help they can expect from you. Not “we had a nice chat,” but “I know how to work with this person.”

This is why the first meeting is not mainly about trust. It is about trust testing. People do not trust the manager who says the right words. They trust the manager whose behavior is predictable after the meeting ends.

The most common mistake is to treat the first 1:1 like a coffee chat. That is not a relationship strategy. That is avoidance dressed up as friendliness.

What should I ask in the first meeting?

Ask about current work, friction, and preferences. Do not start with biography questions that produce rehearsed answers.

In a calibration conversation, I once heard a manager ask, “Tell me about yourself.” The room knew immediately that the manager wanted tone, not truth. The better managers ask for the operational facts first, because operational facts reveal judgment faster than polished self-description.

Use questions that expose risk and working style:

• What are your top 3 priorities over the next 30 days?
• What is most likely to block you this week?
• What is one thing I should not change immediately on the team?
• How do you prefer feedback: live, written, or after reflection?
• What should I know about how you like to make decisions?
• What would success look like after 30 days in this role?

The point is not to collect answers. The point is to see where the real work is hidden. Not “where do you want to be in five years,” but “what do you need from me this week.”

If the direct report is senior, ask them where the org is underestimating the work. If they are junior, ask where they feel most exposed. Senior people often hide risk behind competence. Junior people often hide uncertainty behind politeness. The questions should pull the truth out of both.

How much should I say about myself?

Say enough to make your judgment legible, not enough to make the meeting about you.

A new manager often tries to buy credibility through autobiography. That rarely works. In a reorg, I watched one manager explain their entire career path and leadership philosophy in the first 1:1. The direct report did not need the origin story. They needed to know whether the manager would respond quickly to blockers, how disagreements would be handled, and what decisions could be made without waiting for permission.

This is the organizational psychology most people miss. Predictability lowers anxiety more than charisma does. When people know how you decide, how fast you respond, and what you escalate, they can spend less energy guessing and more energy delivering.

Share four things and stop there:

• How you make decisions.
• How you want issues surfaced.
• What you will decide fast.
• What you will not pretend to know yet.

Not “here is my life story,” but “here is my management contract.” Not “I want transparency,” but “here is what I will share, and when.” That distinction matters because teams do not fail from lack of warmth. They fail from uncertainty about how work moves.

What does the template and timing look like?

A good first 1:1 template is short, timed, and specific.

Use 30 minutes if the relationship is neutral and the role is straightforward. Use 45 minutes only if there is tension, a reorg, or a complex scope. A full hour is usually too much unless the team is deeply misaligned, because long meetings invite vague talk and false intimacy.

A practical first-meeting structure looks like this:

• 5 minutes: purpose, tone, and what the meeting is for.
• 10 minutes: their current priorities and blockers.
• 10 minutes: your working style, decision rights, and expectations.
• 5 minutes: recap, immediate actions, and next meeting time.

If the relationship is already strained, cut the icebreaker and keep the agenda visible. The mistake is thinking formality makes you cold. It does not. It makes you clear.

In a debrief after an onboarding gone wrong, the strongest manager had not been the most charismatic one. It was the one who wrote the agenda before the meeting, used the agenda during the meeting, and sent a clean follow-up after the meeting. The difference was not personality. It was discipline.

The first three 1:1s should produce a rhythm, not a friendship arc. That is the real standard. Not “did they like me,” but “did we establish a repeatable way to work.”

What should happen after the meeting ends?

The follow-up is the real test, because memory fades faster than intent.

Send a recap within 24 hours. Keep it short. Include what you heard, what you will do, and what you need from them before the next meeting. If you promised a decision or an introduction, attach a date to it. Vague intent is the same as no commitment.

A strong follow-up note has three parts:

• What I heard from you.
• What I will do.
• What we will revisit next time.

Set the next 1:1 before the current one ends, and keep it within 7 days. If there is a blocked issue, decide within 48 hours whether you can remove it, delegate it, or escalate it. Waiting turns leadership into theater.

In skip-level conversations, direct reports rarely remember the clever thing their manager said in the first meeting. They remember the manager who followed through with names, dates, and decisions. Reliability compounds. Performative warmth does not.

This is the final judgment. Not a conversation, but a signal. Not a vibe, but a system.

Preparation Checklist

Preparation should be built around clarity, not performance.

• Write down the three outcomes you need from the first 1:1: priorities, support needs, and working cadence.
• Draft 5 questions in advance, and delete any that sound like therapy disguised as management.
• Decide what you can commit to in the first 7 days, and what you cannot.
• Prepare a 5-sentence follow-up note before the meeting starts.
• Schedule the next 1:1 before you leave the room.
• Review current team goals, active projects, and any public docs the direct report relies on.
• Work through a structured preparation system (the PM Interview Playbook covers first-30-day manager calibration and feedback questions with real debrief examples).

Preparation is not about sounding polished. It is about reducing the chance that the direct report learns you are improvising.

Mistakes to Avoid

The common failure is not awkwardness. It is weak judgment.

1. BAD: Turning the meeting into your biography.

GOOD: Explaining how you make decisions and what you expect from them.

1. BAD: Asking “How are things going?”

GOOD: Asking “What is blocked, what is fragile, and what should I not change yet?”

1. BAD: Ending with “Let’s stay in touch.”

GOOD: Ending with a dated follow-up, a short recap, and a named next step.

The pattern is consistent. Not vague warmth, but visible decisions. Not a pleasant conversation, but a usable working relationship.

FAQ

1. Should the first 1:1 be formal?

Yes. Formal enough to create clarity, informal enough to let the person speak honestly. If the meeting feels like a status sync, it is too cold. If it feels like a coffee chat with no structure, it is too soft.

1. How long should the first 1:1 be?

Thirty minutes is the default. Forty-five minutes is for tension, complexity, or a major transition. Sixty minutes usually signals that the manager does not know what the meeting is for.

1. What if the direct report is skeptical of me?

Do not try to win them with enthusiasm. State the operating contract, ask for their view of the work, and deliver one small promise within 7 days. Skepticism is usually cured by consistency, not charisma.

---

Ready to build a real interview prep system?

Get the full PM Interview Prep System →

The book is also available on Amazon Kindle.