💡 왼쪽 원문을 읽으면서 오른쪽에 따라 써보세요. Tab 키로 힌트를 받을 수 있습니다.

원문 렌더가 준비되기 전까지 텍스트 가이드로 표시합니다.

Introduction — Why 1:1s Are a Hot Topic Again

It is 2026: remote and hybrid work are the norm, and AI agents handle a large share of daily engineering work. Paradoxically, one of the most persistent recurring topics on Hacker News and GeekNews is something deeply human — 1:1 meetings and feedback. Posts like "my 1:1 with my manager has degraded into a status update" or "I got blindsided by feedback I heard for the first time in my year-end review" reliably draw hundreds of sympathetic comments.

The reason is clear. Agents help write the code, but **building trust and growing people cannot be automated.** Will Larson (lethain) called 1:1s "the most expensive recurring investment a manager makes," and Kim Scott proposed in Radical Candor a feedback culture that "challenges directly while caring personally." This article translates those classic insights into practical tools for the 2026 workplace, from both the IC (Individual Contributor) and the manager perspectives.

Why 1:1s Become Ritualistic

Diagnose the disease first. Here is the typical path along which a 1:1 dies:

Step 1: Start with no agenda ("So... anything to talk about?")

Step 2: Nothing to say, so the slot fills with status updates

Step 3: "I already heard that at standup..." -> both feel it wastes time

Step 4: "Busy week — skip this one?" -> becomes biweekly, then monthly

Step 5: Mutual surprise at the quarterly review (the birth of the surprise evaluation)

Three root causes:

1. **No purpose**: a 1:1 is not a reporting slot. Work progress flows fine through async channels (tickets, Slack, standup). The unique purpose of a 1:1 is **what async handles poorly** — obstacles, relationships, career, emotions.

2. **No preparation**: when both sides walk in unprepared, the conversation converges on the easiest topic, which is work status.

3. **No follow-through**: if what gets said never changes anything, the reason to speak disappears.

The Structure of a Good 1:1

A Shared Agenda Document

The single highest-leverage intervention is creating **one agenda document both people look at**. Notion, Google Docs, a wiki — anything works.

1:1 — Youngju x Manager (every Tue 14:00, 30 min)

Agenda for next meeting (both add in advance)

- [Youngju] Blocked on cross-team dependency in the payment migration — escalate?

- [Manager] Want your input on next quarter project assignments

Recurring check (2 min every time)

- Review last week action items

Action items

- [ ] (Manager) Confirm API timeline with platform team lead — by 6/16

- [ ] (Youngju) Draft career goals doc v1 — by 6/19

Past notes (newest on top)

2026-06-09

- Discussed: ...

- Decided: ...

Rules:

- **Add agenda items at least 24 hours before the meeting.** If there are zero items, cancelling that week is fine. But if it gets cancelled twice in a row, that itself becomes an agenda item.

- Accumulate notes in the same document. Six months of notes become insurance for both sides at review season.

The Three-Track Structure

Recommended time allocation for a 30-minute 1:1:

| --- | --- | --- | --- |

The career track is the heart of it. It does not need to happen every time, but **if a month has passed without a career conversation, that 1:1 has a warning light on.**

For ICs — How to Own Your 1:1

The owner of the 1:1 is the IC, not the manager. That single mental shift changes everything. Think of the manager 30 minutes as **a budget allocated to your growth.**

Prep Template (5 minutes before the meeting)

This week 1:1 prep notes

1. What is the one thing blocking me most right now?

(technical problem / people problem / process problem)

2. What can only my manager solve?

(authority, information, escalation, political support)

3. What valuable thing did I do last week that my manager might not know?

(self-advocacy is a legitimate use of a 1:1)

4. In what area do I want feedback?

("How was my communication in the last design review?")

5. Career: is my current work connected to my goals?

Good Topics vs. Bad Topics

| Good topics (unique 1:1 value) | Bad topics (better in another channel) |

| --- | --- |

| Collaboration friction with a teammate | Plain status updates |

| Career direction and next steps | Code review requests |

| Workload and burnout signals | Technical decisions a meeting can settle |

| Feedback for your manager | Bug discussions that belong in a ticket |

| Anxiety about org changes | Vacation schedules (email suffices) |

| Questions too awkward to ask elsewhere | Relitigating decided matters |

The Skill of Raising Blockers

When raising an obstacle, shape it as **a decision request, not a complaint.**

[Bad]

"The platform team will not give us the API, so we are stuck. It is so frustrating."

[Good]

"The platform team API slipped two weeks, which blocks the migration.

I see three options:

A. Wait (accept a two-week schedule slip)

B. Build a temporary adapter (two extra days of work, throwaway)

C. You negotiate priorities with the platform team lead

I lean toward B, but if C is possible that is the best outcome. What do you think?"

When you bring options plus your own recommendation, the manager only has to **judge** instead of **absorbing the problem**. This is the fundamental move of managing up.

For Managers — The Question Library and Silence

A Library of 20 Questions

Good 1:1s come from good questions. Organized by situation:

[Opening — state check]

1. If this week were a color, which one? Why?

2. What is consuming most of your energy lately?

3. Workload out of 10? If above 7, what should we drop?

[Unearthing obstacles]

4. What is most frustrating right now?

5. If I could fix exactly one thing for you this week, what would you pick?

6. Is there a process slowing you down?

7. Which meeting feels like a waste of time?

[Team and relationships]

8. Any team dynamics on your mind lately?

9. Who do you collaborate with best, and where is there friction?

10. Is there something going on that I seem unaware of?

[Career and growth]

11. Of your current work, what do you want more of, and less of?

12. A year from now, what would you need to be doing to call it success?

13. Learning anything lately? How could the company support it?

14. What do you think you are missing for the next step?

[Two-way feedback]

15. Any recent decision of mine you disagreed with?

16. What should I do more of, and less of, to make your work better?

17. Honestly, how is the way I run team meetings?

[Closing]

18. What from today should become an action item?

19. Anything you need me to check on before our next 1:1?

20. What did we not get to that we must cover next time?

The Skill of Enduring Silence

The thing managers are worst at is silence. They ask a good question, three seconds pass, anxiety wins, and they fill in the answer themselves. At that moment the 1:1 becomes a manager monologue.

- After asking, **count seven seconds in your head.** The deeper the question, the more thinking time the other person needs.

- If the answer is short, go one level deeper with a single phrase: "Tell me a bit more?"

- Talk-ratio target: **manager 30, IC 70.** Retrospect on the ratio after each meeting.

Comparing Feedback Frameworks — SBI, COIN, Radical Candor

There are many feedback frameworks, but the essence is the same: **start from observable facts, state the impact, and agree on the next behavior.** Here are the big three compared:

| --- | --- | --- | --- | --- |

The Radical Candor quadrants look like this:

Care Personally

Ruinous Empathy | Radical Candor

Sees the problem but | Says it directly,

stays silent for fear | while caring <- the goal

of hurting |

---------------------------------------------------> Challenge Directly

Manipulative | Obnoxious Aggression

Insincerity | All bluntness,

Only talks behind | no caring

backs |

A common misreading: Radical Candor does not mean "just be brutally honest." The point of the quadrants is that **directness without personal care is simply aggression.** If you have not built a trust balance day to day, feedback fails no matter which framework you use.

Five Difficult-Feedback Scripts

Scenario-based scripts written at the level of actual lines, built on the COIN structure (Context-Observation-Impact-Next).

Script 1 — Performance: a teammate repeatedly missing deadlines

"Can we talk about this sprint for a moment? (Context)

In the last three sprints, about half of your tickets rolled over

unfinished on the last day. (Observation — facts only; no generalizations

like you are always late)

That pushes the QA schedule and someone ends up covering on weekends. (Impact)

What I want to understand is whether estimation is hard, or whether

interruptions keep landing on you. I would like to find the cause together.

How do you see it?" (Next — diagnose jointly)

Script 2 — Collaboration: a teammate with an aggressive code review tone

"About the comment you left on the PR yesterday. (Context)

There was a sentence saying you could not understand why anyone would

write it this way. (Observation — quote it)

For the recipient, it can feel like the person is being judged rather than

the code, and in fact their PR frequency has dropped since. (Impact)

The technical point itself was valid. If you phrase the same point as

asking what the intent of the approach is and how case X is handled,

you keep the technical sharpness without triggering defensiveness.

Willing to try that?" (Next)

Script 3 — Attitude: a senior shutting down dissent in meetings

"I want to share something I noticed in the design meeting today. (Context)

When the two juniors proposed alternatives, both times the discussion

ended at the first sentence with: we tried that before, it does not work.

(Observation)

I know that judgment comes from experience. But when that pattern repeats,

new ideas stop appearing in meetings at all, and unexamined risk

becomes everyone problem. (Impact)

Next time, before concluding, could you ask just one question — what

scenario is this proposal assuming? Coming from you as the senior,

that single sentence sets the safety level of the whole meeting." (Next)

Script 4 — Growth: a strong performer whose work is invisible

"This is positive feedback, so relax. (Context)

During last month incident, finding the root cause was essentially your

analysis, but neither the retro document nor the presentation showed

that process. (Observation)

What ends up in evaluation material is only the docs and the talks,

so your impact is being recorded as smaller than it really is. That is

your loss, and the team also loses a chance to learn a good analysis

method. (Impact)

Shall we set a goal next quarter to write up your analyses as short posts?

I will help polish the first one." (Next)

Script 5 — Burnout signal: a teammate who suddenly went quiet

"I have been wondering how you are doing. (Context)

Over the last two weeks you barely spoke in meetings, and you have not

been scheduling the pairing sessions you usually initiate.

(Observation — behavior, not speculation)

I am not saying anything is wrong — it is just different from your usual

pattern, and I care. (Concern instead of impact)

Whether it is work or something else, share only as much as you want.

And if you do not want to talk right now, that is fine too."

(Next — a door, not a demand)

Shared principles:

- **Separate facts (things a camera could record) from interpretations.** "Bad attitude" is an interpretation; "interrupted three times in the meeting" is a fact.

- **One topic at a time.** Batching feedback kills every message in the batch.

- **Be fast.** The longer the gap between event and feedback, the more exponentially the effect decays.

The Receiving Skill — Turning Feedback Into an Asset

The ability to receive feedback well is rarer than the ability to give it — which is exactly why it stands out.

Handling the Defensive Reaction

When you hear criticism, your brain fires a threat response. That is normal. The problem is opening your mouth while in that state.

Four steps when defensiveness rises

1. Pause: swallow the first sentence ("no, actually..." is banned)

2. Note: write down what you heard, verbatim (the act of writing cools emotion)

3. Clarify: "Could you give me one concrete example?"

4. Ask for time: "This is important and I want to think it over.

Can we talk again tomorrow?" — you owe no instant answer

Clarifying Question Collection

- "In what specific situation did you feel that?"

- "Was that a one-time thing, or do you see it as a pattern?"

- "What would have been better for me to do?"

- "Is this advice for my growth, or something that affects my evaluation?" (important — calibrate the weight)

You do not have to agree with the feedback you receive. But you must send the signal that **you heard it, understood it, and will consider it.** Agreement and listening are different acts.

Upward Feedback — Talking to Your Manager

The hardest feedback of all, because of the power asymmetry. The key to safe phrasing is framing it as **an observation about effects, not a critique of the person.**

[Safe upward feedback formula]

"From the perspective of how I work best..." (make yourself the subject)

+ observable fact

+ the impact on you

+ a request (an experiment proposal, not a demand)

[Example 1 — micromanagement]

"From the perspective of how I work: when detail check-ins arrive two or

three times a day on in-progress work, the context switching breaks my

focus blocks. Could we run a two-week experiment where I post a daily

summary in Slack proactively instead?"

[Example 2 — frequently changing direction]

"Over the past month priorities changed three times, and the team threw

away started work twice. I accept that changes happen. But if, at the

moment of the change, you could share even one line about what changed

upstream, the team would understand and pivot much faster."

If you are a manager who wants upward feedback, start by **disclosing your own weaknesses concretely.** Self-disclosure like "I talk too long in meetings — I am working on it, so signal me next time it happens" primes the pump of safety.

Remote 1:1 Tips

- **Walks over cameras**: when possible, occasionally try an audio-only walking 1:1. When the screen-gaze disappears, hard topics surface more easily.

- **Document first, screen share later**: if both read the agenda doc silently first, 30 minutes becomes twice as deep.

- **Across time zones, supplement with async 1:1s**: one weekly video call plus async voice memos during the week works well.

- **Mind the bandwidth loss of emotional signals**: remote strips information from faces and silences. Ask explicitly: "I cannot read your expression well — how did that proposal land?"

Building a Feedback Culture — Cadence and Psychological Safety

To go beyond personal skill and make it a team-level system:

1. **Shorten the cycle**: concentrating feedback into one annual review guarantees surprises. Light weekly feedback in 1:1s plus a quarterly synthesis is the base rhythm.

2. **The ratio of positive feedback**: in a team where only corrective feedback flows, feedback itself becomes a punishment signal. Specific praise (also in SBI form) should run at least three times the frequency of correction.

3. **Leaders receive first**: psychological safety forms when the leader requests feedback about themselves first in retros — and visibly acts on it.

4. **Normalize feedback requests**: make "tell me one thing about how that presentation went" part of the team everyday language. Requested feedback does not trigger defensiveness.

Notes and Follow-Through — Tracking Actions

A 1:1 stays alive only if what is said changes things.

Action item rules

- Every action has an owner and a deadline (otherwise it is a wish, not an action)

- The first 2 minutes of the next 1:1 always review last actions

- An action carried over 3 times gets deleted or redefined (no zombie actions)

- Career agreements accumulate in a separate doc (evidence for review season)

Notes matter especially for ICs. Six months of 1:1 records and completed-action history are the strongest primary source when building a promotion case.

Anti-Pattern Collection

| Anti-pattern | Symptom | Prescription |

| --- | --- | --- |

| Sandwich abuse | Message buried in praise-criticism-praise | Correct separately, praise separately |

| Surprise evaluation | Problems first heard at review time | Distribute via weekly feedback loops |

| Status-report 1:1 | Repeats standup content | Move reporting to async |

| Frequent cancellations | 1:1 sacrificed first when busy | Two consecutive cancels become an agenda item |

| Manager monologue | Talk ratio inverted to 70/30 | Train the 7-second post-question silence |

| Zombie actions | Same action carried over weekly | Delete or redefine after 3 carries |

| Feedback batching | A quarter of feedback in one day | One topic within 48 hours of each event |

One more word on the sandwich technique. Opening with praise, inserting criticism, closing with praise — the moment the recipient learns the pattern, **every compliment becomes suspected as a prelude to criticism.** It is a double loss that destroys the value of praise itself. Corrective feedback is better delivered standalone, with respect.

Pitfalls and Critical Perspectives

- **Beware framework absolutism**: memorizing SBI does not help if trust is absent — it just sounds like a well-structured attack. Frameworks only work on top of a trust balance. Relationship first, technique second.

- **Cultural differences**: the acceptable range of directness varies by culture. Applying the Radical Candor "challenge directly" verbatim reads as rudeness in some organizations. Calibrate intensity to your team context.

- **1:1s are not a cure-all**: structural problems (understaffing, wrong goals) do not get solved in a 1:1. If the same obstacle shows up three weeks running, it is not a conversation problem — it is an organizational problem.

- **The double edge of notes**: in some organizations 1:1 notes can be used in evaluations or legal proceedings. For sensitive personal matters, agree on the recording scope before writing things down.

Final Checklist

For ICs

- [ ] Is there a shared agenda doc, with items added 24 hours ahead

- [ ] Do you bring blockers as options plus a recommendation

- [ ] Do you raise a career topic at least monthly

- [ ] When receiving feedback, do you ask clarifying questions instead of instantly responding

- [ ] Do you deliver upward feedback as observation + impact + experiment proposal

- [ ] Are you accumulating 1:1 notes and completed-action history

For Managers

- [ ] Is your talk ratio at or below 30 (7-second silence after questions)

- [ ] Do you rotate questions across tracks from the library each week

- [ ] Do you deliver corrective feedback within 48 hours of the event

- [ ] Is positive feedback at least 3x the corrective feedback

- [ ] Are there zero surprises in review meetings (if any exist, that is your failure)

- [ ] Did you request feedback about yourself first

- [ ] Do action items have owners and deadlines, reviewed every time

Closing

In an era where AI writes the code, the essence of what remains for managers and ICs is people. The 1:1 and the feedback conversation are the smallest, most frequently repeated units that touch that essence. No grand reorganization required — you can start next week by creating one agenda document and changing one question. Once the small loop starts spinning, trust compounds.

References

- Radical Candor official site — https://www.radicalcandor.com/

- Will Larson, One-on-ones — https://lethain.com/one-on-ones/

- Kim Scott, Radical Candor (the book) — https://www.radicalcandor.com/the-book/

- Center for Creative Leadership, SBI Feedback Model — https://www.ccl.org/articles/leading-effectively-articles/closing-the-gap-between-intent-vs-impact-sbii/

- Manager Tools, One-on-Ones series — https://www.manager-tools.com/map-universe/one-ones

- Lara Hogan, Questions for our first 1:1 — https://larahogan.me/blog/first-one-on-one-questions/

- Camille Fournier, The Managers Path (publisher page) — https://www.oreilly.com/library/view/the-managers-path/9781491973882/

- Hacker News: one-on-one discussion search — https://hn.algolia.com/?q=one-on-one

- GeekNews (management and team culture discussions) — https://news.hada.io/

- re:Work by Google, Manager guides — https://rework.withgoogle.com/en/guides/managers-coach-managers-to-coach