Convincing a Non-Technical Stakeholder of a Constraint

Tell me about a time you had to convince a non-technical stakeholder — a PM, business head, or founder — to accept a technical limitation that affected the feature they wanted or the timeline they had committed to. Expect to cover what the stakeholder wanted and why, the constraint and its root cause, how you explained it (analogy, data, a prototype), the compromise or alternative you proposed, and how it ended.

What's evaluated

• Ability to translate a technical constraint into business language the stakeholder actually cares about
• Stakeholder empathy — whether you dug for the underlying need rather than rejecting the request exactly as stated
• Whether you offered a viable alternative or simply said "no"
• The outcome for the product, and whether the working relationship survived it
• Evidence you used something concrete (data, a prototype, a cost estimate) to make the constraint legible, rather than relying on authority