1:1s That Drive Momentum

Gist

Make 1:1s the report’s meeting and use them to change the work, not recap it.

The Beginning

This is the report’s meeting—you facilitate; they drive. Your job in a 1:1 isn’t to look busy or to collect a tour of updates you could read in a daily or weekly recap. We all get those, kind of a must, nature of the beast. Here in 1:1 your job is to raise output. That means the time you spend together should change the work that happens after the meeting. It facilitates what gets built, what gets unblocked, what gets decided. As Andrew S. Grove puts it in High Output Management, a manager’s job is to raise the output of the team—1:1s are one of the most direct tools to do it.

Ditch what a document emailed can cover; keep what a document can’t. Status lives in dashboards and briefs. In the room, choose. Clarify a result. Remove a blocker. Adjust how hands-on you’ll be for this task, this week. If you treat 1:1s like a weekly performance amplifier instead of a calendar fixture, they become the safest, sharpest place to surface what matters and commit to what’s next.

Close strong every time: end with one written commit so momentum survives the meeting. If it’s not written, it’s optional. If it is written, it ships.

The Agenda (run it the same weekly)

Think of the agenda as three doors you walk through together. It’s simple by design so you can repeat it until it becomes muscle memory.

1) Priority → Blocker → Calibration

Start with the destination. “What result are you aiming at by Friday?” Not “what are you working on,” but what will be true. When the result is visible (publish the PRD, close the top three bugs, ship the onboarding test), decisions get easier. Without the result being expressively clear there is no real goal. Working on the bugs in the system is a great example of no clear goal. In fact, this is just a statement.

Then the present: “What’s the smallest move that clears the biggest blocker today?” Keep it tiny and actionable—one email, one pull request review, one decision you can make. These should be items they cannot clear themselves. Sometimes they just need one swing from a bigger hammer.

Finally, calibrate how you’ll work together this week. Do you need more context, faster feedback, fewer interruptions? You’re tuning the operating system of the work, not just the tasks. Giving the support needed to create efficiency.

2) Outcome → Obstacles → Help Needed

Rewrite vague goals or statements into visible outcomes with a date: “By Thursday, we’ll demo the new flow to three users.” Name the obstacles out loud—conflicts, unknowns, missing assets. Then ask, “What help from me would raise output fastest?” Maybe it’s escalation, a quick design review, or shielding time. This keeps help concrete rather than a vague “let me know or tell me exactly what you need from me.”

3) What changed → What’s stuck → What we’ll do

Skip stale updates. Start with change since the last 1:1—new information, new risks, new opportunities. Name what’s actually stuck (don’t let it hide behind busyness). Then decide what you’ll do before you leave the room. The rule is: every 1:1 ends with forward motion.

Close with: Owner · Outcome · Date — a single line you both can see.

Example: “Alex — publish PRD v1 for review — Fri 11/07.” Send it in chat, add to the document, or screenshot the note. The paper trail is part of the power: it makes progress concrete and revisitable.

Calibrate by TRM (Task-Relevant Maturity)

A 1:1 isn’t one-size-fits-all; it’s a dial. TRM (Task-Relevant Maturity)—Grove’s lens—is a quick read of how skilled and informed someone is for this specific task right now. It tells you how close to stand.

High TRM: Align on outcomes and constraints—don’t micromanage.

When someone has done this kind of work repeatedly, your best move is clarity up front and check-ins at sensible points. Agree on the “done” picture and the lane boundaries (quality bars, risks, dependencies), then get out of the way. If you protect their focus, they deliver as agreed upon, and there is more time to move other issues forward.

New area: Provide a model example and a simple template.

Unknowns create drag and is costly, both in time and money. Hand them a “good looks like this” artifact and a lightweight structure. You shrink ambiguity so they can spend their time on the substance, not guessing your expectations and desired outcomes.

Slipping quality: Review one artifact together in-session.

Not “do better,” but “let’s look at this doc/design and mark what ‘better’ means.” Name the standard, note the deltas, and agree on one visible improvement for next time. Coaching attaches to reality, not abstractions. My better and your better is almost certain to be different unless we discuss it.

Over-confidence: Ask for a quick pre-mortem.

“If this failed in two weeks, why?” You’re not killing momentum; you’re removing blind spots. The five-minute imagination exercise often reveals the one risk worth addressing now. Once on this road it may reveals even more lurking in the shadows.

TRM in one sentence: How skilled and informed is the person for this task now? Low TRM → stay close and concrete. High TRM → set outcomes and space. Medium → pick one spot to pair, then move to async feedback.

Mini-Scripts (drop straight into 1:1s)

Here are some direct drop ins for the meeting. These are steering questions. Your job is to ask and then note.

- “What’s the smallest move that clears today’s blocker?”

- “Give me a confidence 1–5 on this task—what bumps it up one point?”

- “What help from me would raise output fastest?”

- “Let’s end with Owner · Outcome · Date—one line.”

Pitfalls and Fixes

These are the items that will burn and waste a lot of resources if missed. This is just a few examples.

- Vague goals → Rewrite as a visible outcome with a date (“publish v1 by Thu”).

- Whack-a-mole topics → Hold to the 3-part agenda; park tangents in a parking lot.

- Wrong altitude → Match TRM on the spot: hands-on for low TRM; outcomes-only for high TRM.

- Drift/cancellations → Reschedule, don’t cancel. Weekly cadence compounds clarity and trust.

Why it works

This approach shifts 1:1s from talk to output mechanics. You decide faster because the agenda steers you to outcomes, blockers, and the one concrete next step.

You build clarity and trust because the rhythm is predictable and the commitments are explicit. And you cut decision latency—the silent tax that kills momentum—because each meeting ends with a visible owner, outcome, and date.

The written line isn’t busywork; it’s the bridge from conversation to change. This is straight from Grove’s output playbook: tune the meeting to the work (via TRM), decide fast, and leave with a visible commit.

Closer / CTA

- Use Priority → Blocker → Calibration as your spine in one 1:1 this week.

- Replace status with one decision before you leave the room.

- End with Owner · Outcome · Date. Keep the weekly slot; skip none for 30 days.

- Reply with your one-line commit and what changed.

Spotlight — Andrew S. Grove

Former Intel CEO and author of High Output Management. Grove popularized TRM and the idea that managers increase output by calibrating how hands-on they are, making decisions quickly, and using 1:1s to surface and remove real blockers.

Reading list to further your knowledge

• High Output Management — Andrew S. Grove
Start now: Kindle | Audible | Bookshop (E-book)
Read the book: Amazon | Bookshop

• The Making of a Manager — Julie Zhuo
Start now: Kindle | Audible | Bookshop (E-book)
Read the book: Amazon | Bookshop

Appendix

Example one-line commits:

- “Rina — ship onboarding test to 100 users — Wed 11/05.”

- “Leo — escalate vendor contract block to Ops — today 3pm.”

Quick self-check after each 1:1:

1) Did we write a single clear commit?

2) Did we match the altitude to TRM?

3) Did we remove or reduce a blocker today?

“Affiliate links help support Jiffy Notes at no extra cost.”