Influence and Persuasion Questions

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.

I would move quickly because a one-week blockage is usually a clarity problem, not a technology problem.

First, I would bring both teams together and restate the facts: what is blocked, what the milestone depends on, and what happens if nothing changes. Then I would ask each team to explain its assumption about ownership. Often the disagreement is about boundaries, not willingness.

Next, I would decide the immediate owner based on capability and dependency, not pride. If needed, I would split the work into a temporary owner for this milestone and a permanent owner for later. For example, one team might own the interface definition while the other implements the code.

If they still cannot agree, I would escalate with options, not complaints: who can do it fastest, who has the right context, and what the risk is for each choice. That keeps the relationship intact because the discussion stays focused on delivery.

After the milestone, I would document the ownership rule so the same dispute does not happen again. The goal is to unblock the work, make the decision fair, and avoid turning a coordination issue into a personal conflict.

For example, on a project one week from a data-pipeline migration milestone, the platform team and the analytics team each believed the other owned writing the schema-validation logic that would catch bad records before they reached the new pipeline. The platform team's assumption was that analytics, as the consumer of the data, should define what counted as valid. The analytics team's assumption was that platform, as the pipeline owner, should implement any validation logic that ran inside the pipeline. Bringing both teams together surfaced that this was exactly a boundary problem: nobody disagreed on doing the work, they disagreed on who was supposed to start it. The immediate decision, made on capability and dependency rather than either team's preference, was that analytics would own defining the validation rules, the business logic of what counts as a bad record, since only they had that context, while platform would own implementing those rules inside the pipeline code, since only they had write access to it and the deployment pipeline. That split unblocked both teams within a day, and the milestone shipped on schedule with the validation logic live. Afterward, the rule, rule-definition belongs to the data consumer, rule-implementation belongs to the pipeline owner, was documented so the next migration didn't reopen the same argument.

Direct answer

Influencing without authority means moving a decision using credibility, evidence, and reciprocity instead of a title. It's the same underlying competency whether the question calls it "influence" or "persuasion": build credibility before you need it, lead with the other person's problem, bring evidence or a low-cost prototype instead of an opinion, and find an ally rather than going in alone.

Structured elaboration

Core tactics:

1. Build credibility before you need it. A track record of reliable delivery makes the ask land differently than the same ask from a stranger.
2. Lead with their problem, not yours. Frame the ask around what the other person is trying to accomplish.
3. Bring evidence or a prototype, not an opinion. A small, low-cost demonstration beats an argument every time.
4. Trade, don't demand. Small, genuine reciprocity works better than a favor you feel owed.
5. Find one ally before the room. A two-person ask lands differently than a solo one.

Where this shows up. The same competency gets asked about in several shapes:

Worked example

Situation. On a platform team, a senior engineer with no authority over product prioritization noticed a shared upload flow causing repeated failures in a "quick-share" feature product wanted to ship as-is to hit a deadline.

Stakes. Shipping as-is risked a visible failure at launch, but the prioritization decision belonged to product, not engineering.

The influence moves.

• Led with credibility already in the bank: a track record of shipping reliable pieces of the same service, so the ask wasn't coming from a stranger.
• Brought evidence, not opinion: existing logs showing the retry-failure rate on the current flow.
• Built a small, low-cost prototype of just the two risky steps instead of asking for a full rewrite.
• Found an ally: a designer who had already flagged the same UX friction independently, turning a solo request into a two-person, cross-functional ask.
• Framed the pitch around product's incentive (a clean launch) rather than engineering's preference for correctness.

Resolution. Product accepted a scoped fix instead of the full reuse plan, without needing an executive to force the decision.

What a senior candidate does differently. Names the specific tactic used (evidence, prototype, ally, incentive-framing) rather than saying "I just talked to them and they agreed," and can say what they'd have done if it hadn't worked, since escalation is a last resort, not a first move.

Trade-offs and pitfalls

• Persistence is not influence. Repeating your opinion louder doesn't count.
• One tactic alone is weaker than combining them. A common weak answer only ever mentions "I built a good relationship" with nothing concrete behind it.
• Escalating too early burns the informal-influence capital that made the peer relationship work in the first place.

Direct answer

Persuading someone senior to fund or change something means leading with the decision you want, naming the cost of the status quo explicitly, pre-empting the single most likely objection before it's raised, and sizing the ask (a phased or capped version) so agreeing feels lower-risk than it would if you asked for everything up front.

Structured elaboration

Anatomy of an executive ask:

1. Lead with the decision, not the narrative. State the ask early; don't make the sponsor wait for the punchline.
2. Name the cost of inaction explicitly, not just the benefit of acting.
3. Pre-empt the most likely objection (revenue impact, cost, risk) before someone else raises it in the room.
4. Size the ask to reduce perceived risk: a phased rollout, a pilot, or a capped budget is an easier yes than the full commitment.
5. Know your sponsor and your skeptic beforehand, and align the skeptic privately when possible.

Same competency, different scale. This shows up from small asks to board-level ones:

Worked example

Situation. At a mid-size company, an engineering manager proposed a platform consolidation project in a leadership review. A senior VP publicly dismissed it in the room as "solving a problem nobody has," undermining the pitch in front of the same audience needed for approval.

Stakes. Losing credibility with that VP risked not just this proposal but every future ask; meanwhile the underlying problem (duplicated infrastructure, rising support cost) was real and getting worse.

The influence moves.

• Didn't re-litigate in the room; took the public pushback as a signal to gather sharper evidence, not an invitation to argue live.
• Went back to the VP one-on-one, not to reopen the room's discussion but to ask directly what would change their mind, and learned the real objection was a past project's failed ROI, not this one's merits.
• Rebuilt the case to address that exact objection: capped the initial ask to a bounded pilot instead of the full six-month rewrite, with a defined stop-loss checkpoint.
• Brought the VP back in as a named reviewer of the revised plan, rather than resurfacing it as a surprise.

Resolution. The VP co-sponsored the revised, phased version at the next review. The earlier public criticism ended up making the final plan tighter and more credible, not dead.

What a senior candidate does differently. Doesn't treat public pushback as the end of the story or take it personally; treats it as the clearest possible signal of the real objection and goes to address it directly with the person who raised it, rather than only preparing a better slide for the same room.

Trade-offs and pitfalls

• Sequencing matters. Leading with the ask before the sponsor is aligned invites exactly this kind of public pushback; senior candidates often pre-wire the most skeptical stakeholder before the room, not after.
• Sizing matters. Asking for the full multi-month or multi-million commitment up front is a harder yes than a capped pilot with a defined checkpoint; the same case is more persuasive staged.
• "Strategic value" still needs a quantified comparison. Even initiatives without near-term revenue need some measured comparison (opportunity cost, cost of inaction), or the ask reads as a hunch.

Building a coalition before a decision point starts before you ever present: identify whose support or veto will actually matter, engage them privately in an order that makes each later yes easier to get, and bring each person something concrete they need rather than a generic ask for support.

Mapping and sequencing

• Map influence and interest. List everyone who could formally veto or bless the proposal, plus anyone with no formal say who still has real influence over those decision-makers.
• Sequence deliberately. Engage the lowest-friction likely allies first, before the proposal is public, so you arrive at the wider decision point with visible support already lined up rather than asking a group to be first movers together.
• Offer something specific per stakeholder, tied to what they're actually measured on: reduced risk to their own metric, a pilot scoped to their team, early visibility into results, or public credit. A generic ask for support is much weaker than something concrete.

Two named shapes of this pattern

Resolving separate vetoes before convening a group. A tech lead wants to relax a security control temporarily to hit a launch date, with a compensating control added afterward, a security versus time-to-market tradeoff. Brought cold to a mixed room, the most risk-averse voice usually wins by default. Instead, the lead meets security first, alone, asking what compensating control would make a temporary exception acceptable, not asking them to simply waive the check. Only once security has a specific answer does the lead bring legal, showing the agreed compensating control and asking what documentation legal needs to be comfortable with the interim exposure window. Product only joins once security and legal's actual sign-off is already attached, so the wider room is there to confirm, not to negotiate the tradeoff from scratch.

Multiple buy-in strategies aimed at different needs. For a cross-functional analytics initiative that hasn't launched yet, product and marketing may need to be brought along with three genuinely different offers: a scoped pilot for the team most worried about disruption, early access to the resulting data for the team that wants visibility, and public co-ownership credit for whichever team's cooperation is hardest to secure. Using the same single pitch on both functions usually undersells what each one actually needs to say yes.

Scaling it into standing influence

• From one-off coalition to a repeatable habit. Winning support once, on one proposal, with one team, is different from scaling personal influence beyond your immediate team into middle management across the organization. That scaling requires codifying the tactic into something repeatable (pilot, then data, then public credit) rather than reinventing the ask each time, and building relationships with peer leads before you actually need something from them.
• Trusted contributor to go-to partner. The credibility this builds over time moves through a specific progression: from being a trusted contributor, someone whose individual work is reliable, to being a go-to partner, someone stakeholders proactively loop in before a decision is even finalized, because your input has consistently made past decisions better. Track this by whether you're being consulted earlier in the process over time, not just by whether individual asks succeed.
• Owning the plan without owning the decision. When you don't own the decision outright, such as cross-functional analytics choices that belong to other teams, a personal influence plan means investing in relationships and data credibility with the actual owners on an ongoing cadence, not waiting until you need a specific yes.

Worked example

A tech lead wants to ship an integration faster by relaxing a specific security control temporarily, with a compensating control added within a defined follow-up window, instead of the default full security review blocking the launch date, a security versus time-to-market compromise. Approached cold, in a mixed room, security could veto outright, legal could block over compliance exposure, and product needs the date to hold for a partner commitment.

The lead meets security separately first: "what compensating control would make a temporary exception acceptable to you?" Security proposes a monitoring and alerting control plus a hard remediation date. The lead brings that specific agreement to legal next, asking what documentation legal needs to be comfortable with the interim exposure window; legal signs off given a written record and the fixed remediation date. Only then does the lead convene product, security, and legal together, now presenting a plan that already carries security and legal's specific sign-off, so product's core need (the date holds) is satisfied without the lead having to relitigate the tradeoff with all three functions at once.

The wider meeting is short, because every veto-holder's actual concern was resolved one-on-one beforehand, tailored to that function's own criteria, not a single generic pitch delivered to all three simultaneously.

What a senior person does differently here: never brings unresolved cross-functional tension into a group room, resolves each function's specific veto criteria privately in an order that makes later conversations easier, and only convenes the group to confirm what's already agreed.

Trade-offs and pitfalls

• Sequencing takes real calendar time. Under a hard deadline, skipping the one-on-one alignment to save time usually costs more time recovering from a group veto than the sequencing would have taken.
• What you offer each stakeholder has to be genuinely deliverable; an empty promise to secure a yes burns exactly the go-to-partner reputation the moment it isn't honored.
• Scaling this into a repeatable, org-wide habit without a track record of delivered promises just looks like politicking. The trusted-contributor credibility has to come first, before the scaled version works.