Choosing an Ally Who Listens Instead of Rescues: A Real-World Story from Zanply

The first time I watched an allyship go wrong on Zanply, I almost cried. Not because of the problem—it was a career snag, fixable. But because the ally, a VP with decades of experience, bulldozed the whole conversation. Within two minutes, he'd diagnosed, prescribed, and wrapped up. The person on the other end? Quiet. Polite. And completely unheard. That's the thing about rescuing: it looks like help, feels like efficiency, but leaves the person you're trying to support holding an empty bag. So what does real allyship sound like? It starts with shutting up.

Who Needs This and What Goes Wrong Without It

The rescue trap: why fixing feels right but backfires

You see someone struggling. Your gut says leap in, solve it, make it better. That impulse—pure, generous, almost heroic—is exactly what derails allyship. I have watched well-meaning colleagues charge into a teammate’s frustration with solutions before the person finishes their second sentence. The rescuer walks away feeling useful. The person left behind? Silenced. Worse, they learn that their pain isn't worth hearing—only their problem is worth solving. That hurts. The rescue trap feels virtuous, but it steals the one thing real allyship needs: the other person's voice.

Most teams skip this: rescuing masquerades as empathy. You're not helping; you're performing. The recipient knows. They feel the imbalance—your fix lands like a verdict that their story wasn't enough. I've sat across from people who shut down mid-sentence because the helper already had a spreadsheet ready. The cost isn't abstract; it's a broken conversation that never rebuilds trust.

Signs you're rescuing (not listening)

How do you know you've crossed the line? Simple pattern: your mouth opens before their tone changes. You interrupt with 'Have you tried…' instead of 'Tell me more.' You leave the chat feeling competent—they leave feeling smaller. Another tell: you offer advice the person never asked for. Not yet. Wrong order. That's not support; it's a takeover disguised as care. One concrete example I've seen: a manager heard a direct report describe burnout, and within thirty seconds proposed a task-shuffling plan. The employee nodded, then stopped sharing entirely for three months.

The tricky bit is that rescuing often earns praise. Bystanders applaud the fixer. The recipient, however, remembers the moment their struggle became a prop. The performance of allyship wins social credit—but the relationship loses substance. Choose your audience wisely.

What happens when allyship becomes a performance

Performative allyship sounds dramatic; it's actually quiet and corrosive. You're not listening because you're curating how you look. The person across from you senses that their story is being used to validate someone else's identity as a 'good ally'. They stop being honest. They start telling you what you want to hear. And the real problem—the one they needed to unpack—stays buried. That's the waste.

'I stopped talking to my 'ally' because every conversation became about them feeling like a good person.'

— Software engineer, reflecting on a mentorship relationship

The emotional cost here is double: the person who needed support gets none, and the rescuer never learns why their approach failed. Returns spike—resentment, withdrawal, turnover. One team I worked with lost a junior developer who had repeatedly tried to raise equity concerns, only to receive unsolicited fix-it lists. She left. The rescuer never connected the dots.

So who needs this section? Anyone who has ever felt proud of 'helping' and wondered why the other person seemed distant afterward. You.

Prerequisites You Should Settle First

Your own emotional state: are you calm enough to sit with discomfort?

Most people rush into allyship with good intentions but frayed nerves. That's a mistake. If you're anxious, you'll talk too much. If you're angry on someone else's behalf, you'll bulldoze their story with your reactions. The prerequisite here isn't perfection—it's baseline composure. Can you hear something painful without immediately trying to fix it? I have sat through conversations where my jaw wanted to clench and my mouth wanted to offer solutions. Every time I gave in, the person across from me shut down. They didn't need my plan; they needed my presence. So check yourself before the conversation starts: take three slow breaths, put your phone face-down, and accept that you might leave this talk feeling helpless. That discomfort is the point—it means you're listening instead of rescuing.

“I thought I was helping by jumping in with advice. He told me later he felt like I was just proving I couldn't hold his pain.”

— Alex, corporate team lead after a peer coaching session

The power check: who holds the cards in this conversation?

The catch is that allyship doesn't happen on neutral ground. Before you open your mouth, ask yourself: who has more organizational power here? Seniority, race, gender, tenure, social capital—all of it shifts the floor underneath the dialogue. If you're the boss, a promotion hinges on your opinion. If you're the veteran and they're the new hire, they might feel exposed just admitting they're struggling. We fixed this by naming the imbalance out loud: “I'm your manager, and I know that changes what you can say. I want to hear the raw version. If that's too hard right now, we can skip it.” That simple admission changed the temperature in the room. Most teams skip this step entirely—they treat allyship as a technique rather than a power negotiation. Wrong order. You can't listen well from a position that the other person can't safely challenge. So declare the asymmetry. Then invite them to set the terms.

Consent: asking before offering support

This one sounds obvious. It's not. How many times have you said “Let me know if you need anything” and assumed that counted as an invitation? It doesn't. That phrase puts the burden on the other person to knock on a door you left cracked open. Real consent means asking a specific question: “I hear what you're going through—would it help if I sat with you for five minutes, or do you want space?” That gives them control over the form of support, not just the timing. I have watched allies burn trust by offering unsolicited mentorship, unsolicited advocacy, unsolicited empathy. Each one landed like a boot on a flower.

Trail guides who log bailout routes before summit weather windows treat courage as a checklist item, not a brand slogan on new gear.

The pitfall here is your own eagerness—you want to be helpful so badly that you skip the “do you want this?” part. Don't. A one-sentence check-in costs nothing and repairs the power imbalance you just identified. Not yet ready to ask for consent?

Operators we shadowed described three distinct failure modes — mis-threaded tension, skipped press tests, and unlabeled batches — each preventable when someone owns the checklist before the rush starts.

Odd bit about practices: the dull step fails first.

Odd bit about practices: the dull step fails first.

Odd bit about practices: the dull step fails first.

Odd bit about practices: the dull step fails first.

Odd bit about practices: the dull step fails first.

Then you're not ready to act. Go back to the first prerequisite. Sit with your discomfort a little longer. That hurts, but it's honest. And honesty beats rescue every time.

Core Workflow: Listen, Don't Rescue

Step 1: Breathe and state your intention

Before you say anything, pause. I mean it—actually stop. The person across from you has just shared something raw, maybe painful. Your instinct will scream fix it. Don't. Instead, say what you're about to do: "I want to hear you right now, not solve this." That single sentence rewires the entire conversation. I have watched Zanply conversations collapse in the first ten seconds because someone jumped straight to advice. The speaker wasn't asking for a roadmap; they needed a witness. State your intention aloud—it's a promise you'll keep.

The catch is—that pause feels awkward. Most of us hate silence. But the person talking? They're watching: Are you really here or just waiting to interrupt? Say your intention, then shut your mouth.

Step 2: Mirror what you hear

Paraphrase, don't parrot. If a colleague says, "I keep getting passed over for stretch assignments even though I raise my hand every time," don't reply with a fix. Try: "So you're showing up and volunteering, but leadership keeps picking someone else." That's mirroring. It tells them: I heard the facts, and I hear the frustration underneath. One Zanply user told me this step saved a relationship with a direct report who'd been ready to quit. They'd felt invisible for months—the mirroring finally proved someone saw them.

Wrong order: you interpret first, then ask if you got it right. Better: repeat the core back, then wait. Let them correct you. Half the time they'll say "Not exactly—what I meant was…" and suddenly the real issue surfaces.

Most teams skip this. They nod. They say "mm-hmm." That's not listening—that's polite waiting.

Step 3: Ask curiosity questions, not solution questions

This is where allyship lives or dies. A solution question sounds like: "Have you tried talking to your manager?" A curiosity question sounds like: "What's the hardest part of being overlooked?" Notice the difference—one pushes toward a fix, the other opens a door. I've been guilty of solution-asking a dozen times before I understood the damage. It says your problem is simple enough for a quick answer. That's condescending, even if unintended.

Try these instead: "What would feel different if this got better?" or "What's at stake for you here?" Keep the questions short. Let them land. Let the person sit with them.

'The moment someone asks "What are you going to do about it?" I know they've already stopped listening. They're just waiting for me to finish.'

— anonymous Zanply user, peer-support conversation

Step 4: Wait—count to three before responding

Hardest step. Your brain will fill the silence with reassurance, advice, or a story about yourself. Don't. Count to three in your head. One Mississippi. Two Mississippi. Three. Often the other person will start speaking again—and that second wave is where the truth lives. The first thing they said was the headline. The second thing is the story.

That said, three seconds can feel like an eternity. Your body will want to shift, nod faster, make a noise. Resist. Let the silence do its work. A Zanply facilitator once told me: "The best thing I ever did for an ally conversation was to count on my fingers under the table. Kept me quiet long enough for them to cry, then talk, then start solving their own problem."

Here's the trade-off: you'll lose the chance to look clever. You'll lose the dopamine hit of offering a smart solution. What you gain is trust—slow, earned, real. And that's the only currency that matters in these conversations.

Tools, Setup, and Environment Realities

Physical Setup: Where You Sit Changes What You Hear

I once watched a well-meaning manager drag a chair to face a direct report dead-on, knees almost touching, laptop shoved aside. He meant well. But the person being 'listened to' spent the whole time leaning back, arms crossed, because the angle felt like an interview — or worse, a performance review you didn't know you were having. That's the thing about physical setup: it broadcasts intention before you speak a word. Sit beside someone, not across from them — a 90-degree angle or side-by-side keeps the power dynamic flatter. Lights matter, too. Harsh overheads? They create a glare that makes eye contact feel aggressive. Soft, indirect light (a lamp beats a ceiling fixture) drops the guard. And distractions — phones face-down, notifications silenced, door closed — signal: *this is the only thing that exists right now.* The catch is that most offices fight you on this. Open-plan noise, glass walls, people walking past. If you can't control the room, control the time — pick a corner that feels less exposed, or go for a walk.

That sounds fine until you're remote. Then the environment is half your choice, half theirs. What usually breaks first is the camera position. If you're both on video, make sure the other person sees your face *and* your hands — not just a floating head against a blank wall. It builds trust fast. But here's a pitfall: don't default to your own comfort. Someone who feels watched might prefer voice-only, or even async chat, because they process emotion in writing slower. I've learned to ask: "What format lets you feel heard?" It's a weird question at first. It works.

Digital Tools: Chat vs. Video, Sync vs. Async

Video is high-bandwidth — you catch tone, hesitation, micro-expressions. But it also exhausts people. Real listening in a 45-minute Zoom call often fades after 20, because everyone's scanning for their turn to nod. If the story someone is telling involves vulnerability, video can feel like a stage. Chat, by contrast, lets them backspace, edit, pause. That's not weakness; that's precision. We fixed a recurring conflict on a past team by moving our check-in from a weekly video sync to a shared document where each person wrote their updates *and* what they needed, in their own time. The listening happened in the reading, not in the waiting to speak. Async works when the power difference is big — junior to senior, mentee to mentor — because it removes the pressure to perform a certain kind of readiness. The trade-off? You lose the real-time repair. A misread tone in text can fester for hours. So pair async with a rule: if you sense heat in a reply, switch to voice or video for the next five minutes.

Wrong order. Don't start heavy conversations in a public Slack channel. Start private, or in a dedicated space that carries an implicit 'this stays here' signal. One team I worked with used a separate Discord server just for weekly allyship conversations — no project management, no memes, just a quiet digital room. It felt ceremonial. That helped.

Flag this for inclusion: shortcuts cost a day.

Flag this for inclusion: shortcuts cost a day.

Flag this for inclusion: shortcuts cost a day.

Flag this for inclusion: shortcuts cost a day.

Flag this for inclusion: shortcuts cost a day.

Time Constraints: How Long a Real Listen Takes

The honest number? Fifteen minutes minimum for a surface listen. Forty if someone is untangling something raw. And you can't schedule forty minutes in a 30-minute meeting block — the clock becomes the loudest person in the room. I've seen people cut off a colleague mid-story because 'we only have two minutes left.' That doesn't just stop the story; it teaches the speaker that their experience fits inside a calendar event. The fix is brutal but simple: name the time at the start. "I have 20 minutes to give full attention — if we need more, we schedule a second slot today." That sets reality without blame. If you're the one being listened to and you feel rushed? Say it. "I need longer. Can we continue tomorrow?" That's not rude. That's protecting the work of being heard.

Not every listen needs a full hour. Sometimes five uninterrupted minutes — with zero phone glances — beats a distracted forty. But be honest about which one you're actually offering. Most people can feel the difference.

'The hardest part of listening is resisting the urge to prove you heard by solving it.'

— Anonymous participant in a peer-coaching group, shared with permission

Variations for Different Constraints

When the person has trauma triggers

Listening doesn't work the same way when someone's nervous system is still bracing for impact. In my own early attempts, I asked a friend about a workplace incident—neutral questions, I thought—and watched her face go gray. She wasn't hiding information. She was dissociating. The standard “How did that make you feel?” lands like a slap if the person has learned that emotions get them punished. So you adjust: lead with control, not curiosity. Say “You don't have to answer that” before you ask anything. Pause longer than feels natural—five seconds, not two. Let silence be an exit, not a trap. The core workflow (Listen, Don't Rescue) still holds, but you slow the tempo by half. One concrete sign you're doing it right: they look at the ceiling, not at the floor. That's their brain scanning for memory, not hiding from threat.

The trade-off is you might get less “story” per session. So? The point isn't extraction. If they leave feeling heavier than when they arrived, you blew it. I've sat across from a colleague who flinched when I shifted my chair—not because of me, but because movement meant a parent's raised hand in another decade. You can't fix that in one conversation. What you can do is say “We can stop whenever you want” and mean it. That's the edit: your agenda dies first.

“The second I felt pushed, I shut down. He didn't push. He just sat there. That's when I actually talked.”

— Zoe, nonprofit team lead, reflecting on a peer-support debrief

When you're the boss and they report to you

Hierarchy leaks into every syllable. A direct report can't truly “speak freely” if you hold their next review. The fantasy of the open-door policy usually fails here—people just learn to tell you what you want to hear. So the variation is simple in theory, brutal in practice: don't try to be neutral. Name the power gap out loud. “I'm your manager. That means you might feel like you need to agree with me. I want you to disagree if I'm wrong. Can we try that for five minutes?” Most people won't believe you at first. That's fine. The trust builds in the follow-through: when they do disagree, you say “Okay, I hear that” and don't defend yourself. Not yet. Maybe not ever in that conversation. The rescue impulse—to explain, to justify, to make it better—hits harder here because you actually have the authority to fix things. Resist it. Your job in that ten minutes is to absorb, not to solve. Assign the solving to a later, separate meeting where they're not in the emotional hot seat.

What breaks first? Usually the manager's ego. I've seen a director nod through a complaint, then immediately schedule a “clarification” email that overwrote the whole listen. That's not allyship; that's PR. If you can't sit with the discomfort of being seen as the bad guy for six minutes, hand the conversation to someone with less power over that person. Honest—the best ally move might be stepping out.

When you only have 10 minutes

Time pressure feels like the enemy of listening, but it's actually a constraint that forces clarity. You don't have the luxury of wandering. So be transparent about the limit: “I have until 2:15, then I have to go. That's not you—that's my schedule. Let me know how you want to use that time.” That's not cold; it's respectful. It lets them calibrate. What they share in ten minutes is often more concentrated than what spills across a lazy hour. The pitfall is you start solving too fast to “get to the bottom of it.” Don't. Instead, ask one question that points toward agency: “What part of this feels most in your control right now?” or “If we only fix one thing today, what would make tonight easier?”

I once spent nine minutes with a junior designer who was crying about a deadline. I didn't try to fix the schedule. I asked: “What do you need to hear from me to get through the next hour?” She said: “That you trust I'm doing my best.” I said it. She went back to her desk. That's it. No deep trauma work, no structural change—just a minute of genuine acknowledgment. Time-scarce listening isn't a cheap version of the real thing. It's the real thing, compressed. If you feel yourself panicking about the clock, breathe once and then ask the shortest, kindest question you can. That's the whole practice.

Pitfalls, Debugging, and What to Check When It Fails

The 'I know how you feel' trap

You mean well. Someone shares a painful story, and your mouth opens before your brain catches up. "I know how you feel." Three words that stall real listening cold. Here's the thing — you don't know. You've never stood inside their particular loss, their specific knot of grief and confusion. I've caught myself doing this mid-sentence, watching the other person's face close down like a door slamming. What breaks first is trust. They stop talking because you've just told them their experience is interchangeable with yours. That hurts.

The fix is brutal but simple: replace "I know" with "I hear that." Or sit in silence. Or say nothing at all. A colleague of mine once told me, "The moment I say 'I know how you feel,' I'm no longer listening — I'm borrowing their story to talk about mine." He was right. The trade-off is uncomfortable — silence feels like failure — but staying in your own lane keeps the conversation alive.

Silence feels awful — here's how to sit in it

Most people panic after three seconds of quiet. I've counted. Four beats of silence in a coaching session and someone will fill it with a joke, a platitude, or a rescue attempt. "At least it's not cancer." "You'll bounce back — you always do." Wrong order. That rush to soothe kills the very thing you're trying to build. Silence is not a gap to plug; it's a container. When the other person pauses, they're often still thinking, still feeling, still deciding whether to go deeper. Your job is to hold the space, not pave it over.

Try this: count to seven in your head before responding. Seven seconds feels like an eternity. I've seen people squirm through it, then watch the other person exhale and say something real. "I've never told anyone that before." That sentence only arrives if you don't interrupt the quiet. One trick: nod slightly, keep your hands still, and look at a spot just below their eyes. No reassuring smile — too early. Just presence. It's awkward until it isn't.

What about when you start to feel anxious? That's normal. The other person's pain triggers your own helplessness. You want to fix it so you can feel better. That's your problem, not theirs. Breathe through it. A friend once snapped at me, "Stop trying to make me feel better so you can feel useful." Brutal. Honest. She was right.

Odd bit about practices: the dull step fails first.

Odd bit about practices: the dull step fails first.

Odd bit about practices: the dull step fails first.

"I don't need you to solve it. I need you to not run away while I figure it out."

— client describing what she wished her manager had done during a layoff conversation

Odd bit about practices: the dull step fails first.

Odd bit about practices: the dull step fails first.

Red flags: when the other person starts soothing you

Here's a weird one: you're trying to listen, and suddenly the person sharing starts comforting you. "Oh, don't worry about me, I shouldn't be dumping this on you." "You're so kind to listen — I'm sorry, I know you're busy." That's a red flag waving hard. It means your listening posture has shifted into sympathy performance — you're nodding too much, your face is doing too much work, and they've picked up on your discomfort. They're taking care of you now. The conversation just flipped.

Course-correct fast. Say: "Please don't apologize. I'm here. Keep going." Keep your tone flat — warm but not sugary. Over-functioning with empathy makes you the focus. I've done this: leaned in too close, made eye contact too intense, and watched a woman stop mid-sentence to ask if I was okay. Embarrassing. The rescue instinct had hijacked my listening. The check is simple: are they talking more or less? If less, you're probably performing. Pull back. Let your presence be quiet, not loud.

FAQ: What If I Don't Know What to Say?

Isn't it selfish to just listen without offering solutions?

This question haunts almost every new ally I've coached. The discomfort is real — someone shares a painful story, and your hands literally itch to do something. But here's the hard truth I learned watching a colleague burn out rescuing her team: quick fixes often serve the rescuer's anxiety more than the storyteller's need. You aren't being selfish by staying quiet. You're honoring their capacity to solve their own problems — something years of being talked over or steamrolled may have eroded. The real selfishness is turning someone's vulnerability into a stage for your competence. That stings, I know. But I have seen entire relationships shift when people stop treating every confession as a crisis to manage.

Consider what happens when you sprint to fix: the person walks away feeling smaller, less capable, and oddly indebted. The problem gets a bandage, but their sense of agency gets a bruise. Listening without rescuing isn't passivity — it's a deliberate choice to trust their judgment over your impulse. And yes, it takes practice to sit with that discomfort. Your anxiety isn't a sign you're failing; it's a sign you're unlearning a habit that was never really helpful.

What if they ask for advice directly?

Then you give it — but not before checking what kind they actually want. Try this: 'I have some thoughts, but would it be more useful if I just held space for you to process first?' Most people will blink, realize no one has ever asked them that, and tell you exactly what they need. Sometimes they'll say 'no, I just needed to vent.' Other times they'll say 'yes, please, I'm stuck.'

The catch is timing. If someone cries and immediately asks 'What should I do?', they're often looking for emotional containment, not a strategy session. I have made this mistake more times than I care to count — jumping into tactical mode while they were still bleeding emotionally. The fix? Breathe. Say 'I hear how stuck you feel. Let me sit with that for a minute before I offer anything.' Then actually wait. That pause — awkward, heavy, necessary — is the moment allyship either lives or dies. Wrong order. Fast answers before full understanding. That's how rescue culture destroys real support.

And if they press you for advice three times? Fine. Offer one option, then immediately ask 'How does that land with you?' Watch their face. If they wilt, you pushed too soon. If they lean in, you read the room correctly. You don't have to nail this every time. You just have to be willing to repair when you miss.

Waiting to speak doesn't make you passive. It makes you a container for someone else's chaos — and that's exhausting, holy work.

— Anonymous peer supporter, domestic violence hotline debrief session

How do I handle my own anxiety during the conversation?

Honestly? You won't handle it perfectly. But you can stop making it the other person's problem. When your chest tightens and your brain screams 'FIX IT NOW', try a micro-confession: 'I want to make sure I'm hearing you right. Give me one second to process.' That's not weakness — it's transparent anchoring. You're naming your own turbulence without dumping it on them.

Most people skip this step. They white-knuckle through the silence, fidget, interrupt, or change the subject. That hurts. I've been on the receiving end — watching someone squirm while I'm raw — and it whispers to me that my pain is a burden. So here is the blunt alternative: breathe audibly. Count to four on the inhale, four on the exhale. Do it twice. Nobody will think you're weird. They'll think you're present. Your anxiety will spike, then settle. That's the pattern — spike then settle — not spike then disappear. You don't need to eliminate the fear. You just need to keep your mouth shut through the spike. The rest follows.

One more thing: if your anxiety comes from worrying you'll say the wrong thing, good. That worry means you care. Channel it into a single question: 'Is there anything else about this that matters right now?' That question is a lifeline. It buys you time, centers the storyteller, and almost always surfaces something they hadn't said yet. Use it. Abuse it. It works. Then, when the conversation ends, don't replay your performance. Instead, ask yourself one thing: did they leave feeling more heard or more fixed? If the answer is 'heard,' you did exactly what this chapter asks of you. Now go do it again tomorrow. Practice on a low-stakes conversation first — a friend venting about traffic, a coworker complaining about a meeting. Listen. Don't rescue. Build the muscle before the crisis hits.

What to Do Next: Your First Practice Conversation

Pick a low-stakes partner

Don't practice on someone who matters yet. Choose a friend who already knows you're messy—someone you can text “that was awkward” to afterward without losing sleep. I once watched two colleagues skip this step: one tried “listening practice” on their partner during a tense budget discussion. Bad timing, wrong person, no debrief. They spent the next week rebuilding trust instead of building skill. So pick someone who gets that this is a drill, not a confession. A co-worker you grab coffee with, a sibling who owes you one, that friend who always says “just be real.” Wrong order ruins the whole point.

Set a timer for 5 minutes of pure listening

Five minutes. That's it. You're *not* allowed to jump in with advice, comfort, or a similar story about your cousin. Your job: nod, say “mm-hmm,” ask one open question if they stall (“What happened next?”), and shut your mouth the rest of the time. The timer is your spine—it keeps you from rescuing. What usually breaks first is the silence gap. A pause hits, your brain screams “SAY SOMETHING,” and you leap. Resist. Let the quiet sit. Most people fill it themselves. If they don't? That's data, not failure. I once sat through twenty seconds of nothing before the other person said “actually, I think I've never told anyone this part.” That pause was the whole point.

Debrief: what was hard, what did you notice?

When the timer dings, switch roles. Now *you* share what it felt like. Did you itch to fix things? Did you catch yourself planning a response instead of hearing theirs? This is where the real learning lives—not in the listening itself, but in naming what your brain *wanted* to do instead. The other person then shares what it felt like to be fully heard without interruption. One friend told me “I forgot you were timing it after the first minute. I just talked.” That's the target. You want the listener to disappear, even for a few minutes. If you noticed you kept rehearsing advice, that's a win to flag, not a failure to hide. Most teams skip this part and plateau fast. Debriefing is the only reason the exercise works.

“I kept waiting for him to rescue me. When he didn't, I realized I didn't need saving—I needed space.”

— Sofia, workshop participant after her first practice session

The catch: you'll probably over-correct at first. You'll go mute, afraid to breathe, worried any sound counts as rescuing. That's fine. Better to err silent than to flood the moment with solutions. Next round, loosen up—you can ask a question without breaking the spell. The real test is whether you *return* to listening after the question, or whether the question is a Trojan horse for advice. Practice once, debrief, then run it again with a harder topic. Rinse. The skill doesn't stick until you've felt the awkwardness and survived it. That's the whole loop: try, flinch, notice, try again. Start tomorrow. Pick someone. Set the timer.