1on1不翻车速查表 vs Google 1on1 Framework for New Managers
TL;DR
1on1不翻车速查表 is the emergency brake; Google 1on1 Framework is the operating system. A new manager who treats them as the same thing will either sound polished and learn nothing, or learn a lot and still lose the team.
In the first 30 to 90 days, use the速查表 to avoid obvious failure: missed blockers, vague follow-up, and meetings that turn into project theater. Use Google's framework to run 1:1s as a coaching loop, not a status ritual.
The judgment is simple. Not every 1:1 needs depth, but every 1:1 needs a reason to exist.
Running effective 1:1s is a system, not a talent. The Resume Starter Templates includes agenda templates and question banks for every scenario.
Who This Is For
This is for the first-time manager who just inherited 4 to 8 direct reports, has a weekly 30-minute slot, and is already feeling the friction between keeping delivery moving and not sounding managerial by accident.
It also fits the IC-turned-manager who still thinks a good meeting is one where everyone leaves “aligned.” That instinct fails fast. A strong 1:1 is not about alignment theater. It is about surfacing risk, making decisions visible, and teaching people how you think.
If you are already managing a stable team with a mature cadence, this will feel less like a rescue kit and more like a calibration tool. That is the right frame. The problem is not that you need more meetings. The problem is that you need fewer empty ones.
Which one should a new manager use first?
Use 1on1不翻车速查表 first, then graduate to Google's framework once the room stops feeling fragile.
In the first month, a new manager is usually not missing sophistication. They are missing control of the basics: who owns the agenda, what counts as a real blocker, and when to stop talking. The速查表 is useful because it prevents the most expensive beginner mistake, which is treating a 1:1 like a polite project update.
I have seen this in manager debriefs. A new EM came in from staff engineering and ran every 1:1 like a technical sync. By week three, one engineer had not mentioned a promotion concern, another had silently absorbed a dependency risk, and the skip manager was surprised in staff review. The meeting was not broken because it lacked content. It was broken because it lacked judgment.
Google's framework matters after that. The official re:Work material frames manager work around outcomes, people development, and community building, with coaching and performance conversations sitting at the center (Google re:Work). That is the real difference. Not a script, but a system. Not a checklist, but a standard.
The speed sheet helps you survive the first 2 weeks. The framework tells you what kind of manager you are trying to become by day 90.
> 📖 Related: google-vs-amazon-PM-interview-2026
Why do most first 1on1s fail?
Most first 1:1s fail because managers confuse comfort with trust.
In a Q3 debrief, a director told me the new manager “has great rapport.” The next question was why the team kept missing handoffs. The answer was obvious. The 1:1s were warm, but nobody was being challenged. Rapport without friction is just social maintenance. It feels safe and produces nothing.
This is where the psychology matters. People do not disclose risk because a manager is friendly. They disclose risk when the manager proves that truth will change something. That means the meeting has to carry consequence. If a person can leave a 1:1 unchanged, the manager has not done the job.
Not a therapy session, but a decision surface. Not a status review, but a control loop. Not advice-giving, but calibration. Those distinctions matter because managers often try to be liked before they try to be useful.
The failure mode is predictable. New managers over-index on open-ended questions, then wander into silence. Senior managers over-index on speed, then turn the meeting into a blur of decisions with no coaching. Both are wrong for the same reason. They are optimizing for the manager's comfort, not the employee's clarity.
What does Google's framework actually reward?
Google's framework rewards managers who create clarity, not just atmosphere.
The re:Work material is blunt about this. Good managers coach, set expectations, communicate well, support growth, and create a team environment that can sustain performance. That is not romantic language. It is a demand for behavior that can be observed in a 1:1 and later defended in a review.
A new manager often misreads this as “be supportive.” That is too vague. Supportive can mean listening. It can also mean avoiding hard feedback. Google-style management is closer to disciplined care. You notice the problem early. You say what matters. You help the person move.
In practice, that means your 1:1 is not about covering every topic. It is about testing whether the person understands the work, the constraints, and the growth edge. If they only bring updates, the manager has not created a coaching environment. If they only bring complaints, the manager has not created enough structure to turn pain into action.
Not more empathy, but more precision. Not more talking, but better questions. Not more positive tone, but more usable signal. That is the part most candidates and new managers miss when they read a framework and think they have understood it.
> 📖 Related: [](https://sirjohnnymai.com/blog/google-vs-nvidia-pm-role-comparison-2026)
What should you ask in a 30-minute 1on1?
You should ask fewer questions, but each one should force a real tradeoff.
A 30-minute 1:1 is not a long conversation. It is a compressed diagnostic. If you burn 10 minutes on pleasantries and 15 on project status, you have built a status meeting with a nicer name. The right structure is simple: blockers first, decisions second, growth third, feedback last.
In the first 10 minutes, ask what is stuck, what is uncertain, and what will break if nothing changes. In the next 10, ask what decision they need from you and what decision they are avoiding. In the last 10, ask what skill gap, behavior gap, or relationship gap is limiting them this month. That is enough.
The counterintuitive part is that the junior the employee, the more structure they need. Senior people do not need fewer guardrails because they are senior. They need more room to surface judgment. They already know how to fill silence. They need a manager who can distinguish noise from a real concern.
If you ask only “How are things going?” you will get polite weather reports. If you ask “What are you not saying because it feels premature?” you get the real meeting.
How do you know the meeting is working?
The meeting is working when next week starts cleaner than this week.
That is the only metric that matters early on. Not satisfaction. Not friendliness. Not whether both people felt heard. The test is whether blockers surfaced earlier, decisions got made faster, and the employee left with more clarity than they entered with.
In one leadership review, a hiring manager described a new manager as “very responsive.” The team still kept missing deliverables. The problem was not responsiveness. The manager had become a collector of problems instead of a setter of direction. The 1:1s were full of motion, but nothing actually changed between meetings.
By day 30, you should know each person's current motivator, current risk, and current career tension. By day 60, you should have given at least one piece of feedback that changed behavior. By day 90, you should have either changed a recurring failure pattern or made peace with the fact that the person is in the wrong seat.
Not busier, but clearer. Not warmer, but more honest. Not more frequent, but more continuous. If three meetings pass and nothing new ever surfaces, your 1:1 is ceremonial.
Preparation Checklist
Start with the basics, then build the management muscle.
- Set a fixed 30-minute weekly cadence for each direct report. If the meeting moves every week, the message is that it is optional.
- Ask the employee to own the agenda, but keep the first two topics under your control: blockers and decisions. Ownership without structure becomes drift.
- Write one coaching question before every meeting. If you arrive empty, you will default to status collection.
- Track recurring themes across 4 to 6 weeks. One-off issues are noise. Repeat issues are management work.
- Keep a short follow-up log with decisions, dates, and owners. Memory is not a system.
- Work through a structured preparation system (the PM Interview Playbook covers coaching loops and debrief-style judgment examples that map cleanly to first-time manager 1:1s).
- Revisit the 30/60/90-day transition. The first month is about trust, the second about pattern recognition, the third about intervention.
Mistakes to Avoid
The common errors are boring, which is why they survive.
- Mistake: turning the 1:1 into project status.
BAD: “Walk me through everything on the roadmap.”
GOOD: “What is blocked, what is at risk, and what decision do you need from me?”
- Mistake: using the meeting to sound supportive without making a call.
BAD: “That sounds hard. Let’s keep an eye on it.”
GOOD: “This is the real issue. Here is what we will change before next week.”
- Mistake: treating the framework like a script instead of a judgment tool.
BAD: “I asked my four standard questions, so I did the 1:1.”
GOOD: “I changed the questions because the person needed feedback, not a template.”
FAQ
The real failure is not bad structure. It is the refusal to make a judgment.
- Should a new manager use a strict 1:1 script?
Use one only until you stop freezing. After that, scripts become a crutch. The goal is not to sound consistent. The goal is to surface the right issue in under 30 minutes.
- Is Google's 1:1 approach too heavy for small teams?
No. The framework is heavier only if you confuse depth with bureaucracy. For a team of 4 or 5, it is usually the opposite: less noise, more honest coaching, fewer missed signals.
- What is the fastest sign that a 1:1 is broken?
If the employee leaves unchanged, the meeting failed. A good 1:1 produces a decision, a clearer risk, or a behavior change before the next week starts.
Ready to build a real interview prep system?
Get the full PM Interview Prep System →
The book is also available on Amazon Kindle.