Is 1on1 System Worth It for New Manager at Google? ROI Analysis

The 1on1 system is not a nice-to-have ritual; it is the single highest-leverage activity a new Google manager can execute to secure team retention and delivery velocity within the first 90 days.

In the L6 promotion debriefs I have sat through, the difference between a “promotable” and a “strong no” often hinged on one specific artifact: the documented history of meaningful 1on1s that drove measurable outcome changes. New managers at Google frequently misinterpret their role as technical leads who happen to have reports, believing their value lies in code reviews and architecture diagrams. This is a fatal error. The organizational psychology principle at play here is the “transformational leadership gap,” where individual contributors fail to shift their identity from doer to multiplier. The problem isn’t your technical depth; it’s your failure to build the psychological safety required for your team to innovate without you. At Google, where the average engineering tenure is scrutinized and attrition costs roughly $250,000 per mid-level engineer in lost productivity and recruiting fees, skipping structured 1on1s is financial negligence. You are not building a relationship; you are building an insurance policy against project failure.

Does the 1on1 System Actually Improve Retention for New Google Managers?

Yes, structured 1on1s directly correlate with retention because they surface disengagement signals three to six months before an employee submits their resignation, allowing for timely intervention.

I recall a Q3 calibration meeting where a hiring manager defended a high-performing team lead who had lost two senior engineers in six months. The director stopped the presentation and asked to see the 1on1 notes from the preceding year. The manager produced calendars showing thirty-minute blocks, but the notes were empty or limited to “status update.” The director’s verdict was immediate: “You managed tasks, not people.” The counter-intuitive truth here is that high performers do not leave because of workload; they leave because of a lack of growth visibility, which is only uncovered in deep, unscripted 1on1 conversations. When a new Google manager treats 1on1s as status meetings, they signal that the human element is secondary to the Jira ticket. This creates a transactional environment where loyalty is non-existent.

The ROI calculation is stark. Replacing a L5 software engineer at Google involves a recruiting process averaging 45 days, a signing bonus often ranging from $40,000 to $60,000, and a ramp-up period of six months where productivity is at 50%. In contrast, a 30-minute weekly 1on1 costs only 26 hours of manager time per year. If that time prevents a single regrettable attrition, the return on investment exceeds 1000%. The mechanism is not magic; it is data collection. In a well-run 1on1, a manager asks, “What is the one thing blocking you that I can remove?” rather than “What did you finish yesterday?” The former uncovers systemic friction; the latter just updates a dashboard. Most new managers fear the silence in these meetings, but that silence is where the real work happens. If you are talking for more than 20% of the time, you are failing. The goal is not to impart wisdom; it is to extract obstacles.

How Do 1on1s Impact Delivery Velocity and Project Outcomes at Google?

Regular 1on1s accelerate delivery velocity by identifying cross-functional blockers and resource gaps weeks before they become critical path delays in the launch timeline.

During a critical infrastructure migration project last year, the engineering VP halted a team’s progress not because of code quality, but because the manager had no record of discussing resource constraints with their reports in monthly 1on1s. The team was burning out, silently hiding the fact that they were waiting on security review approvals for three weeks. A manager who holds effective 1on1s acts as a radar system for the organization. The insight layer here is “blocker latency”: the time between a problem existing and the manager knowing about it. In teams with ad-hoc communication, this latency can be weeks; in teams with rigorous 1on1s, it is days. At Google, where projects often span multiple orgs like Cloud, Search, and Ads, the complexity of dependencies is the primary killer of velocity.

Consider the mathematics of a delayed launch. A two-week slip in a major feature release can cost a product group millions in projected revenue or market share. If a manager discovers a dependency risk during a Tuesday 1on1 instead of the Friday status meeting, they gain four days of mitigation time. That four-day window is often the difference between making a quarterly goal and missing it. The “not X, but Y” dynamic is crucial: 1on1s are not for reporting what happened; they are for negotiating what will happen. A new manager who uses this time to micromanage task completion slows the team down by creating a bottleneck at their own desk. Conversely, a manager who uses the time to clear political hurdles or secure budget for tools empowers the team to move faster. The script is simple: “If you could change one process this week to move 20% faster, what would it be?” The answer to that question is your roadmap for the week.

What Is the Actual Time Cost Versus Career ROI for L3 to L5 Managers?

The time cost of 1on1s is approximately 10% of a new manager’s weekly capacity, but the career ROI manifests as eligibility for L6 promotion within 18 to 24 months versus stagnation.

In the promotion committee for the E3 cycle, I reviewed a packet for a manager who had delivered a technically flawless project but had zero documentation of developing their direct reports. The committee rejected the packet instantly. The rationale was explicit: “We promote leaders who build other leaders, not heroes who carry the team.” The harsh reality for new managers at Google is that your individual contribution is now irrelevant to your evaluation; your output is strictly the output of your team. If your team is stagnant, you are stagnant. The 1on1 system is the primary vehicle for demonstrating that you are developing talent. Without it, you are merely a senior individual contributor with a fancy title.

Let’s break down the time allocation. A manager with six direct reports spends roughly three hours a week in 1on1s, plus two hours for preparation and follow-up. This is five hours, or just over 10% of a 45-hour work week. The return on this investment is the accumulation of “leadership capital.” When promotion season arrives, you do not scramble to find examples of your leadership; you have a year’s worth of documented coaching moments, conflict resolutions, and growth plans extracted directly from those meetings. The counter-intuitive observation is that spending less time in meetings and more time in focused 1on1 preparation yields higher promotional velocity. Many new managers try to “save time” by canceling 1on1s during crunch time. This is a catastrophic signal to the organization that you cannot handle pressure without sacrificing your team’s well-being. It marks you as a tactical firefighter, not a strategic leader. The script for a busy week is not to cancel, but to shorten: “We have 15 minutes today to focus purely on your biggest blocker. Let’s make it count.” This preserves the rhythm while respecting the crisis.

Can 1on1 Data Replace Intuition in Performance Reviews and Calibrations?

Yes, aggregated 1on1 data replaces subjective intuition with objective evidence, shielding both the manager and the employee from bias during calibration cycles.

I witnessed a calibration session where a manager argued for a “Exceeds Expectations” rating for an engineer based on “gut feel” and recent visibility. The director asked for specific instances of feedback given and received over the last two quarters. The manager stumbled, relying on vague recollections of hallway chats. The rating was downgraded to “Meets Expectations” because the lack of documented dialogue suggested the feedback was not actionable or consistent. The principle at work is “recency bias mitigation.” Human memory is flawed and favors the last two weeks of performance. A structured 1on1 system creates a longitudinal dataset that prevents the entire year’s performance from being judged on the final sprint. At Google, where calibration committees are notoriously rigorous and skeptical of unsupported claims, anecdotal evidence is worthless.

The value proposition extends beyond defense; it enables precision. When you have notes from twenty-four 1on1s, you can identify patterns. Perhaps an engineer consistently struggles with ambiguity in the first week of a project but excels once requirements are clear. This is a coaching insight you cannot get from a quarterly survey. You can address it in real-time. The “not X, but Y” distinction is vital here: 1on1s are not for storing grievances; they are for tracking growth trajectories. A manager who brings a spreadsheet of goals and progress markers to a calibration commands the room. A manager who says, “I think they are doing great,” gets eaten alive. The script for the review conversation is direct: “In our session on March 12th, we agreed you would lead the design doc. You delivered it two days early, which matches our goal of increasing ownership. Let’s discuss how to scale that.” This level of specificity builds trust and clarity, removing the anxiety of the unknown for the employee.

Preparation Checklist

Define the Agenda Protocol: Establish a rule that the direct report owns 70% of the agenda, focusing on their blockers and growth, while you reserve 30% for organizational context and feedback.
Implement a Shared Document System: Create a persistent, shared doc for each report where talking points are added 24 hours in advance; this forces reflection and prevents the “what’s up?” void.
Master the “Silence” Technique: Prepare three open-ended questions (e.g., “What is the hardest part of your week?”) and practice waiting ten seconds after asking them to force deeper disclosure.
Review Previous Action Items: Start every session by reviewing commitments made in the last meeting; failing to follow up destroys credibility faster than any technical mistake.
Align on Career Trajectory: Dedicate one 1on1 per month exclusively to long-term career mapping, separate from immediate project work, to ensure retention alignment.
Study Structured Coaching Frameworks: Work through a structured preparation system (the PM Interview Playbook covers specific feedback models and career mapping frameworks with real debrief examples) to ensure your conversations drive measurable behavioral change rather than just venting.
Audit Your Talk Ratio: Record yourself (with permission) or self-monitor to ensure you are speaking less than 20% of the time; if you are lecturing, you are not managing.

Mistakes to Avoid

Mistake 1: Treating 1on1s as Status Updates BAD: The manager spends 25 minutes asking “Is the API done?” and “When will the test pass?” while taking notes on Jira tickets. GOOD: The manager asks “What is preventing the API from being done?” and “Who do you need help from to unblock the test?” focusing on removal of obstacles. Verdict: Status updates can be emails; 1on1s must be for problems that cannot be solved asynchronously.

Mistake 2: Canceling During “Crunch Time” BAD: The manager sends a calendar invite cancellation during launch week saying “Too busy, let’s sync next month.” GOOD: The manager keeps the slot but changes the title to “Emergency Blocker Buster” and focuses strictly on immediate triage and stress management. Verdict: Canceling signals that the employee’s well-being is expendable, which permanently damages trust and increases attrition risk post-launch.

Mistake 3: Lack of Follow-Through on Commitments BAD: The employee requests a specific training budget or introduction to another team, and the manager says “I’ll look into it,” but never mentions it again. GOOD: The manager adds the request to the shared doc immediately, sets a reminder for 48 hours, and provides a definitive yes/no/update in the next session. Verdict: Unfulfilled promises in 1on1s are interpreted as a lack of care or competence, eroding the manager’s authority faster than technical ignorance.

FAQ

Q: How often should a new Google manager hold 1on1s with senior engineers? Hold them weekly for the first 90 days to establish rhythm, then move to bi-weekly only if the senior engineer explicitly requests it and demonstrates high autonomy. Never drop below bi-weekly, as even senior staff require consistent alignment on shifting organizational priorities. The frequency signals priority; reducing it too soon signals disinterest.

Q: What if my direct report refuses to share an agenda or talk deeply? Stop trying to fill the silence and explicitly state the dynamic: “This time is for your agenda. If you have nothing, we can end early so you can get back to work.” This boundary forces them to realize the value of the space. Eventually, the discomfort of unused time will drive them to prepare topics that matter to their career.

Q: Should 1on1 notes be shared with the employee or kept private? Always use a shared document for action items and goals, but keep your private coaching observations and sensitive feedback notes in a separate, private file. Transparency on commitments builds trust, while privacy on sensitive assessments protects the integrity of future performance reviews and calibration discussions.amazon.com/dp/B0GWWJQ2S3).