From grimoire
Runs a structured stay interview with a valued direct report — before flight risk shows — surfaced when a manager wants to learn what keeps the person engaged or might drive them to leave.
How this skill is triggered — by the user, by Claude, or both
Slash command
/grimoire:run-stay-interviewThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Conduct a structured, proactive conversation with a valued direct report to learn what keeps them engaged and what might drive them to leave — so you can act on that information before a resignation forces a reactive response.
Conduct a structured, proactive conversation with a valued direct report to learn what keeps them engaged and what might drive them to leave — so you can act on that information before a resignation forces a reactive response.
Adopted by: Kaye & Jordan-Evans's "Love 'Em or Lose 'Em" is the most widely cited employee retention framework, used in training programs at Boeing, the US Army, and hundreds of large corporations; SHRM's 2016 guidance identifies stay interviews as the highest-ROI single retention intervention; Microsoft, LinkedIn, and Deloitte have formalized stay interviews as part of their talent management cadence Impact: Gallup's 2017 "State of the American Workplace" found that 52% of voluntarily exiting employees say their manager or organization could have done something to prevent their departure — and 51% say no one asked them in the 3 months before they quit what would keep them; SHRM research found that replacing an employee costs 50–200% of annual salary; Kaye's research found that stay interview participants who received follow-through on at least one issue showed 40% higher retention at 12 months compared to those who received no follow-through Why best: Exit interviews collect data after the organization has already lost — the employee has resigned, is mentally gone, and has no incentive to be fully candid; performance reviews are evaluative and backward-looking; one-on-ones are operational; stay interviews are the only tool designed specifically to surface what the employee values and what they might need, while there is still time to respond
Sources: Kaye & Jordan-Evans "Love 'Em or Lose 'Em" (Berrett-Koehler, 2014); SHRM "Stay Interviews: A Tool to Prevent Employee Turnover" (shrm.org, 2016); Gallup "State of the American Workplace" (2017)
Stay interviews are not for the whole team simultaneously. Prioritize:
High priority:
Timing:
Do NOT schedule as a response to a perceived flight risk signal that you haven't acknowledged — if the employee suspects you're interviewing them because you think they're about to leave, it changes the dynamic. Frame it as a standard practice applied to everyone.
This is not a performance conversation, a check-in on their projects, or a career development conversation. Name it clearly when scheduling:
"I'd like to schedule a stay interview with you — a conversation
specifically about what keeps you here and what I could do to make
your experience better. It's not about performance, not about your
projects. It's about you. About 30–45 minutes — does [time] work?"
Sending this in advance gives the employee time to reflect rather than reacting in the moment.
These five questions from Kaye & Jordan-Evans cover the full retention landscape:
1. What do you look forward to when you come to work each day? Surfaces what energizes them — their motivators, the work they love, the relationships that matter.
2. What are you learning here, and what do you want to learn? Surfaces whether mastery is being served — whether the role is growing them or stagnating.
3. Why do you stay? The most direct question. Forces articulation of what they value. Often reveals what they've never said aloud.
4. When was the last time you thought about leaving, and what prompted it? Most valuable question. Almost every high performer has considered leaving. This surfaces the real triggers — without requiring the employee to volunteer them unprompted.
5. What can I do, or stop doing, that would make your experience here better? Directly actionable. What they tell you here is your to-do list.
Listen more than you talk. Do not defend or explain. Take notes. If an answer is vague, probe: "Can you say more about that?" or "What would that look like specifically?"
The most common manager mistake: responding to a concern immediately with a reassurance or a counterargument. This closes the conversation and signals that the employee should be less honest.
Instead:
Employee: "I sometimes feel like my work isn't being seen at the leadership level."
Wrong: "Oh, I'm sure [executive] knows who you are."
Right: "Tell me more about what that feels like. What would visibility look like to you?"
Your role in this conversation is to understand, not to fix. You can fix later.
Within one week of the conversation, act on at least one thing the employee told you. This is the single most important step. Stay interviews where nothing changes are worse than no stay interviews — they signal that asking was performative.
Even small actions matter:
Follow up explicitly: "I wanted to let you know I heard what you said about [X]. Here's what I did / am going to do."
After each stay interview, document:
This documentation protects you if they do leave — you can explain the actions you took — and it surfaces patterns across the team if multiple people raise the same issue.
npx claudepluginhub jeffreytse/grimoire --plugin grimoireRuns structured exit interviews that capture retention insights from departing employees. Useful for HR, people analytics, or talent management workflows.
../../../../.claude/skills/leadership/employee-engagement-retention.md
Structure effective one-on-one meetings that build trust, surface concerns, and align on growth and development. Use when preparing regular 1:1s with direct reports or designing 1:1 practices for your team.