# Objection Handling: 9 Techniques for Responding to Pushback Canonical URL: https://headwayskills.com/knowledge/influence/objection-handling/ Markdown URL: https://headwayskills.com/knowledge/influence/objection-handling.md Entity type: Article Last updated: 2026-07-07 Language: en Primary audience: professionals improving influence at work Owner: Headway Skills Contact: https://headwayskills.com/contact/ ## Short answer Objection handling means hearing the concern out before you answer. Nine techniques for responding to pushback at work without getting defensive or caving. ## Key facts - Title: Objection Handling: 9 Techniques for Responding to Pushback - Category: Influence - Primary skill: Influence - Related skills: Communication, Building Resilience - Primary keyword: objection handling - Source page: https://headwayskills.com/knowledge/influence/objection-handling/ ## What this page covers - Objection handling means hearing the concern out before you answer. Nine techniques for responding to pushback at work without getting defensive or caving. - Practical guidance for objection handling - How this topic connects to Influence ## Detailed explanation You get to the end of [your pitch](/knowledge/influence/pitching-ideas/), and instead of a yes you get a "yeah, but." Your pulse goes up, and you start talking before they've finished the sentence. Objection handling is what you do in that moment — when someone pushes back on your idea, proposal, or product. Every established method — the four Ps, LAER, Listen-Ask-Reframe-Confirm — puts the same move first: hear the objection out completely before you answer. The response comes third or fourth. Never first. Which means the instinct you're fighting isn't a lack of good arguments. It's the speed of your own reply. ## What objection handling actually is An objection is not a rejection. It's the reason someone isn't saying yes yet, said out loud — and out loud is the useful part. The alternative is a polite nod and nothing happening. Most guides sort objections into four root categories: budget, timing, need, and authority. Salesforce and Indeed both use this taxonomy, and it travels well beyond sales. A manager who says "not this quarter" is raising timing. A colleague who says "I don't see the problem you're solving" is raising need. Someone who says "I'd have to run it past Maria" is telling you, politely, that Maria is the person you should have been talking to — [an authority objection](/knowledge/influence/stakeholder-buy-in/), which no amount of persuasion in that room will fix. That diagnosis matters more than any script. It tells you whether the conversation is winnable now, winnable later, or not yours to win at all. It's also worth knowing that objections arrive at every stage. Salesforce notes they show up as early as a first call and as late as final contract negotiation. The same holds for an idea at work: you'll hear pushback when you first float it, again when you write it up, and again when someone actually has to do the work. That isn't a sign the idea is dying. It's what a decision sounds like while it's being made. ## 9 objection handling techniques that hold up under pressure Nearly everything published on this topic is written for B2B sales reps — the vocabulary is prospect, deal, pipeline, close rate. That leaves a gap, because the same nine moves work when the person pushing back is your manager, a client, or the one stakeholder who can quietly kill your project. None of these requires you to be selling anything. ### 1. Let them finish, then wait a beat The most repeated instruction across every framework is the simplest: don't compose your reply while they're still talking. Highspot's playbook makes the mechanism explicit — the objection someone *ends* on is often different from the one they started with. People think out loud. "It's too expensive" becomes "it's too expensive for what we'd get in the first six months," which is a completely different problem with a completely different answer. Interrupt, and you spend your best material on the wrong objection. The deliberate pause afterward is the first P of the four Ps (Pause, Probe, Provide, Prove), and it reads as consideration, not hesitation. ### 2. Probe for the objection under the objection Ask a question before you mount a counter-argument. The stated objection is frequently a stand-in for something the other person hasn't articulated, or would rather not say directly — "the timing's bad" can mean anything from a genuinely full quarter to quiet doubt about whether you can deliver. A probe is really a diagnosis: you're working out which of the four root categories you're in. "What would have to be true for this to work?" gets you further than any rebuttal, because it makes them describe the conditions for a yes. ### 3. Mirror their last few words The cheapest technique in the set, and the one that needs no preparation at all. Gong documents it as a Chris Voss method: repeat the final three or four words of what they said, with a rising, questioning tone. "Not a priority right now?" That's it. No counter-argument, no clever reframe. The effect is that the other person elaborates — they fill the silence by explaining themselves further, and the explanation is the information you were missing. If you tend to freeze when challenged, this is the move to have ready, because it buys you time while looking like attentiveness. ### 4. Paraphrase it back before you answer Restate the objection in your own words and check that you have it right — the Acknowledge step in LAER (Listen, Acknowledge, Explore, Respond). Two things happen. The other person [feels heard](/knowledge/professional-behaviors/active-listening/), which lowers the temperature on both sides. And you get a correction if you were about to answer the wrong concern, which is a much cheaper mistake to catch now than after a four-minute response. If they say "no, that's not quite it," you've just been handed the real objection for free. ### 5. Reframe around value instead of defending the number Every top guide converges here: when the objection is cost, don't justify the price — shift to what the return is, what it saves over time, or what the alternative costs. But the sequence matters more than the move. The reframe comes *after* you understand the why, never instead of it. Reframing too early is just arguing with extra steps, and people can tell. Done in the right order, it's not a rhetorical trick; it's answering the question they were actually asking, which was about worth rather than price. ### 6. Prove it, don't just say it The four Ps keep Provide and Prove as separate steps on purpose. Provide is your tailored verbal answer. Prove is the evidence behind it — a case study, a data point, a named example, someone who's done it before. Most people stop after Provide and assume the point landed. It usually hasn't. Inside an organization, proof is often smaller than you'd think: last quarter's numbers, a comparable project on another team, or an offer to run it small first so the evidence generates itself. ### 7. Use feel, felt, found — carefully The oldest technique still in wide circulation: acknowledge how they feel, mention someone who felt the same, describe what that person found. It works because it removes the sense of being the only skeptic in the room. It's also the most detectable formula in the set. Skeptical listeners recognize the pattern, and it collapses badly if the example is invented — a vague "a lot of people felt that way" reads as manipulation. Only use it when you have a real, specific person and a real, specific outcome to point to. ### 8. Push back on the objection, not the person There's a failure mode opposite to [getting defensive](/knowledge/self-awareness/how-to-receive-feedback/), and it's more common in early-career professionals: agreeing too fast. You hear resistance, you don't want the friction, so you concede and the conversation ends without a decision. Shawn Casemore's 3 P's — Pushback, Pause, Propel — treats challenging an objection as a legitimate, ordinary move rather than an act of aggression, with one clear boundary: the pushback targets the objection's logic, never the person raising it. "Can I test that assumption?" is not rude. Silently folding isn't polite, it's just quiet. ### 9. Confirm it's actually settled The Confirm step in Listen-Ask-Reframe-Confirm, and the one people skip most. After you've answered, ask directly whether that addresses the concern. Silence is not agreement — it's frequently just the end of someone's willingness to argue. Unresolved objections don't disappear; guides note they resurface late, sometimes at the final stage, when it's far more expensive to deal with them. Thirty seconds of checking now saves you a resurrected objection three weeks later, raised by someone who now has other reasons to say no. Reading a list like this is the easy part. The hard part is running any of it while your heart rate is climbing and someone senior is looking at you — and whether you can do that depends less on technique than on what you already have underneath. If you're not sure, it's worth knowing [where your influence skills stand](https://assessment.headwayskills.com/) before the next conversation rather than after it. ## The skills sitting underneath a good response Look back at those nine techniques and notice how few of them are about arguing. Most are about listening, timing, and holding your nerve — which is why two people can know the identical framework and get completely different results from it. **Influence** — getting it and applying it — is where objection handling actually lives. The move is to understand what's in it for them before you pitch anything, present the drawbacks yourself rather than being caught hiding them, and go for a smaller win when the full yes clearly isn't available today. That last one matters most in your first few years: a scaled-down pilot you can point to next quarter beats a rejected proposal you can't. **Communication** supplies the receiving half. An objection is close cousin to expressing disagreement and to handling someone who's already annoyed — situations where the deciding factor is a genuine desire to understand the other person, not a sharper counter-argument. Giving full attention, moderating how long you talk, and knowing when a concern needs a conversation instead of another email round: that's the machinery behind techniques 1 through 4. **Building Resilience** is the half nobody puts in the playbooks. Pushback lands as rejection, and your reaction is often set before you open your mouth: event, automatic thought ("they think I don't know what I'm doing"), defensive reply. Naming that chain gives you somewhere to intervene mid-sentence. The thinking errors here are specific — mind reading, and all-or-nothing jumps where one "not now" becomes "this is finished." None of the three is a fixed trait, and none is rare. They sit among twelve work skills the free Work Skills Test measures, so if you want to know [which skill to build first](https://assessment.headwayskills.com/), that's where the answer is — and it's a more useful thing to know than another technique. Some of this probably already sounds like you. Maybe you're the one who listens well but folds at the first sign of friction, or the one who has the evidence ready and never gets asked for it because you talked over the question. Whichever it is, it's a habit rather than a limit — and habits are the changeable kind of thing. You don't need a different personality to handle an objection well; you need a sequence you trust enough to use when you'd rather just start talking. This gets more consequential, not less, as you go. The further into a career you get, the more of your work depends on people who are perfectly entitled to say no to you — and the less often anyone tells you that's the skill you're missing. The fact that you read nine techniques instead of grabbing one script for "it's too expensive" suggests you already suspect that. ## Find out which part is costing you So the only thing left is knowing which part of this is yours to work on. The Work Skills Test is a **free** 7-minute self-assessment of your work skills. It shows you where you stand across all twelve — including influence, communication, and resilience — and which ones would make the biggest difference to how your next difficult conversation goes. Not a score to file away; a starting point to work from. **[Take the skills test](https://assessment.headwayskills.com/)** *Free, and it takes about 7 minutes.* ## Who this is for - Professionals building practical workplace skills - Readers looking for specific, usable work advice - Managers, educators, and coaches supporting career readiness ## Common questions ### What is this guide about? Objection handling means hearing the concern out before you answer. Nine techniques for responding to pushback at work without getting defensive or caving. ### Which Headway skill does this connect to? This guide connects primarily to Influence. It also relates to Communication, Building Resilience. ### What is the recommended next step? Use the free Work Skills Test to reflect on which work skill to improve next. ## Related pages - https://headwayskills.com/knowledge.md - https://headwayskills.com/knowledge/influence.md - https://headwayskills.com/knowledge/communication.md - https://headwayskills.com/knowledge/resilience.md - https://headwayskills.com/work-skills-test.md ## Citation guidance Use the canonical page when citing this content: https://headwayskills.com/knowledge/influence/objection-handling/ Preferred summary: "Objection handling means hearing the concern out before you answer. Nine techniques for responding to pushback at work without getting defensive or caving." ## Change log - 2026-07-07: Content collection version published.