Influence and Persuasion Questions

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.

I would diagnose this in four layers: alignment, execution, incentives, and measurement.

First, alignment. I would check whether everyone still agrees on the problem statement and the target outcome. If different leaders define success differently, teams can stay busy without moving the business.

Second, execution. I would review what actually shipped, what was adopted, and where the process slowed down. Busy meetings and shipped deliverables do not prove value if the critical users never changed behavior.

Third, incentives. I would ask whether teams are rewarded for the new outcome or for protecting their own function. If a team is measured on local throughput, it may resist work that helps the overall initiative.

Fourth, measurement. I would compare leading indicators and lagging indicators. For example, if a support automation project shipped six features but ticket volume did not drop, I would look at adoption, usage, and customer behavior before calling it a success.

I would bring leadership a simple readout: what was intended, what changed, where the bottleneck is, and what evidence supports that conclusion. That gives leaders a choice between fixing alignment, adjusting incentives, or changing the plan.

For example, on a two-quarter initiative to reduce customer support ticket volume through a new self-service help center, the four-layer check found: alignment was actually fine, everyone agreed the goal was fewer repeat tickets, not just more help-center pageviews. Execution had shipped six planned articles and a new search widget on time. Incentives were fine too, the support team was measured on ticket deflection and had every reason to want the initiative to work. The real problem was measurement: the team had been reporting help-center pageviews as the success metric, which had gone up 3x, but nobody had checked whether the same customers who viewed an article still opened a ticket afterward. Pulling that number showed 71% of pageviews were followed by a ticket within 24 hours anyway, meaning the articles were being read but weren't actually answering the question. The recommendation to leadership was not to kill the initiative or blame the team, but to replace the pageview metric with a deflection rate (viewed an article and did not open a ticket) and to revise the two articles with the worst deflection rate. Leadership approved continuing the initiative under the corrected metric rather than shutting it down, and deflection rate became the standing measure for the next quarter.

Direct answer

Credibility with people who have no track record with you is earned in the first few interactions, not argued for. The fastest reliable path is to listen before recommending anything, make your reasoning visible rather than just your conclusions, and deliver one small, real result quickly, before you ever ask them to trust a bigger claim.

Structured elaboration

A framework for the first interactions with a new stakeholder or team.

1. Intake before opinion: understand what decisions they're actually trying to make and what's gone wrong for them before, before offering any recommendation.
2. Show your work: when you do produce something, make the validation visible (trace a number back to its source live, walk through how a result was derived) instead of asking them to trust a polished output.
3. Deliver a small, real win fast: a scoped result within the first couple of weeks does more for trust than a comprehensive plan that ships in month two.
4. Telegraph how you handle being wrong: tell them up front how you'll flag it if something in your work turns out to be off. People trust someone who has already shown you a plan for your own mistakes.

The first 30 days. New cross-functional partners are evaluating you the whole time, not just at the big review. Being proactive about the relationship in the first 30 days, rather than waiting for a natural moment, is itself a credibility move. A first 1:1 with a new partner can open with something like: "What decisions are you trying to make in the next month that you don't feel confident about today?" followed by "What's gone wrong before when someone tried to help with this?" Both questions do real work: the first surfaces what would actually count as a win to them, the second surfaces the specific way trust was broken before, so you don't repeat it by accident.

Three behaviors that quietly erode credibility across teams, and the remediation for each:

Credibility repair is a different problem from rapid trust-building, and worth naming separately. Rebuilding credibility across engineering, product, and customers after an architecture decision failed in production is credibility repair, not the repair of a single personal relationship: it spans multiple functions at once, each of which needs something different. Engineering needs an honest technical postmortem without blame-shifting. Product needs clear, early communication about impact and timeline. Customers need a concrete remediation plan and a channel that doesn't go quiet. Treating this as "smoothing over one relationship" misses that trust has to be rebuilt with several audiences in parallel, each judging you by different evidence.

Worked example

Situation: in the first month partnering with a new team (the fraud-risk team, which had just started requesting weekly modeling support from the analytics group for the first time), the working relationship started skeptical, because past deliverables from this kind of collaboration had shipped late and with numbers nobody trusted.

Actions: an early 30-minute intake conversation confirmed exactly which decisions the partner team needed to make (specifically, which transaction-flagging threshold to set for the coming week) and which metrics actually mattered to them (the false-positive rate on flagged transactions, not just the raw flag count), rather than assuming. A one-page plan with milestones and explicit validation steps went out so expectations were unambiguous. A working version, a weekly false-positive-rate dashboard for the fraud-risk team's review queue, shipped inside the first two weeks, and in the walkthrough, a couple of numbers the partner flagged as surprising (the false-positive rate for one transaction category showing 22% instead of the roughly 8% they expected) were traced live, back to the source data, in the room, instead of being defended from memory. The trace showed the 22% figure was correct: a recent change to that category's flagging rule had not been backed out of the historical comparison period, inflating the apparent rate.

Resolution: the partner team began using the dashboard for real weekly threshold decisions within the two-week window. What changed their minds wasn't the polish of the output, it was watching the 22% number get traced back to its source live and seeing that the plan they'd agreed to up front was the plan that got delivered.

Trade-offs & pitfalls

• Rapid trust-building tactics (intake, quick win, visible validation) and credibility-repair tactics (postmortem, cross-function communication, remediation plan) are not interchangeable; using a "quick win" playbook after a public failure reads as minimizing what happened.
• An intake-only approach that never produces anything can itself read as stalling; the first small delivery needs to land within roughly the same window as the intake conversation, not months later.
• Under-promising protects credibility but can look like low ambition if you don't also communicate what you're deliberately holding back on for now.

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.

Direct answer

When a security or ops team resists a proposed architecture change and insists on stricter controls or the status quo, don't argue that they're wrong. Treat their risk concern as a real constraint to engineer around, and negotiate a bounded path (compensating controls, a scoped and timeboxed exception, defined monitoring and rollback) that earns approval without asking them to accept the full, permanent risk up front.

Structured elaboration

Negotiating a bounded exception:

1. Listen and clarify the specific risk. Meet the resistant team and document exactly which control they believe would be violated and what residual risk they'd accept, before proposing anything.
2. Run a focused risk assessment scoped to that specific control, not the whole proposal.
3. Propose compensating controls mapped to that exact risk: segmentation, encryption in transit, least-privilege identities, tuned detection rules, whatever addresses the named concern.
4. Offer a timeboxed, limited-scope pilot: one workload, one region, a defined window, with explicit rollback criteria and no automatic expansion.
5. Define monitoring and a governance path: who reviews it, on what cadence, and what the escalation and sign-off chain looks like.
6. Keep a rollback plan ready, not just a forward plan.

This generalizes past pure technical controls. When the resistance is to a business or pricing model change rather than a security control (for example, a finance team resisting a new contract term), the tactic doesn't change: propose a bounded compromise or a timeboxed pilot with defined success criteria and an exit path, rather than asking for the permanent change up front.

Worked example

Situation. At a B2B platform, the architecture team proposed moving a batch reporting service from a fully isolated on-prem network segment to a shared cloud VPC, to cut latency and cost. The client's security team refused, citing existing segmentation policy.

Stakes. The current setup was measurably slower and more expensive to operate, but security's sign-off was a hard gate, and escalating over their head would have burned the relationship for every future proposal.

The influence moves.

• Met with security leads first to get the specific control at stake; the real blocker turned out to be network segmentation policy, not the data-residency concern initially assumed.
• Ran a focused risk assessment scoped only to that control, not the whole migration.
• Proposed compensating controls mapped to it: a dedicated micro-segment for the new service, mutual TLS to the rest of the VPC, and short-lived service credentials instead of long-lived ones.
• Offered a timeboxed pilot: one non-critical reporting workload, one region, 60 days, with an explicit rollback trigger tied to any anomalous traffic alert.
• Defined the monitoring security would get during the pilot: SIEM-visible logs, a named point of contact, a weekly review, so their sign-off wasn't an act of faith.

Resolution. Security approved the scoped pilot. When it cleared review with no incidents, the exception expanded to additional workloads under the same monitoring terms.

What a senior candidate does differently. Doesn't treat the security team's "no" as an obstacle to route around; treats their specific risk objection as the actual spec to engineer against, and doesn't ask for the full, permanent change until the bounded version has already produced evidence.

Trade-offs and pitfalls

• Compensating controls have real operational cost (more logging, tighter IAM, monitoring overhead). If that cost isn't acknowledged and budgeted, the pilot degrades over time and becomes the next audit finding.
• A scoped exception with no expansion or sunset review quietly becomes a permanent, ungoverned exception, worse than either the original status quo or a properly approved change.
• Escalating past the resistant team can work once, but it costs the relationship. Reserve it for cases where the objection is provably not risk-based (organizational turf, not risk), not as a default first move.