Emotional Intelligence and Relationship Building Questions

Active listening is the deliberate practice of fully attending to what someone is saying (and not saying), confirming your understanding out loud, and adjusting your response based on that confirmation, rather than letting sound reach your ears while you plan your next point. That distinction matters: hearing is passive and automatic, listening is active and effortful, and the difference shows up the moment you're asked to repeat back what someone just said and can't.

Behaviors by setting

In a group discussion (for example a cross-functional design review):

• Verbal: before adding your own view, paraphrase the previous speaker's point ("So the concern is that this adds a week to the migration, not that the approach itself is wrong, is that right?"). This closes a top source of group miscommunication: two people talking past each other because they never confirmed they heard the same thing.
• Nonverbal: visible note-taking and eye contact that rotates across all participants, not just whoever is talking loudest, signals you're tracking the whole room, which tends to draw quieter voices in.

In a one-on-one (for example a discovery call or a 1:1 with a teammate):

• Verbal: ask one open-ended follow-up per point instead of jumping to your own reaction ("What made that the priority over the other option?").
• Nonverbal: closing the laptop and silencing notifications. The single most common active-listening failure in 1:1s is multitasking, quietly reading email while nodding along, and it's usually detectable to the other person even when they don't say so, which erodes trust over time.

This matters most with an external partner, where there's no shared history to fall back on if you get it wrong, a misread there costs more than the same misread with a teammate you'll see again tomorrow.

Worked example
A prospect on a discovery call says "we need this to integrate with our CRM." A passive listener says "got it, we support that" and moves on. An active listener paraphrases first: "When you say integrate, do you mean data flows in automatically, or that your reps can trigger it manually from inside the CRM?" That one clarifying question, prompted by not assuming you understood, is often what prevents a churned renewal months later when the delivered integration doesn't match what was actually needed.

Trade-offs and pitfalls
Paraphrasing every sentence in a large meeting slows it down and can read as stalling, save it for decision points, not every utterance. And nonverbal cues without follow-through are hollow: nodding and taking notes builds no trust if you never act on what you captured, the behavior only reduces miscommunication when it's paired with a real change in what you say or do next.

The first five minutes of an angry-client call aren't for solving the problem, they're for proving you've registered the complaint and gathering the specifics needed to actually solve it: an opening acknowledgment, reflective statements, open questions, and only then a concrete next step.

Verbatim opening (first five minutes)
[0:00] "Thanks for getting on with me, I know you're frustrated, and I want to understand exactly what's happened before we talk about fixing it."
[0:30] Client explains three tickets submitted since the 3rd with no response.
[1:00] Reflective: "So to make sure I've got this right: three tickets since the 3rd, no response on any of them, and it's affecting your team's ability to hit their own deadline. That's a real miss on our end, and I'm sorry it went unanswered this long. I can also see this breached our response-time SLA (the response-time commitment in your agreement), and that's on us, not you."
[2:00] Open question: "Can you walk me through which of the three is most urgent right now, and what does resolved actually look like for that one?"
[3:00] Open question: "Is this the first time you've had a gap like this, or has it happened before?"
[4:00] Next step: "Here's what I'm doing: pulling up all three tickets right now while we're on this call, giving you a status on each before we hang up, and personally checking in with you in 48 hours regardless of where things stand. Does that work as a starting point?"

Trade-offs and pitfalls
Apologizing before reflecting the specifics back can feel hollow, a "sorry" with no evidence you understood what happened. Reflect first, then apologize for the specific thing you now understand happened. Promising a fix timeline you don't yet control, instead of a check-in commitment you do control, is a common overcorrection under pressure, don't commit to an outcome before you have the information to back it.

Direct answer

Address the jargon gap in the moment on behalf of the room, not any one confused person, and reinforce it afterward in writing so no one has to admit later that they didn't follow along.

Structured elaboration

In the moment, frame the pause as helping the group, not exposing an individual's gap: "Can we pause on [term] for a second? Not everyone here works with that daily, could you unpack it in one sentence?" This protects anyone who didn't understand from having to call themselves out.

In the follow-up, send a short recap to the whole group, not privately to the people you assume needed it, since singling anyone out defeats the purpose: a brief glossary of the terms used, each in one plain sentence, framed as a convenience for anyone catching up on the recording or notes later.

Worked example

In-the-moment phrase: "Can we pause on 'churn attribution model' for a second? Could you unpack that in one sentence for anyone not deep in this daily?"

Follow-up email: "Quick recap of a few terms from today's call, for anyone catching up on the notes or the recording.

Churn attribution model: the method used to decide which factor gets credit when a customer cancels, so 'price' and 'missing integration' can be compared rather than argued about.

Net revenue retention: what the customers we already had at the start of the period are paying us now, after upgrades, downgrades and cancellations, as a percentage of what they were paying then. Above 100 percent means the existing base grew on its own.

Cohort: a group of customers bucketed by when they signed up, so a change over time is compared like with like instead of against a base that keeps changing shape.

Useful context for the roadmap discussion next week." Three terms, one plain sentence each, in the order they came up on the call, which is what makes it read as notes rather than as a quiz. Sent to the full distribution list, not to a subset, so it reads as routine documentation rather than a correction aimed at specific people.

Trade-offs and pitfalls

Interrupting too often to ask for definitions can slow down a stakeholder who's used to a faster pace and make you look like you're not following the broader conversation, save it for terms that are actually load-bearing for the decision being made. And a follow-up email that reads as a lecture, rather than a convenience, undoes the goodwill from handling it gracefully live, keep the tone brisk and matter-of-fact.

When direct disagreement is culturally discouraged, real concerns show up as indirection, not silence: a qualified agreement ("that could work, maybe"), a question standing in for an objection ("have we considered timeline risk?"), or disproportionate quiet from specific people rather than the room overall. The fix isn't forcing directness, it's changing how you listen and how you ask so disagreement doesn't require someone to break a norm to voice it.

Adjusting how you listen

• Treat a qualified "yes" as incomplete information, not agreement, and follow up privately: "You said maybe, what's the maybe?"
• Watch for who goes quiet relative to their own usual participation, not just who's quiet overall, a normally vocal person going quiet on one specific topic is a stronger signal than a naturally quiet person's silence.
• Distinguish the type of misinterpretation before reacting: is the quiet indicating disagreement, uncertainty about whether it's their place to speak, or a language-comprehension gap in a fast meeting? Each needs a different follow-up (a private check-in, a direct invitation, or slowing down and restating).

Adjusting how you ask

• Replace yes/no questions with ones that presuppose a concern exists and ask what it is: "What's the biggest risk with this plan?" is easier to answer honestly than "Does anyone disagree?"
• Offer a written, asynchronous channel as a second path, some people who won't contradict someone live will write a direct concern in a follow-up document.
• In multi-country meetings, actively assign floor time by name across time zones rather than relying on whoever speaks first, otherwise the same few people in the convenient time zone dominate every call while others' input is muted by scheduling, not culture.

Ongoing practice
A recurring, low-stakes channel, an anonymous document or a rotating check-in, explicitly for concerns that didn't get raised live. When someone does surface a concern that way, visibly act on it (crediting them if they're comfortable), so the norm builds on evidence rather than a promise that speaking up costs nothing.

Worked example
On a multi-country account team, an engineer in one region kept saying "no problem, we'll manage" about an aggressive timeline. Reading the qualified tone as incomplete, the account lead followed up privately and learned "we'll manage" meant unpaid overtime, not that the timeline was actually fine. Raising the concern in the next call as the lead's own observation, rather than attributed to the engineer, got the deadline moved without anyone having to publicly contradict the plan.

Trade-offs and pitfalls
Over-applying this becomes its own problem, treating every "yes" as suspect erodes trust with people who genuinely mean it. Calibrate to the specific person over time rather than assuming an entire culture behaves one way, individuals vary more than any stereotype does.

Using the STAR structure (Situation, Task, Action, Result):

Situation: mid-sales-cycle call with a prospect who'd been burned by a previous vendor's overpromising. They opened the call visibly guarded, short answers, arms crossed on video.

Task: earn enough trust in a single 30-minute call to get past generic skepticism into a real conversation about their actual needs.

Action: instead of launching into the pitch, I named the pattern directly: "It sounds like you've been sold something before that didn't hold up, what happened?" and then just listened, using minimal verbal encouragers and no interruption, for their full account. I mirrored their more clipped, direct style rather than my usual more expansive one, and I deliberately underclaimed rather than overclaimed: "I won't promise this solves everything you just described, here's specifically what it does and doesn't do." When they brought up the same broken timeline promise that had burned them before, I reflected it back before responding: "So the timeline commitment itself is the sensitive point, not just whether the product works."

Result: by the end of the call their posture and tone had visibly shifted, arms uncrossed, longer answers, and they proactively asked to bring in a technical stakeholder for the next call, something they'd resisted earlier in the cycle. The deal closed, and in the post-sale kickoff the client specifically named "you were the first vendor call where I didn't feel sold to" as the reason they moved forward, the qualitative signal that listening, not the pitch, drove the outcome.

Trade-offs and pitfalls
Underclaiming feels counterintuitive when the instinct is to build excitement, but with an already-skeptical buyer, matching their skepticism with honesty builds more trust than optimism does. Mirroring someone's guarded style too literally can come across as cold if overdone, calibrate it rather than mimicking them exactly.