Influence and Persuasion Questions

Skills and tactics for persuading and influencing decisions and behaviors when you do not have formal authority, and for scaling influence across teams and organizations. Candidates should demonstrate how to build credibility and trust tailor messages to stakeholder priorities, use data and customer insight to make the business case, tell compelling stories that connect to outcomes, recruit allies and champions, negotiate and compromise, and create operational changes such as standards processes or tooling to lock in gains. Interviewers will probe for examples of influencing technical and non technical stakeholders resolving disagreements building consensus and measuring the impact of influence on adoption quality speed or other business outcomes. For senior levels include examples of cross organizational influence and governance for sustained change.

MediumTechnical

77 practiced

Sales requests a discount for a strategic customer to win a large contract; Product worries the discount creates a market precedent harming long-term pricing. As the PM mediating this conflict, outline a negotiation plan that includes short-term concessions, guardrails to avoid precedent, measurable success criteria, and communication to internal teams.

Sample Answer

Situation: Sales needs a discount to win a large strategic customer; Product is concerned about setting a damaging pricing precedent. As PM I’d mediate with a structured negotiation plan that protects long-term pricing while enabling the win.

1) Objectives (aligned): - Short-term: Secure the deal within target margin floor.- Long-term: Preserve list price integrity and avoid public precedent.

2) Short-term concessions (conditional):- Time-limited, one-off discount tied to contract length, volume milestones, or co-marketing commitments.- Replace % price cut with value-adds: extended onboarding, premium support, implementation credits, or phased pricing ramp.- Use non-standard contract terms (confidentiality, non-disclosure of pricing) and a contract clause denying resale or reference for other customers.

3) Guardrails to avoid precedent:- Require explicit “one-time exception” approval flow (VP Sales + VP Product sign-off).- Limit eligibility window (e.g., 90 days) and enforce confidentiality and non-disclosure.- Record the rationale, decision, and templates in a pricing exception log for audits.- Attach sunset clauses and renewal at standard pricing unless future discounts approved via established process.

4) Measurable success criteria:- Deal closed within X days and within minimum gross margin Y%.- Customer commits to N-month term or $M ARR and agreed milestones.- Onboarding success metrics (time-to-value <= T weeks, adoption > Z% by month 3).- No leakage: zero other customers citing this pricing in next 6 months.

5) Communication to internal teams:- Share executive one-pager summarizing concession, guardrails, approval path, and renewal plan.- Update Sales playbook and pricing exception register; notify Legal, Finance, Customer Success.- Run a 30-minute sync with Sales, Legal, Finance, CS to align responsibilities (confidentiality enforcement, monitoring adoption, renewal cadence).- Post-close, circulate a short report with outcomes and lessons; propose any pricing policy changes if patterns emerge.

Rationale: This balances the revenue opportunity with systemic protection — capture the strategic customer while making the concession non-repeatable, measurable, and auditable.

MediumTechnical

73 practiced

You're running a cross-team design critique where designers disagree on a direction. As the PM facilitator, how do you structure the critique to reach actionable decisions, avoid design by committee, and ensure designers feel ownership of the final direction?

HardTechnical

78 practiced

You suspect a senior stakeholder is influencing prioritization for a pet project that offers limited customer value. How do you surface and address this informal influence without damaging the relationship? Describe the steps, evidence collection, and escalation if required.

Sample Answer

Situation: In my current PM role I noticed a senior stakeholder pushing to prioritize a “pet” feature—bright, visible to execs but delivering little measurable customer value—potentially displacing higher-impact work.

Task: My goal was to surface the informal influence, protect the roadmap’s customer focus, and keep the relationship intact.

Action:- Gather evidence neutrally: I pulled data (user analytics, support tickets, NPS comments), estimated opportunity cost (weeks of dev effort, impact on OKRs), and competitive/contextual research showing limited market demand.- Create a comparison: I built a one-page prioritization brief (problem, user voices, quantitative impact, implementation effort, risks) comparing the pet project against top candidates using a standard framework (RICE/Cost of Delay).- Private conversation first: I met the stakeholder 1:1, framed with curiosity: “Help me understand the user problem you’re solving and the success metrics you care about.” I shared the brief and asked for their constraints and priorities—listening to surface motivations (visibility, personal deadline).- Reframe and collaborate: I proposed alternatives that satisfied their underlying need (e.g., a smaller demoable milestone, analytics dashboard item, or marketing pilot) while preserving high-impact work.- Align stakeholders: I presented the transparent prioritization brief in the roadmap review, invited discussion, and documented the decision and metrics to revisit.

Result: The stakeholder felt heard, we agreed on a lower-effort pilot that delivered visibility, and we kept the roadmap focused on higher-value items. Delivery tracked against agreed metrics; after two quarters the pilot either scaled or was retired based on data.

Escalation (if required):- If influence persisted and threatened OKRs, I would escalate factually to my manager and the PM leadership with the documented brief, clearly showing trade-offs and requested decision (e.g., de-prioritize or approve with explicit funding/timebox).- Maintain professionalism: keep records of conversations, decisions, and agreed metrics; involve HR/ethics only if behavior crossed governance boundaries.

What I learned: Use data and curiosity-first conversations to convert political influence into constructive collaboration; document decisions and alternative compromises to protect product outcomes without burning bridges.

MediumTechnical

57 practiced

Provide a template for a decision record you would use to document cross-functional choices (e.g., architecture, roadmap trade-offs). Include fields such as context, options considered, chosen option, trade-offs, owners, and review cadence. Explain why each field matters for future influence and governance.

Sample Answer

Decision Record Template (for cross‑functional choices)

- Title: Short descriptive name- ID: DR-YYYYMMDD-XX (unique)- Date: Decision date- Authors / Owners: Primary owner (name, role) and supporting stakeholders- Context & Background: Business goals, constraints, metrics, timeline, trigger for decision- Problem Statement: What must be solved, scope, stakeholders affected- Options Considered: 1) Option A — short description; 2) Option B — short description; 3) Option C…- Evaluation Criteria: Success metrics, non‑functional requirements, cost, time to market, risk- Analysis & Pros/Cons: For each option list benefits, risks, estimated effort, dependencies- Chosen Option: Clear description of selected approach and rationale mapping back to criteria- Trade‑offs & Technical Debt: What we accept now, what we defer, likely future costs- Action Plan & Next Steps: Implementation owners, milestones, rollout plan, required approvals- Monitoring & Metrics: KPI(s) to track decision effectiveness and telemetry plan- Review Cadence & Expiry: When to revisit (date or trigger), frequency of reviews, sunset criteria- Communication Log: Who was informed, when, and where the record lives (link)- Related Artefacts: Links to designs, RFCs, tickets, contracts- Sign-offs: Names/roles and timestamps

Why each field matters- Title/ID/Date: Traceability for audits and historical context.- Owners: Accountability — who executes and who to consult.- Context/Problem: Prevents re‑debate by capturing the original constraints and goals.- Options/Evaluation: Demonstrates due diligence and makes trade‑offs explicit for future reviewers.- Chosen Option/Trade‑offs: Records rationale and known compromises so future teams understand technical debt.- Action Plan/Monitoring: Ensures decisions turn into outcomes and allows measurement of success.- Review Cadence/Expiry: Avoids decisions becoming stale; forces re‑assessment as conditions change.- Communication/Related Artefacts/Sign-offs: Governance, discoverability and compliance.

Use a shared, searchable template (Confluence/Notion/Git repo) and link DR IDs into roadmap and sprint artifacts so decisions drive execution and can be audited.

EasyTechnical

58 practiced

List three low-effort, high-impact initiatives you would take in your first 30 days to build credibility with an engineering team that is skeptical of PM priorities. For each, explain why it helps and what metric or signal you'd use to show progress within 30-90 days.

Unlock Full Question Bank

Get access to hundreds of Influence and Persuasion interview questions and detailed answers.

Join thousands of developers preparing for their dream job.