Download the '1:1 Not Fan Che' Checklist: Stop Wasting Your 1:1 Time

TL;DR

Most 1:1s fail because employees treat them as status updates, not leverage points. The issue isn’t frequency—it’s intent. Download the '1:1 Not Fan Che' Checklist to convert your meetings from passive check-ins into strategic alignment engines.

Who This Is For

This is for individual contributors and managers at tech companies—especially in product, engineering, and design—who are spending 5+ hours a month in 1:1s and seeing zero career acceleration. If your manager treats your 1:1 like a calendar placeholder, or if you leave the meeting with no clearer sense of priority, this is for you.

Why do my 1:1s feel like a waste of time?

Your 1:1s feel like a waste because they’re run as汇报 (huìbào), not dialogue. In a Q3 debrief at a Series B startup, an EM admitted: “We have 1:1s every week, but I only hear blockers when things are on fire.” That’s the norm, not the exception.

The problem isn’t your manager’s availability—it’s the absence of structure. At Google, PMs are trained to treat 1:1s as decision forums, not update sessions. One senior director told me: “If I’m hearing about a project for the first time in a 1:1, someone failed upstream.”

Not a report-out, but a push for judgment.

Not a log of activity, but a test of prioritization.

Not a performance review, but a real-time calibration of influence.

Most people walk into 1:1s with an agenda of tasks. High-leverage players bring a theory: “Here’s what I’m optimizing for, here’s the trade-off I’m making, here’s where I need your call.” That shift—from labor to strategy—is what turns a meeting into momentum.

What should I actually talk about in a 1:1?

Talk about trade-offs, not tasks. In a hiring committee meeting at Meta, a candidate’s feedback read: “She used her 1:1s to surface cross-team dependencies six weeks before launch—enough time to reallocate resources.” That’s the signal: 1:1s as early-warning systems for leverage points.

Most employees recite: “Did X, working on Y, blocked on Z.” That’s noise. What managers actually evaluate in retrospective is: Did this person identify the right constraint? Did they escalate with context, not panic? Did they use my time to unlock multiplier work?

You should discuss:

A decision you’re holding because it requires downstream alignment
A priority conflict between team goals and org goals
Feedback you’re hesitant to give a peer, and why
A skill you’re developing, and how you’re measuring progress

Not “what I did,” but “what I’m choosing.”

Not “what’s blocking me,” but “where I need your weight.”

Not “can you help,” but “here’s the outcome I’m protecting.”

I saw a junior PM at Amazon turn her 1:1 into a promotion accelerator. Instead of listing PRDs written, she came with: “I’m deprioritizing feature polish to hit the Q4 compliance deadline. That means Sales gets less training—but Legal gets full sign-off. Do you agree with that trade?” Her manager didn’t just agree—he looped in the GTM lead. That conversation became Exhibit A in her promotion packet.

How do I get my manager to engage in 1:1s?

Stop waiting for your manager to set the tone—frame the stakes first. In a debrief at a late-stage fintech, a lead engineer said: “My manager only engages when I tie the topic to risk.” That’s the unlock: people respond to consequence, not curiosity.

One IC at Stripe restructured her 1:1s by starting each with: “The risk here is threefold: timeline slippage, team burnout, and customer trust erosion. I want your read on which we should optimize for.” Her manager’s engagement spiked—not because the topic changed, but because the frame did.

Not “I’d like your thoughts,” but “I need your call.”

Not “Can we talk about X?” but “X will impact Y unless we decide Z by Friday.”

Not “I’m stuck,” but “I’ve made a choice, and I want you to validate or override it.”

Power isn’t given—it’s claimed through decision velocity. Managers don’t invest in people who ask for permission. They invest in people who force judgment, then act on it. Your 1:1 should be the place where you make that demand respectful, data-backed, and time-bound.

How often should I have 1:1s with my manager?

Once a week is the minimum viable frequency for ICs in high-velocity roles. Biweekly is acceptable only if you’re senior (L5+) or in a stable phase (post-launch, pre-planning). At Netflix, where “context over control” rules, engineers at L4 and below are expected to initiate weekly syncs—even if the manager doesn’t.

I reviewed 23 promotion packets from Facebook’s 2022 cycle. Every promoted IC had documented evidence of weekly managerial touchpoints for at least six months pre-review. Not formal reviews—1:1s where they surfaced risk, negotiated priority, or requested sponsorship.

But frequency without function is theater. A PM at Uber had weekly 1:1s but was denied promotion because her manager wrote: “I didn’t see her making hard calls.” The meetings existed—but they lacked decision density.

Not “we talk every week,” but “we made three irreversible calls in the last 30 days.”

Not “we have time scheduled,” but “we’ve resolved X, Y, Z escalations before they became fires.”

Not “we’re aligned,” but “we’ve tested alignment under pressure.”

If your 1:1s aren’t producing documented decisions, reduce frequency and invest that time in stakeholder mapping instead.

What should I do if my manager dominates the 1:1?

Reclaim the agenda by pre-circulating decision prompts. In a People Ops review at a public SaaS company, a manager was flagged for “conversational overreach” in 1:1s—taking over discussions, offering unsolicited advice, derailing focus. The fix wasn’t feedback; it was structural.

The IC began sending a 3-bullet pre-read 24 hours in advance:

Decision needed: Should we delay the API rollout to fix auth bugs?
Options: (A) Delay by 2 weeks, (B) Ship with known issues, (C) Partial launch
My recommendation: B, with a comms plan for enterprise customers

The manager stopped dominating—not because he changed, but because the conversation was already framed.

Not “let’s chat,” but “here’s the choice.”

Not “what do you think?” but “I recommend X—do you override?”

Not “can we talk about priorities?” but “I’ve ranked them—disagree?”

Control isn’t about airtime. It’s about who defines the problem. If you let your manager set the agenda, you’re signaling you can’t. Send the pre-read. Own the frame. Force the call.

Preparation Checklist

Define one decision or trade-off to resolve in every 1:1
Send a 3-bullet pre-read 24 hours in advance
Track decisions made and actions owned in a shared log
Audit your last 5 1:1s: how many produced irreversible calls?
Work through a structured preparation system (the PM Interview Playbook covers 1:1 strategy with real debrief examples from Google, Meta, and Amazon)
Identify one peer whose 1:1s generate visible momentum—reverse-engineer their approach
Every quarter, ask: “Did my 1:1s accelerate my impact, or just document it?”

Mistakes to Avoid

BAD: Showing up with a list of tasks completed. “I finished the mockups, wrote the spec, and met with engineering.” This frames you as a doer, not a driver. Managers don’t promote people who report labor.

GOOD: Opening with: “I’m choosing to delay the spec finalization to get Legal input on data retention. That pushes dev start by three days, but reduces compliance risk. I need your call on whether that trade is acceptable.” This frames you as a prioritizer.

BAD: Waiting for your manager to ask, “How can I help?” No manager at a tech company promotes someone who waits to be rescued. That’s entry-level passivity.

GOOD: Stating: “I need you to message the security team by EOD to unblock the audit. I’ve drafted the note—can you send it or suggest changes?” This is sponsorship engineering—specific, time-bound, and respectful of their time.

BAD: Letting the meeting end without a decision or action. “We’ll circle back next week.” That’s entropy.

GOOD: Closing with: “So we’re aligned: ship with known bugs, comms by Thursday, you’ll ping Security by 5 PM. I’ll update the ticket.” Decision logged, ownership clear, momentum preserved.

FAQ

Why isn’t my manager giving me more guidance in 1:1s?

Your manager isn’t withholding guidance—they’re assuming you’ve made a call unless you flag otherwise. In a hiring committee at Google, one candidate was dinged for “low agency” because her 1:1 notes only contained questions, not recommendations. Bring options, not open loops.

Should I send notes after every 1:1?

Only if they include decisions and owners. At Amazon, L5+ PMs are expected to maintain a “1:1 decision log” that’s visible to their manager. Notes that just summarize conversation are shelfware. Capture the irreversible calls, not the chat.

What if my manager cancels 1:1s constantly?

Canceling 1:1s is a signal of low strategic trust. One engineering lead at Lyft was told directly: “I cancel when I don’t see ROI.” The fix wasn’t complaining—it was sending a pre-read so valuable the manager refused to miss it. Make the meeting irreversible, or it will be.

Ready to build a real interview prep system?

Get the full PM Interview Prep System →

The book is also available on Amazon Kindle.