Influence and Persuasion Questions

Situation: I needed the Support team to invest time in a new escalation process, but I had no formal authority over them.

Task: My job was to earn their support instead of asking for compliance.

Action: I started by learning what mattered to them. I met with the support manager and a few frontline agents to understand their pain points. The main issue was that they were already overloaded, so any new process had to save time, not add work. I then reframed my initiative in their language. Instead of talking about my project milestones, I showed how the change would reduce repeat tickets and make it easier to resolve customer issues on the first contact. I also offered a small pilot so they could test the idea before committing fully.

Result: Because I tied the request to their goals and reduced the burden, they agreed to participate and became active partners in the rollout.

What I learned is that influence comes from understanding the other function’s priorities, showing respect for their constraints, and making the benefit concrete.

Direct answer

When the blocker is skepticism, not a lack of information, the fastest way through it is to give people something to react to instead of something to be convinced of: a working prototype, a runnable demo, or a scoped pilot that lets them see the outcome rather than take your word for it. The artifact does the arguing; you just have to build the right one for the specific doubt in the room.

Structured elaboration

Step 1: diagnose the shape of the skepticism before picking an artifact. "I don't believe it" comes in different flavors, and the wrong artifact wastes the build effort:

Step 2: design the artifact around the objection, not around what's easiest to build. Scope it to the smallest thing that resolves the specific doubt, timebox it, and agree on pass/fail criteria before you start building, ideally with the skeptic's input, so the result isn't yours to spin.

Step 3: know where this can backfire. A demo built to impress rather than to test invites the objection "that's not how it'll behave in production." A notebook you hand over to build trust can just as easily hand ammunition to an opponent if it surfaces an edge case you hadn't accounted for. A pilot with too small a sample or a novelty effect can look causal and not be. Build the artifact to survive scrutiny, not just to look good once.

Worked example

Situation: a data science team built a new lead-scoring model intended to replace the manual process Sales used to decide which inbound leads to call first. Product also had to sign off, since routing the score into the CRM meant committing engineering time away from the roadmap. Neither audience would take "the model scores well offline" as sufficient: Sales trusted their own read on which leads convert, and Product didn't want to fund an integration for a metric that might not move revenue.

The pilot: rather than opening with the model's offline accuracy numbers, the team proposed a one-month randomized pilot. Every new inbound lead was randomly assigned, evenly, to one of two queues: the existing manual triage order (control) or the model-ranked order (treatment). Reps worked whichever queue they were assigned and were not told which queue was which. This is the deliberate causal design piece: random assignment is what lets a difference in outcomes be attributed to the model rather than to which reps happened to get the stronger leads that month.

Pinned inputs: 800 leads entered the pilot, split 400 to each queue by the randomization. The control queue converted 52 leads to a qualified opportunity. The treatment queue converted 71.

$$\text{Control conversion rate} = 52 / 400 = 13.0\%$$ $$\text{Treatment conversion rate} = 71 / 400 = 17.75\%$$ $$\text{Relative lift} = \frac{17.75 - 13.0}{13.0} \approx 36.5\%$$

Presenting to Product and Sales required two different framings of the same result. For Sales, the pitch led with what a rep actually cares about: working the model-ranked queue closed proportionally more leads for the same headcount and the same hours worked that month, which answers "will this replace my judgment with something worse" with results instead of an abstract accuracy score. For Product, the pitch led with the causal design itself: because assignment was random, the lift could be attributed to the model and not to seasonality, a strong sales month, or which reps happened to be on which queue, which is what justified spending engineering time on the full CRM integration rather than commissioning another manual audit of the leads process.

What a senior person does differently: they design the pilot's comparison before building anything (a held-out or randomly assigned control group, not a before/after on the same population), they pick pinned inputs and show the arithmetic rather than asserting a final lift number, and they prepare two distinct framings of the identical result for Product and Sales rather than one deck that tries to land with both.

Resolution: Sales agreed to route new leads through the model by default going forward, and Product approved the CRM integration in the next sprint. The causal design was what made the result durable: had the comparison been a simple before/after on the same population instead of a randomized control, either team could have credibly attributed the lift to a stronger sales month rather than to the model.

Trade-offs & pitfalls

• Building a good artifact costs real time; it only pays off when the resistance is genuinely about evidence, not about competing priorities or politics. A prototype won't fix a stakeholder who has a different agenda.
• A rehearsed demo and a reproducible artifact earn different kinds of trust: a scripted demo is faster to build but easier to distrust; a notebook or environment the audience can rerun themselves is slower to prepare but harder to dismiss.
• An artifact-driven win still needs a path to the actual ask. A convincing demo that nobody follows up on just becomes "a nice thing we built once."
• Watch for optimizing the artifact for the happy path. If the skeptics' real objection is an edge case, a demo that avoids it doesn't persuade, it confirms the suspicion that you're not taking the concern seriously.

Direct answer

In the moment, the sequence is acknowledge, then a tight piece of evidence, then a small concrete next step, not a bigger version of the argument that just got dismissed. The goal in the room is not to win the disagreement outright, it's to convert "I'm not convinced" into "let's find out," while leaving the executive's standing in the room intact.

Structured elaboration

The three-step in-room conversation plan. When a VP publicly disagrees and is skeptical of your evidence, the structure that reliably works is: (1) opening, an acknowledgment that takes the concern seriously rather than defending immediately; (2) presenting evidence and reframing, concise, specific, and aimed at exactly what they said was unconvincing, not a restatement of everything you already said; (3) reaching agreement in the room, a small, low-risk next step both people can say yes to right now, rather than asking them to simply change their mind.

1. Opening: acknowledge specifically, not generically. "I hear you, that concern about X is fair" lands better than a vague "I understand your point."
2. Evidence and reframing: two or three sharp points, tied directly to what they said was weak, not a restatement of the original pitch.
3. Reaching agreement: propose a bounded next step (a short pilot, a follow-up with specifics, a narrow test) with an explicit exit condition if it doesn't hold up, so agreeing costs them little.

Setting changes the moves, not just the tone. A pushback that happens privately in a small meeting is a different problem from the same pushback happening publicly, in an all-hands, in front of the exec's own reports and peers. In public, add one more move: correct the record without undermining the executive's credibility in front of the room. That usually means agreeing publicly to follow up with the specifics rather than contradicting them point by point in front of others, then having the detailed evidence conversation offline. Winning the technical point in public while making the executive look uninformed in front of their own team is a worse outcome than losing the point that day.

When it's not disagreement, it's an in-the-moment directive. Sometimes the executive isn't just skeptical, they're asking for an immediate change you believe is unsupported. The move here is to script the pushback so it protects the relationship while still registering the concern: something like "I want to make sure we don't regret this. Can I take ten minutes with you right after this to pressure-test it before we commit?" This buys the review you need without refusing the executive in the room, and it signals that the concern is about the decision, not about resisting them.

Worked example

Situation: a recommendation to move a workload to a new vendor gets pushed back on live in a small planning meeting: "this feels like vendor marketing, I'm not convinced."

Opening: "I hear you, vendor marketing can definitely overpromise, that's a fair thing to be skeptical of. Can I ask specifically what feels like hype, the performance claims, the security posture, or the cost savings? That tells me exactly where to focus."

Evidence: once the concern narrows to performance claims specifically, the response stays tight: independent benchmark results against the current baseline, the relevant compliance attestations already on file, and two reference customers in a similar industry who can be contacted directly.

Reaching agreement: "Rather than deciding on the vendor's word or mine, I'd propose a six-week pilot on a non-production workload with four explicit pass criteria: latency, integration effort, operational fit, and cost at scale. If it misses any of them, we stop and reassess. Does that address the concern, and are you comfortable greenlighting a bounded pilot?"

The public variant of the same scenario: the same pushback happens in an all-hands instead. The opening and evidence stay nearly identical, but the close changes: "That's worth getting right, let me pull the benchmark data and the reference contacts together and walk you through it right after this," rather than debating the specifics live in front of the room. The detailed evidence conversation and the pilot proposal then happen in the follow-up, not in public.

Trade-offs & pitfalls

• Escalating the argument in the moment (more data, louder) rarely works on a skeptical senior audience; it reads as not having heard the objection.
• In public settings, correcting the record too bluntly can win the specific point and cost the relationship; the better move is usually to take the detailed disagreement offline while still registering, briefly and respectfully, that the record needs a follow-up.
• Conceding immediately to an unsupported in-the-moment directive avoids conflict but can commit the team to a bad call; the scripted "let's pressure-test it first" move protects both the relationship and the decision.
• Not every pushback deserves the full three-step treatment. If the executive is right, the senior move is to say so plainly and move on, not to manufacture a pilot to save face.

Direct answer

A strong answer shows you built a case, not just found a number. You named the default decision that was about to happen without evidence, matched the weight of evidence to how reversible the decision was and how much time you had, triangulated quantitative and qualitative signal so the "what" and the "why" both showed up, and packaged the result as a decision artifact the stakeholder could act on, not a data dump they had to interpret themselves.

Structured elaboration

Anatomy of an evidence-based case:

1. Name the default. Say plainly what decision is about to happen and why (usually intuition, urgency, or one compelling anecdote), so the room can see the gap you're filling.
2. Match evidence weight to reversibility and time. An irreversible, expensive decision earns more rigor; a near-term deadline earns the fastest credible signal, not the most rigorous one.
3. Triangulate. Quantitative data shows what is happening; qualitative signal (interviews, quotes, support tickets) shows why. Either alone invites the obvious rebuttal ("that's just anecdotes" or "the numbers don't say why").
4. Package for the audience. A one-page decision memo or a single slide often does more persuasive work than another week of analysis.

Worked calculation: honest uncertainty. Say a pilot of 200 users produced 30 conversions ($\hat p = 0.15$). Reporting the point estimate alone overstates confidence; a senior candidate reports a confidence interval instead, a range you can say you are 95% sure the true value falls in, rather than presenting one number as if it were exact. The 1.96 is the cutoff that corresponds to 95% confidence under a normal approximation (the assumption that many possible outcomes cluster into the familiar bell-curve shape, where about 95% of that curve falls within 1.96 standard errors of the estimate), and the term under the square root is the standard error, a measure of how much this estimate would move around if the pilot were rerun on a fresh sample:

$$\hat p = \frac{30}{200} = 0.15$$ $$CI_{95\%} = \hat p \pm 1.96\sqrt{\frac{\hat p(1-\hat p)}{n}} = 0.15 \pm 1.96\sqrt{\frac{0.15 \times 0.85}{200}} \approx 0.15 \pm 0.05 = [0.10,\ 0.20]$$

Saying "10% to 20%, most likely around 15%" instead of a bare "15%" is what separates a credible business case from a fabricated-precision one, and it pre-empts the "is this even real" objection a numerate stakeholder will raise.

Same move, different packaging. This competency shows up in many shapes across roles, and the table below is a reference, not a checklist to work through row by row: skim it once for the pattern, then treat the worked example further down as the one version you actually need to know cold. The underlying move (evidence proportional to stakes, triangulated, packaged to persuade) stays the same in every row:

Worked example

Situation. At a mid-size B2B platform team, leadership was two weeks from locking next quarter's roadmap around a reporting-and-analytics overhaul, driven by one executive's belief that power users needed deeper reports to upgrade. Meanwhile, early trial cancellations were climbing and nobody had looked at why.

Stakes. Committing a full quarter of engineering capacity to the wrong bet, while trial users kept leaving faster than new demand could replace them, would have made growth slower, not faster, than the reporting bet was even meant to fix.

The influence moves.

• Named the default out loud, as a factual gap rather than an accusation: the roadmap was currently being decided on one executive's hypothesis with no supporting signal.
• Matched evidence to the window: with only ten days before the roadmap locked, pulled existing product-analytics event data (already collected, no new instrumentation needed) and ran a short opt-in exit survey to the last 60 days of canceled trials.
• Triangulated: the event data showed where in onboarding users dropped off; the survey free-text explained why. Of 40 respondents, 27 cited setup and configuration confusion as their reason for leaving ($27 \div 40 = 0.675$, about 68%), not a missing feature.
• Packaged it as a one-page decision brief: one paragraph stating the ask ("delay the reporting overhaul one quarter, fix onboarding setup friction instead") plus a short evidence appendix (the funnel chart and three verbatim quotes), not a slide-by-slide walkthrough.
• Sized the ask to the evidence: proposed a two-week spike to fix the worst setup step and re-measure, rather than asking for a permanent reroute of the whole quarter on ten days of analysis.

Resolution. Leadership approved the two-week spike before the roadmap locked. The evidence was credible enough that the original executive co-sponsored the change instead of contesting it.

What a senior candidate does differently. A mid-level candidate stops once the numbers "prove" the point. A senior candidate also stages the ask so it's proportionate to how much evidence they actually had, and brings the original stakeholder along as a co-sponsor rather than a defeated opponent, which is what protects the relationship for the next disagreement.

Trade-offs and pitfalls

• Rigor vs. speed. Over-investing in statistical proof for a reversible, low-stakes call wastes the one resource (time and goodwill) that a genuinely irreversible call actually needs.
• Data dump vs. artifact. A wall of dashboards is not persuasive on its own; the packaging (one slide, a two-part memo) often does more work than an extra week of analysis.
• Causal overclaim. Claiming a change "caused" a metric improvement without ruling out confounders (seasonality, concurrent launches) is the fastest way to lose credibility with a numerate stakeholder. Name the confidence and the caveats instead of hiding them.
• Thin-signal cases. Treat a severe but thin (n<10) signal as grounds for a bounded, reversible action (a pilot, a spike), not a full commitment. Conflating "worth investigating now" with "proven" is a common junior mistake.

I would first separate disagreement on the outcome from disagreement on the method. Then I would bring the executives into a short decision session with a one-page brief: the business goal, the options, the trade-offs, and the decision needed. I would make decision rights explicit using RACI, which means Responsible, Accountable, Consulted, and Informed. That way, everyone knows who recommends, who decides, and who simply needs to stay informed.

For example, if one sponsor wants speed, another wants cost savings, and a third wants risk reduction, I would ask which metric is the tie-breaker if they conflict. I would propose a shared scorecard with 2 or 3 measures, such as revenue impact, operational risk, and delivery date, then ask the accountable executive to make the final call in writing.

While the debate is happening, I would keep teams executing on work that is not dependent on the unresolved choice, pause only the parts that could be wasted, and communicate a clear interim plan. The goal is to prevent thrash, protect momentum, and get everyone back to one set of success criteria.

For example, on a customer-onboarding automation initiative, three executives disagreed about halfway through: the VP of Engineering wanted to prioritize system reliability given a recent outage, the VP of Finance wanted to prioritize cost savings from reduced manual onboarding labor, and the VP of Risk wanted to prioritize compliance controls given a pending audit. In the decision session, the RACI mapping made the VP of Product the accountable decision-maker, with all three VPs as consulted. The proposed scorecard used three metrics: onboarding error rate (tied to reliability), manual labor hours saved per month (tied to cost), and number of unresolved audit findings (tied to risk). The accountable VP decided that the audit-findings metric was the tie-breaker for this quarter, since the audit deadline was fixed and immovable, while the reliability and cost metrics would be weighted equally starting the following quarter. While that decision was being finalized in writing, the teams kept building the shared onboarding data pipeline, which every option needed regardless of the outcome, and paused only the specific reporting dashboard whose design depended on which metric ultimately won.