> This page is for version v8.3.0 (default). > For other versions, use one of these documentation indexes: > - v8.3.0 (default): https://docs.mindreasoner.com/v-8-3-0/llms.txt > For clean Markdown of any page, append .md to the page URL. > For a complete documentation index, see https://docs.mindreasoner.com/llms.txt. > For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.mindreasoner.com/_mcp/server. # Retain Your Best People ![Mind Reasoner](/_fern-files/_img/466e07efd0202b28f29ec8dda3be88918c85104c2652efceb8ff717127f861ca.webp) > **Stop Reacting to Resignations** > > **The shift:** Create employee minds. Know who's at risk before they start looking. Have more effective performance conversations. Navigate organizational changes smoothly. > > **Result:** Retain top talent and strengthen team engagement proactively. --- ## What You Can Predict #### Flight Risk **Know before they resign:** * Who's considering leaving * Unvoiced concerns and frustrations * What would make them stay * What would trigger them to leave Act before they start job searching. #### Performance Conversations **Deliver feedback effectively:** * How they'll receive difficult feedback * Which framing will work best * What concerns they'll raise * How to maintain trust during tough talks Navigate sensitive conversations with confidence. #### Career Development **Support growth proactively:** * Career aspirations and goals * Skills they want to develop * What motivates them * Growth opportunities they'd value Retain high performers through development. #### Team Changes **Navigate org changes smoothly:** * How team will react to restructuring * Individual concerns about changes * Resistance points to address * What communication approach works Implement changes without losing people. --- ## How to Predict #### 1. Create Employee Mind Upload past interactions with the employee: ```bash > "Create a mind for Marcus Johnson, Senior Engineer, using /Documents/employee-interactions/marcus-johnson-1on1s.vtt" ``` **Training:** 5-15 minutes #### 2. Ask Any Question **Assess flight risk:** ```bash > "How satisfied are you in your current role? Are you considering looking for other opportunities?" ``` **Test feedback approach:** ```bash > "I need to give you feedback about missing deadlines. How will you respond if I frame it this way: [approach]?" ``` **Predict reaction to change:** ```bash > "We're reorganizing the team structure. How will you feel about this change? What concerns will you have?" ``` #### 3. Act Proactively Get predictions. Address concerns before they escalate. **You'll know:** * How to retain your best people * How to deliver feedback effectively * How to navigate changes successfully --- ## Real Examples #### Predict Flight Risk ### Before 1:1 Meeting **You ask employee mind:** ```bash > "How satisfied are you in your current role? Are you considering looking elsewhere?" ``` **Employee mind reveals:** ``` SATISFACTION LEVEL: LOW (high flight risk) Hidden concerns I have (that I haven't voiced to you): 1. Career Stagnation What's happening: Same role for 3 years, no promotion path Why I haven't said anything: Don't want to seem pushy Impact: Feeling undervalued and stuck Risk level: HIGH - actively updating LinkedIn 2. Work-Life Balance Erosion What's happening: Expected to work late frequently Why I haven't said anything: Team is understaffed Impact: Burnout building, family time suffering Risk level: HIGH - recruiters reaching out 3. Lack of Recognition What's happening: Led 2 major projects, minimal acknowledgment Why I haven't said anything: Should be obvious to leadership Impact: Feel invisible and unappreciated Risk level: MEDIUM - motivation declining What would make me leave: - Another company offers senior title - Recruiter presents better work-life balance - One more project without recognition What would make me stay: - Clear promotion timeline discussion - Acknowledgment of contributions - Commitment to work-life boundaries - Genuine investment in my growth ``` ### In Actual 1:1 **What happens:** * You: "I wanted to talk about your career path. You've been here 3 years - let's discuss promotion timeline." * Employee: "Actually, I've been hoping we'd discuss this..." *\[opens up about concerns]* * You: *\[addresses career path, acknowledges contributions, sets boundaries]* * Employee: *\[feels valued, stays on team]* **Result:** Retained top performer by addressing concerns before they accepted another offer. #### Navigate Performance Conversations ### Before Difficult Feedback Conversation **You ask employee mind:** ```bash > "I need to give you feedback about consistently missing sprint deadlines. If I say: 'Your missed deadlines are impacting the team and we need to see improvement,' how will you respond?" ``` **Employee mind predicts:** ``` My likely response: DEFENSIVE (conversation will go poorly) Why this approach won't work: - "Impacting the team" feels like blame/shame - "We need to see improvement" sounds like threat - Doesn't acknowledge context I'm dealing with - I'll shut down and relationship will be damaged What I'm actually dealing with (that you don't know): - Overwhelmed with unclear requirements - Context-switching between 4 projects - Working evenings to catch up - Feel like I'm drowning but too proud to say it If you use this framing: - I'll get defensive - Won't share what I'm struggling with - Will start looking for new job - Trust will be damaged ``` ### Test Better Approach **You ask:** ```bash > "What if I approach it differently: 'I've noticed you've been missing deadlines lately, which isn't like you. What's going on? How can I help?' How would you respond to that?" ``` **Employee mind confirms:** ``` BETTER. This approach will work. Why: - Acknowledges this is unusual for me - Shows concern, not blame - Opens space for me to share context - Positions you as ally, not critic What I'll say: "Honestly, I've been overwhelmed. The requirements keep changing and I'm spread across too many projects. I've been working nights but can't keep up. I need help prioritizing." With this approach: - I'll be honest about struggles - We can solve the real problem - Trust strengthens - Performance actually improves ``` ### In Actual Conversation **What happens:** * You: "I've noticed you've been missing deadlines, which isn't like you. What's going on?" * Employee: *\[opens up about being overwhelmed, exactly as predicted]* * You: *\[helps prioritize, reduces project load, clarifies requirements]* * Employee: *\[performance improves, trust strengthened]* **Result:** Effective feedback conversation that improved performance and strengthened relationship. #### Predict Team Reactions ### Before Announcing Restructure **You ask employee mind:** ```bash > "We're reorganizing the team. You'll be moving from Engineering Team A to the new Platform Team under a different manager. How will you feel about this? What concerns will you have?" ``` **Employee mind predicts:** ``` REACTION: VERY NEGATIVE (potential resignation trigger) Why this is risky for me: 1. Manager Relationship Issue: I have strong relationship with current manager Concern: New manager unknown - will they support me? Risk: Loss of trusted advocate 2. Career Impact Issue: Was tracking toward promotion on current team Concern: Starting over on new team = promotion delayed Risk: Feel like career setback 3. Work I Care About Issue: Leading initiative on Team A that I'm passionate about Concern: Will I have to hand it off? Risk: Loss of ownership and impact 4. Team Dynamics Issue: Strong relationships with Team A colleagues Concern: Starting over building trust Risk: Feel isolated in new environment If announced without addressing these concerns: - Will feel like my input doesn't matter - Will interpret as demotion or lack of confidence - High likelihood I'll start job searching - May resign within 30 days ``` ### Refine Communication Approach **You ask:** ```bash > "What if I present it this way: One-on-one conversation before announcement. Explain the platform team is strategic priority, you're being chosen for your expertise. Discuss promotion timeline won't be affected. Ask about the project you're leading and find way to keep you involved. Would this help?" ``` **Employee mind confirms:** ``` MUCH BETTER. This approach will work. Why: - One-on-one shows respect for my input - "Chosen for expertise" reframes as opportunity, not move - Promotion timeline commitment addresses career concern - Keeping project involvement preserves my ownership - I feel valued, not shuffled My likely response: "I appreciate you thinking of me for the platform team. Can we talk about the promotion timeline and how I can stay involved in the current project? If we can work those out, I'm open to this move." With this approach: - Won't trigger resignation - Can discuss concerns openly - Transition happens smoothly - Actually get excited about opportunity ``` ### In Actual Conversation **What happens:** * You: *\[has one-on-one, frames as opportunity, addresses concerns proactively]* * Employee: *\[responds positively, as predicted, raises concerns]* * You: *\[works through concerns together]* * Employee: *\[accepts move, stays engaged]* **Result:** Successfully navigated org change without losing valued employee. --- ## Common Scenarios #### Retention Risk Assessment **Predict:** * Current satisfaction and engagement level * Unvoiced frustrations building up * What would trigger them to start looking * What would make them stay long-term **Assess quarterly** for high performers and key team members. **Outcome:** Retain top talent by addressing concerns proactively #### Performance Improvement Plans **Predict:** * How they'll receive performance feedback * What framing will be most effective * Underlying issues affecting performance * Which support would help them improve **Test feedback approaches** before difficult conversations. **Outcome:** More effective performance conversations that maintain trust #### Promotion Discussions **Predict:** * Their expectations for promotion timing * How they'll respond to "not yet" * What development areas they're aware of * What timeline would retain them **Navigate promotion conversations** transparently and effectively. **Outcome:** Manage expectations while maintaining motivation and retention #### Organizational Changes **Predict:** * Individual reactions to team restructuring * Concerns about new roles or managers * Career impact worries * Which employees are at highest flight risk **Test change communication** before announcing. **Outcome:** Smooth organizational transitions without losing key people --- ## Quick Start #### 1. Create Employee Minds For high performers and at-risk team members, upload: * 1:1 meeting transcripts * Performance review discussions * Email exchanges * Team meeting interactions **Training:** 5-15 minutes per employee #### 2. Assess Regularly Quarterly or when concerns arise, ask employee minds: * How satisfied are you in your role? * What concerns do you have? * Are you considering other opportunities? Identify flight risk early. #### 3. Test Before Difficult Conversations Before performance feedback or major announcements: * How will they respond to this feedback? * Which approach will be most effective? * What concerns should I address? **Result:** More effective conversations that strengthen (not damage) trust --- ## Implementation #### MCP (No Code) **Use Mind Reasoner through Claude Code** No coding. Just natural conversation in Claude. **You:** ```bash > Create an employee mind for Sarah Chen, Product Manager, using /Documents/employee-1on1s/sarah-chen-2024.vtt ``` **Mind Reasoner:** ``` ✓ Training employee mind... (~10 min) ``` **You:** ```bash > How satisfied is Sarah in her current role? Is she considering looking for opportunities elsewhere? ``` **Mind Reasoner:** ``` Based on Sarah's communication patterns: SATISFACTION LEVEL: MEDIUM (watch closely) Current state: - Enjoys the work and team - Frustrated with lack of decision-making authority - Feeling micromanaged on recent projects - Seeing peers get promoted while she waits Flight risk assessment: MODERATE - Not actively looking yet - But open to recruiter conversations - One more frustration could trigger search - Will start looking if promotion discussion pushed to next year What would keep her engaged: - More project ownership and autonomy - Clear promotion timeline discussion - Acknowledgment of her contributions - Involvement in strategic decisions Unvoiced concerns: - Feels like her growth has plateaued - Worried she's being passed over - Questions if she has path to advancement here - Hasn't said anything because doesn't want to seem impatient Recommendation: - Have career development conversation this month - Give her ownership of upcoming strategic project - Acknowledge specific contributions - Outline clear promotion criteria and timeline ``` **You:** ```bash > I want to give Sarah ownership of the new product strategy project. If I approach her this way: [your approach], how will she respond? ``` **Mind Reasoner:** ``` POSITIVE. This will significantly improve retention. Her likely response: "I really appreciate the opportunity. This is exactly the kind of strategic work I've been hoping to do. Can we also discuss the promotion timeline?" Why this works: - Shows trust in her capabilities - Addresses autonomy concern - Demonstrates investment in her growth - Creates momentum for promotion discussion Impact on retention: - Flight risk drops from MODERATE to LOW - Engagement increases - Will turn down recruiter calls - Buys you 6-12 months to execute on promotion ``` [MCP Tools Reference →](/mcp-tools) #### Direct API **Build employee engagement prediction into your HR workflow** ```javascript const API_BASE = 'https://app.mindreasoner.com/api/public/v1'; // Create employee mind and train // (See API Quick Start for full workflow) // Assess flight risk const flightRisk = await fetch(`${API_BASE}/simulate`, { method: 'POST', headers: { 'Authorization': `Bearer ${API_KEY}`, 'Content-Type': 'application/json' }, body: JSON.stringify({ mindId: employeeMindId, scenario: { message: "How satisfied are you in your current role? Are you considering other opportunities?" } }) }).then(r => r.json()); console.log('Flight risk assessment:', flightRisk.message); // Test feedback approach const feedbackTest = await fetch(`${API_BASE}/simulate`, { method: 'POST', headers: { 'Authorization': `Bearer ${API_KEY}`, 'Content-Type': 'application/json' }, body: JSON.stringify({ mindId: employeeMindId, scenario: { message: "If I give you this feedback: [approach], how will you respond?" } }) }).then(r => r.json()); console.log('Feedback approach test:', feedbackTest.message); ``` [API Documentation →](/api-quick-start) --- ## Next Steps #### [Predict Candidates](/workflow-hr-predict-candidates) Predict candidate fit and interview responses #### [MCP Quick Start](/mcp-quickstart) Set up in 5 minutes #### [API Quick Start](/api-quick-start) Build into your HRIS > **Info** > > Questions? Email [support@mindreasoner.com](mailto:support@mindreasoner.com)