Exit Surveys: What to Ask When Employees or Customers Leave

Employee Exit Surveys: Questions That Get Honest Answers

Exit interview questions often produce diplomatic non-answers ("I found a great opportunity") rather than honest ones ("My manager made my job miserable"). This happens because employees correctly calculate that what they say on the way out can follow them via references and professional networks. Anonymity, separation from the HR interview, and systemic rather than personal framing are the keys to honesty.

• Primary reason for leaving: Offer specific options (compensation, career growth, management, workload, culture, personal reasons) — then invite elaboration
• What would have changed the decision: "Was there anything the company could have done to retain you?" — surfaces preventable factors
• Manager relationship: Rate on a scale, not open text — scaled responses are more honest than verbal ones for sensitive topics
• What you'll miss: Unexpectedly powerful — what they'll miss reveals what you're actually doing well
• eNPS: "Would you recommend this company as a place to work?" — establishes overall sentiment benchmark
• One thing to change: "If you could change one thing about working here, what would it be?" — generates specific, actionable input

Customer Churn Surveys: Catching Customers at Departure

The customer churn survey has a narrow window: the moment of cancellation or non-renewal. A 1-minute survey shown at the cancellation moment — before the account is deactivated — consistently produces your highest-quality churn data.

Using Exit Data to Drive Retention

• If 30%+ of employees leave citing career growth: You have a career development infrastructure problem — not individual manager performance
• If 40%+ of churning customers cite "missing feature": That feature is a retention dependency — it belongs on the product roadmap
• If churning customers cluster in specific segments: That segment may be a poor product-market fit — re-evaluate acquisition targeting
• If a spike in exits correlates with a specific event: A policy change, manager departure, product update — this is recoverable if caught quickly