本文へ移動
cccskills
無料GitHub で公開

hard-conversations

Writes you a ready-to-use script for a feedback or hard conversation, then rehearses the pushback. Use when you need to give tough feedback, confront a peer, tell a report they are underperforming, deny a promotion, prepare to fire someone, say no to your boss, ask for feedback, or repair a conversation that went badly. Draws on 66 Lenny's Podcast guests including Kim Scott, Carole Robin and Alisa Cohn.

インストール方法を見る

含まれるファイル(4)

  • SKILL.md18.3 KB
  • assets/card.png2.6 MB
  • references/frameworks.md16.1 KB
  • references/quotes.md5.5 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Hard Conversations

hard-conversations: lead guest team

Turn a conversation you are dreading into a short, specific script you can say out loud, plus a plan for how they will react. Built from 183 insights from 66 Lenny's Podcast guests. Lead team: Kim Scott, Carole Robin, Alisa Cohn.

When to use

  • You owe someone feedback and keep putting it off (a report, a peer, a designer, an engineer, your boss).
  • A report keeps missing deadlines, interrupting people, or not meeting the bar, and softer hints have not worked.
  • You are denying a promotion, delivering a bad review, or heading toward a firing or a layoff.
  • A peer or cross-functional partner is damaging your work (excluding you, undercutting you) and you are getting resentful.
  • You just got hard feedback and need to decide how to respond, or you want real feedback and everyone says everything is fine.
  • A conversation went sideways (tears, anger, defensiveness) and you need a repair.
  • You need to say no to a request without damaging the relationship.

If the user attached anything (a draft message, review text, Slack thread, 1:1 notes, performance doc), read it first and work from it. Do not ask for what the file already answers.

Step 1 — Diagnose (ask before answering)

Ask only what you cannot infer. Max 4 questions:

  1. Who is it with, and how much trust and history is there? Report / peer / boss / exec / cross-functional; how often do you praise them specifically? Why: low trust means build the reservoir and the opt-in first (Alisa Cohn, Julie Zhuo); high trust allows blunter delivery (Kim Scott, Ebi Atawodi).
  2. What kind of conversation is it? A one-off moment, a recurring pattern, a gap against stated expectations, a promotion no, a pre-exit warning, friction that is mostly about how it feels, or you are the one receiving? Why: this picks the play in Step 2.
  3. What is your evidence, and have you stated the expectation clearly? What would a video camera have recorded? Have you ever said the bar out loud? Why: unclear expectations turn this into a clarity conversation, not a performance one (Molly Graham, Ben Horowitz, Alisa Cohn).
  4. What outcome do you want, and what makes this hard for you? (Fear of tears, venting, protecting your reputation, fear they will quit.) Why: it exposes which failure mode you are in (ruinous empathy vs aggression) and whether you should wait before speaking.

Step 2 — Pick the play

If… (situation)UseFromWhy
Small, fresh moment (meeting, doc, demo)CORE + HHIIPPP (Context, Observation, Result, Next step; do it now, in person or on the phone)Kim ScottFast, behavior-focused, works for praise and criticism
Recurring behavior, relationship matters, you are getting irritatedBehavior-feeling-reason + stay on your side of the netCarole RobinKeeps you to what you actually know; builds the relationship
You need a structured opener for a report or peer, minutes of prepSBI, 4 Is, or What / So What / Now WhatPaige Costello, Matt AbrahamsLight structures that end in problem solving
Performance gap against expectationsPerformance feedback script, after the expectation-clarity checkAlisa Cohn, Molly GrahamEvidence, link to their goals, agree on the fix
Pattern persists after clear feedback; exit is possiblePre-firing 30-day conversation, then a short firing conversationAlisa Cohn, Matt MocharyNo surprises; HR and legal involved
You are denying a promotionPromotion-denied script (decision first, two reasons, hope)Alisa CohnShort, clear, leaves a path
The person is defensive, angry, or cryingPause script, curious-not-furious, move up on careAlisa Cohn, Kim ScottHold the message, change the temperature
It went badly or you lost your temperRepair (own it, name impact, say what changes)Becky Kennedy, Matt Abrahams, Carole RobinTrust is built by repair, not perfection
You are the one asking or receiving feedbackGo-to question, count to six, reward the candorKim Scott, Jules Walter, Nikhyl SinghalMost feedback you want never arrives unless you ask well
You need to decline a requestSay no by talking about trade-offsWes KaoGets the no without the word

Step 3 — Run it

0. Prep (always, ten minutes)

  1. Motive check. Are you helping them improve or venting? If venting, wait (Alisa Cohn, Julie Zhuo). Vent first to a friend or partner, then cut about 90% of what you wanted to say; keep only what drives behavior change (Wes Kao).
  2. Worry audit. Split your hesitation: which part is about their feelings, which part is about how you will look (Kim Scott). The second is self-protection, not kindness.
  3. Evidence. Write 2-3 observable facts with dates (Tuesday, 3:00 meeting, interrupted me three times). If you cannot, you are holding a judgment, not feedback (Alisa Cohn, Kenneth Berger). Swap labels (rude, self-involved, not strategic) for countable behaviors.
  4. Expectation check. Did they know the bar? If you were unclear, run a clarity conversation first (Molly Graham, Ben Horowitz: when you want to yell, you probably have not explained it).
  5. Outcome. One sentence: by the end, we agree that ___. Add an ask, not just a complaint (Kenneth Berger).
  6. Stretch only 15%. Say something slightly outside your comfort zone, no further (Carole Robin).
  7. Timing and channel. Do it soon, in person or by phone, never Slack or email. Delay only if either of you is too upset (Kim Scott). Praise in public, criticize in private by default (see debates).

A. Impromptu feedback: CORE (Kim Scott)

  1. Context: where and when. Observation: what you saw or heard. Result: the impact. Next step: what to do. For praise, the next step is do more of that.
  2. Start neutral with a question (were you aware of it?), offer help, and escalate directness only if they brush it off.
  3. Frame it as your read, not the truth; ask how they see it (Kim Scott).
  4. Done when they can say back the behavior and the next step.

B. Interpersonal feedback: behavior-feeling-reason (Carole Robin)

  1. Three realities: your intent, your behavior, their impact. You only know your own side and the shared behavior. Never narrate their motives.
  2. Script: when you [specific behavior], I feel [one feeling word], and I'm telling you because [outcome I hope for]. Then ask what happened on their side and problem-solve.
  3. Net test: if your sentence needs like or that after I feel, you crossed the net. Replace it with a single feeling word (sad, irritated, anxious).
  4. Pinch before crunch: if irritation is growing, raise it now while small. If you have wanted to say it for three or four days, you are out of integrity (Kenneth Berger).
  5. Resolve the interpersonal friction before you give task feedback, or the task feedback becomes a proxy (Carole Robin).

C. Performance gap (Alisa Cohn, Molly Graham, Becky Kennedy)

  1. Open neutral: I wanted to have a conversation about something I have been observing.
  2. State 2-3 facts, then why it matters to their goals. Anneka Gupta also starts by asking where they want to go in their career.
  3. Hold identity and behavior apart: this is a good person doing a late-PRD pattern (Becky Kennedy). Say it is a pattern, name the business need, then ask what is going on.
  4. Check clarity (Molly Graham): what do you see as your role and what success looks like? If their answer differs from yours, re-clarify before judging.
  5. Invite their view, then agree on what changes, by when, and how you will both know.
  6. Offer help (examples, a class, a pairing); do not take over the task.

D. The harder variants

  • Promotion denied (Alisa Cohn): say it will be hard to hear and state the decision in the first sentence; give two reasons; say it matters that they succeed; commit to concrete help; offer to revisit next week. If they argue tenure or fairness, mirror, restate the criteria, and say the decision stands.
  • Pre-firing (Alisa Cohn): we have to have a difficult conversation. Recap that you raised it multiple times over months, cite current evidence, give a deadline (about 30 days) and the consequence, and affirm what they bring. Involve HR and legal. Test: if the honest answer to have I been crystal clear is sort of, you have not.
  • Firing and layoffs: short and simple. Recap prior conversations, state the decision, hand logistics to HR. The person hears it from their manager one-on-one, never by email or in a group (Matt Mochary). Offer to be their agent with your network.
  • Environment-fit framing (Kevin Yien): adapt to this environment or find one that fits better. It is empowering, not a verdict.
  • Specific-role gap (Ben Horowitz): name what they do well, then the specific requirement of the role they are missing, the concrete consequence, and your offer to help.

E. When it gets hot

  1. Warn first: one sentence of notice that it will be a difficult conversation lowers the threat response (Matt Mochary).
  2. Defensive: pause. Let's pause for a second; the energy has changed. I'm saying this to help you. Offer to continue now or later. Hold the point (Alisa Cohn).
  3. Angry: be curious, not furious. Ask why they are so angry while keeping the issue on the table (Kim Scott). Anger distances; name the underlying hurt or fear if it is yours (Carole Robin).
  4. Sad or crying: move up on care without retracting. I may not have said that in the best way; how could I have said it differently? Do not say no big deal (Kim Scott). Tears are not a reason to withhold; Alisa Cohn's client was thanked the next day.
  5. They say the facts are wrong: list every specific problem and show the pattern (Kim Scott). Ask what they heard you say; it often differs from what you said (Carole Robin).
  6. Close: restate agreement, who does what, and when you will check in.

F. Asking and receiving feedback

  1. Ask presumptively, in your own words, not do you have any feedback. Kim Scott's go-to: what could I do or stop doing that would make it easier to work with me? Alternatives: what could I have done this week to better support you? or a specific behavior (Jules Walter: to what extent did I show executive presence?). Offer your own critique first so they can agree.
  2. Count to six in silence. If still nothing, ask them to notice something before next time.
  3. Listen to understand, repeat it back more sharply than they said it, ask is that fair? (Nikhyl Singhal).
  4. Respond: agree with the 5-10% you can, say you will think about the rest, then return with a respectful explanation. Or choose: act as stated, look for themes, or keep your style and explain the trade-offs (Ami Vora).
  5. Reward the candor: fix it, make it visible, name who told you, then ask if you over- or under-corrected (Kim Scott, Nikhyl Singhal).
  6. Mine the discard pile: the feedback you wrote off as odd is often the shadow of your strength (Nikhyl Singhal).

G. Declining a request (Wes Kao)

Yes, I can do that. It means [current work] moves to [date]. Does that work, or should I stay on the original? A prioritization conversation, not a refusal.

Where the experts disagree

  • Criticize in private (Kim Scott, Elizabeth Stone) vs in public (Jeetu Patel, Keith Rabois). Use private when trust is not yet established, the issue is personal, or the person is sensitive. Use public only on established-trust teams where the goal is the best idea winning and visible problem-solving. Default: private; keep praise public.
  • Be soft and warm (Alisa Cohn's even-keeled opener, Boz: be kind, not nice) vs just say it (Claire Vo: not meeting expectations, Kim Scott's escalation). Soften tone, never content. If hints have failed, go to Claire Vo's plain version: state the gap, the consequence, that you believe in them, and that it is their responsibility.
  • Feelings first (Carole Robin, Rachel Lockett) vs facts only (Alisa Cohn, Kenneth Berger). Use a feeling word when the relationship is the issue and you are close; stay on facts and impact for performance conversations with reports. Both reject judgments.
  • Do it now (Kim Scott) vs wait until calm (Alisa Cohn, Julie Zhuo). Wait only for your motive or heat, not your nerves. Name your nervousness out loud (Julie Zhuo).
  • Just say thank you (Jules Walter) vs thanks is not enough (Kim Scott). Say thanks immediately; reward it with a visible fix.
  • Public, recorded, relentless critique (Dalio-style) vs Kim Scott: the latter calls it obnoxious aggression. Candor is judged at the listener's ear.

Deliverable

Produce this brief, filled in for the user's actual situation:

# Hard conversation brief: [person], [topic]

**Type:** [impromptu / recurring / performance gap / promotion / pre-exit / peer friction / receiving]
**Where I am on the 2x2:** [ruinous empathy / obnoxious aggression / manipulative insincerity / on target] because [reason]
**Outcome I want:** [one sentence]
**Motive check:** [helping / venting], my worry about myself: [one line]

## Evidence (camera-level facts)
1. [date, situation, behavior]  2. [...]  3. [...]

## The script (say it out loud once)
- Opener (notice + intent): [...]
- Observation / behavior: [...]
- Impact (my feeling or the result): [...]
- Tie to their goal: [...]
- Invite their view: [...]
- Ask / next step: [...]

## If they react
| Reaction | My line | Hold the point? |
|---|---|---|
| Defensive | [pause script] | yes |
| Angry | [curious question] | yes |
| Sad / crying | [care without retracting] | yes |
| Disagrees with facts | [list the pattern, ask what they heard] | yes |

## Logistics
Channel: [in person/phone] | When: [date] | Who else needs to know (HR, manager): [...]
Rehearsal: [mirror, then a trio with a partner and observer for net jumping]

## Next 3 actions
1. [Rehearse out loud and cut 90%]  2. [Hold the conversation by DATE]  3. [Follow-up check-in date and what I will look for]

Grade existing work

Score a draft message, script, or review 1-5 per criterion, total out of 40; return the top 3 fixes with the guest behind each.

Criterion135
Observable specificity (Alisa Cohn, Kenneth Berger)Labels and personality (you're careless)Some examples, mixed with judgmentDated, camera-level facts with a pattern
Net discipline (Carole Robin)Guesses at motives; says I feel likeMostly own side, some attributionOnly own intent, shared behavior, and own feeling
Care + challenge (Kim Scott)One only (all nice or all blunt)Both, but unbalancedExplicit care for their goals and a clear hard message
Clear ask or next stepNone; vague be more strategicSuggestion without owner or dateAgreed change, owner, deadline, follow-up (Alisa Cohn, Kenneth Berger)
Clarity of consequencesHint onlyStated softlyPlain statement plus belief in them (Claire Vo, Alisa Cohn)
Timing and channel (Kim Scott)Slack or email, weeks latePhone or video, delayedPrompt, synchronous, private
Reaction plan (Alisa Cohn, Kim Scott)None; would retract if upsetSome linesPause, curious, care-without-retracting lines ready
Two-way and follow-up (Kim Scott, Mihika Kapoor)One-way deliveryInvites responseAsks for their view, acts on feedback received, schedules check-in

Red flags

  • Ruinous empathy is where about 90% of our mistakes live (Kim Scott); softening a likable underperformer cost one team its best people.
  • Hinting. Passive-aggressive feedback is the worst kind (Anneka Gupta); I've gotten some feedback that you could improve is unkind (Claire Vo).
  • Net jumping: labels, you don't care, I feel like statements (Carole Robin, Rachel Lockett).
  • Slack, email, or a small video square for hard feedback (Kim Scott).
  • Asking for accountability as a speech; it triggers safety systems and facade compliance (Evan LaPointe). Ask questions instead (Varun Parmar).
  • Surprise firings. Founders who knew in month one and did nothing (Uri Levine); no 30-day conversation (Alisa Cohn).
  • Venting dressed as feedback (Alisa Cohn, Wes Kao).
  • Radical Candor as a license to be a jerk, or public relentless critique (Kim Scott).
  • Retracting when they look sad (Kim Scott), or arguing back when you disagree with feedback.
  • Never asking. Ask for the thing you hear in calibration rooms but never to your face (Jules Walter).

Receipts

  • "Radical Candor is just what happens when you care personally and challenge directly at the same time." — Kim Scott, Lenny's Podcast (00:04:04)
  • "I would say 90% of us make 90% of our mistakes in that ruinous empathy bucket. It's by far and away the most common problem." — Kim Scott, Lenny's Podcast (00:07:11)
  • "we don't understand that we are only privy to two out of the three. So I know what's going on for me, and I know what I did. I have no idea what happened on your end." — Carole Robin, Lenny's Podcast (00:44:04)
  • "I always ask my clients, what's my evidence that this is happening?" — Alisa Cohn, Lenny's Podcast (00:19:05)
  • "Simplest way to embrace the discomfort is to close your mouth and count to six." — Kim Scott, Lenny's Podcast (00:41:53)
  • "the most selfish thing you could possibly do, is withhold feedback that would otherwise be useful to someone because you don't want to be uncomfortable." — Matt MacInnis, Lenny's Podcast (01:11:49)

Go deeper

  • references/frameworks.md — every framework in this skill, how to run it
  • references/quotes.md — verified quotes with timestamps
  • Related skills:
    • influence — when the conversation is really about moving a stakeholder, not correcting behavior.
    • exec-comms — to rewrite the written follow-up or the escalation message.
    • career — when the conversation is your own promotion case or a job-move decision.
    • hire — when the answer is a role scorecard and a better-calibrated bar, not a harder talk.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Sets up how you and your team build and work with AI agents, and produces an Agent Workflow Charter (agent lanes, plan-mode loop, autonomy ladder with promotion criteria, rules file, review policy, security rules, rollout plan). Use when you ask 'how should we work with Claude Code / Codex / Cursor', 'how many agents should I run', 'should the agent be autonomous', 'plan mode', 'CLAUDE.md', 'AI-native team', 'roll out AI to my team', or 'my agent keeps screwing up'. Draws on 110 Lenny's Podcast guests incl. Claire Vo, Boris Cherny and Aishwarya Naresh Reganti.

日本語の概要は準備中です。原文の説明を表示しています。

menkesu/awesome-pm-skills4422026年10月6日 更新

Decide which AI features to build, delay, shelve or kill, and whether each one gets better as models improve. Produces an AI Bet Memo (feature-by-feature verdicts, retest triggers, scaffolding ledger, moat and safety check) from a roadmap or idea list. Use for 'AI strategy', 'AI roadmap', 'what should we build with AI', 'will the next model make this obsolete', 'build vs wait for the model', 'will OpenAI/Anthropic build this', 'agent or chatbot', 'is this feature worth shipping'. Draws on 118 Lenny's Podcast guests incl. Nick Turley, Kevin Weil and Dianne Penn.

日本語の概要は準備中です。原文の説明を表示しています。

menkesu/awesome-pm-skills4422026年10月6日 更新

Turns an idea into a working, user-testable prototype with AI builders (Lovable, v0, Bolt, Replit, Cursor, Claude Code) and gets you unstuck when the tool breaks. Produces a Prototype Brief with a build-prompt pack, a debugging log and a user-test plan. Use for 'vibe coding', 'build a prototype', 'prototype this feature', 'Lovable prompt', 'my AI builder is stuck', 'prototype instead of a PRD', or 'demo for users'. Draws on 44 Lenny's Podcast guests incl. Lazar Jovanovic, Zevi Arnovitz and Guillermo Rauch.

日本語の概要は準備中です。原文の説明を表示しています。

menkesu/awesome-pm-skills4422026年10月6日 更新

b2b-sales

無料

Builds a founder-led B2B sales motion - ICP and kill criteria, outbound message, first-call and demo plan, pilot and procurement plan, pipeline math, and a readiness check for your first sales hire. Use when you ask about founder-led sales, enterprise sales, cold outreach, ICP, 'why are deals stalling', pilots/POCs, procurement, 'when do I hire a sales rep', or adding sales to a PLG product. Draws on 49 Lenny's Podcast guests incl. Jen Abel, Geoffrey Moore and Pete Kazanjy.

日本語の概要は準備中です。原文の説明を表示しています。

menkesu/awesome-pm-skills4422026年10月6日 更新

career

無料

Turns a career question into a decision brief the PM can act on this week - a career plan, a promotion case, a stay-or-leave verdict, a job-search system, or an offer-negotiation script. Use when someone says 'how do I get promoted', 'should I leave my job', 'job search', 'I got laid off', 'negotiate my offer', 'career plan', 'IC or manager', 'next role', 'am I stuck', 'how do I stay relevant with AI' or 'how do I break into PM'. Draws on 188 Lenny's Podcast guests including Phyl Terry, Nikhyl Singhal and Deb Liu.

日本語の概要は準備中です。原文の説明を表示しています。

menkesu/awesome-pm-skills4422026年10月6日 更新

Runs a product quality review on a journey, feature, landing page, onboarding flow, or AI/agent surface and returns a friction log, a scored critical-journey review, and a taste bar your team can calibrate against. Use when someone asks is this good enough to ship, how polished should it be, why do users bounce, what is our quality bar, how do we build taste, or to review a design, prototype, onboarding, or checkout. Draws on 264 insights from 100 Lenny's Podcast guests incl. Katie Dill, Dylan Field and Stewart Butterfield.

日本語の概要は準備中です。原文の説明を表示しています。

menkesu/awesome-pm-skills4422026年10月6日 更新

menkesu のスキルをすべて見る

このスキルの問題を報告する