employee-engagement
$
npx mdskill add mkurman/zorai/employee-engagementDesign surveys and drive culture change with data-backed actions.
- Creates engagement surveys that link questions to specific improvement plans.
- Integrates with performance management and onboarding workflows for context.
- Prioritizes manager-led interventions based on engagement variance research.
- Delivers clear action commitments and progress reports to stakeholders.
SKILL.md
.github/skills/employee-engagementView on GitHub ↗
---
name: employee-engagement
version: 0.1.0
description: >
Use this skill when designing engagement surveys, running pulse checks,
building retention strategies, or improving culture. Triggers on employee
engagement, surveys, pulse checks, retention strategies, culture building,
eNPS, team health, and any task requiring engagement measurement or
improvement programs.
tags: [engagement, surveys, retention, culture, enps, team-health]
category: operations
recommended_skills: [performance-management, onboarding, remote-collaboration, community-management]
platforms:
- claude-code
- gemini-cli
- openai-codex
license: MIT
maintainers:
- github: maddhruv
---
## Key principles
1. **Measure to improve, not to surveil** - Every survey must have a stated action
commitment before it is sent. Employees learn quickly when nothing changes after a
survey; they stop responding honestly. If you are not prepared to act on the data,
do not collect it.
2. **Act on results or stop asking** - The fastest way to destroy survey credibility is
to collect responses and go silent. Publish results within two weeks, share what you
heard, commit to specific actions, and report back on progress. Close the loop every
time.
3. **The manager is the #1 lever** - Research consistently shows that the most
significant driver of engagement variance is the direct manager - more than company
culture, compensation, or benefits. Manager-level action plans matter more than
org-wide initiatives. Coach managers first.
4. **Belonging drives engagement** - Employees who feel they belong - that they are seen,
valued, and included regardless of background - are significantly more engaged.
Inclusion is not a separate workstream; it is a prerequisite for engagement. Segment
results by demographic to surface gaps.
5. **Exit interviews are too late** - By the time an employee hands in notice, the
decision is typically made. Stay interviews - structured conversations with engaged
employees about what keeps them and what risks pushing them out - are a more
effective retention tool. Build them into the regular cadence.
---
## Core concepts
### Engagement drivers
The major evidence-based drivers of engagement, roughly in priority order:
| Driver | Description | Key questions |
|---|---|---|
| Meaningful work | Feeling that work matters and connects to something larger | "Does my work make a difference?" |
| Manager relationship | Trust, support, recognition, and growth from the direct manager | "Does my manager care about me as a person?" |
| Psychological safety | Ability to speak up, take risks, and be authentic without fear of punishment | "Can I raise concerns without retaliation?" |
| Growth & development | Opportunities to learn, advance, and build new skills | "Do I have a clear path to grow here?" |
| Autonomy | Ability to make meaningful decisions about how work gets done | "Do I have the freedom to do my best work?" |
| Recognition | Feeling that contributions are seen and valued | "Does my work get recognized?" |
| Clarity | Understanding of expectations, priorities, and how success is measured | "Do I know what is expected of me?" |
| Connection | Relationships with colleagues and sense of team belonging | "Do I have a best friend at work?" (Gallup Q12) |
### Survey types
| Type | Cadence | Length | Purpose |
|---|---|---|---|
| Annual engagement survey | Yearly | 30-50 questions | Full diagnostic; benchmark over time |
| Pulse survey | Monthly or quarterly | 5-10 questions | Track trends; detect emerging issues early |
| Onboarding survey | 30/60/90 days | 10-15 questions | Catch early disengagement; validate onboarding quality |
| Stay interview | Quarterly (at-risk) / annually (all) | Conversation, 6-8 prompts | Understand retention motivators; surface risk factors |
| Exit survey | At offboarding | 10-20 questions | Capture departure reasons; identify systemic patterns |
| Post-change pulse | After major events (reorg, layoffs, leadership change) | 5-8 questions | Measure sentiment impact; identify where support is needed |
### eNPS (Employee Net Promoter Score)
eNPS measures how likely employees are to recommend the organization as a place to work.
It is the fastest single-question engagement signal.
**Question:** "On a scale of 0-10, how likely are you to recommend [Company] as a place
to work to a friend or colleague?"
**Scoring:**
```
Promoters (9-10): Engaged, enthusiastic advocates
Passives (7-8): Satisfied but not actively promoting; flight risk if competitors recruit
Detractors (0-6): Disengaged or actively unhappy; potential attrition and reputational risk
eNPS = % Promoters - % Detractors
```
**Benchmarks:**
| eNPS range | Interpretation |
|---|---|
| Above +50 | Excellent - top-quartile employer |
| +20 to +50 | Good - above average |
| 0 to +20 | Neutral - room for improvement |
| Below 0 | Concerning - more detractors than promoters |
Always follow the eNPS question with "What is the primary reason for your score?" to
surface qualitative themes.
### Retention risk factors
Employees are most likely to leave when two or more of these signals are present:
- Manager relationship is poor (low manager score on pulse surveys)
- No growth or promotion in 18+ months
- Below-market compensation (self-reported or confirmed by benchmarks)
- Low belonging or psychological safety scores
- Recent major life event (spouse relocation, new child)
- Passed over for a role or project they wanted
- Workload unsustainable for 3+ consecutive months
- Recently returned from parental or medical leave
- Peer attrition - their close colleagues have left
---
## Common tasks
### Design an engagement survey
**Question bank approach:** Select 25-40 questions across drivers. Always include at
least two questions per driver to increase reliability. See
`references/survey-question-bank.md` for the full categorized bank.
**Survey structure template:**
```
1. Overall engagement anchor (1 question)
"I would recommend [Company] as a great place to work." (5-pt agree/disagree)
2. Core driver questions (20-35 questions, 5-pt scale)
Meaningful work: 3-4 questions
Manager: 4-5 questions
Psychological safety: 3-4 questions
Growth: 3-4 questions
Recognition: 3-4 questions
Clarity: 3-4 questions
Connection: 3-4 questions
3. eNPS (1 question + open-text follow-up)
4. Open text (2 questions, optional)
"What is working well?"
"What is one thing that would most improve your experience at [Company]?"
```
**Design rules:**
- 5-point Likert scale ("Strongly Disagree" to "Strongly Agree") for consistency
- No double-barreled questions (e.g., "My manager is supportive and communicates clearly")
- State in the survey intro what will be done with results
- Guarantee anonymity and explain minimum group size for reporting (typically 5)
- Keep under 20 minutes to complete
### Run pulse checks
**Cadence design:**
```
Monthly pulse (recommended for most teams):
- 5 questions: 1 eNPS, 3 rotating driver questions, 1 open text
- Results shared at team meeting within 2 weeks
- Manager sees their team's results; org sees aggregate
Quarterly deep pulse:
- 10 questions: eNPS + 2 questions per top priority driver
- Compared against prior quarter trend
- Leadership reviews by team and segment
Annual full survey:
- Full question bank (30-50 questions)
- External benchmark comparison
- Drives annual engagement strategy
```
**Pulse question rotation:** Avoid asking the same questions every month. Rotate through
driver areas so employees experience variety while maintaining trend data on critical
questions (eNPS should appear every pulse for continuity).
### Analyze survey results
**Segmentation framework:** Never report only aggregate scores. Break down results by:
| Dimension | Why it matters |
|---|---|
| Team / manager | Identifies where action is needed; reveals manager impact |
| Tenure | New hires vs. long-tenured employees often have opposite experiences |
| Level (IC vs. manager vs. director) | Different role stressors; different drivers |
| Department | Engineering vs. Sales vs. Support may have wildly different culture |
| Demographic (if data collected) | Surfaces belonging and inclusion gaps |
**Statistical significance rule:** Do not surface team-level results with fewer than 5
respondents. Report as "insufficient responses to show" to protect anonymity.
**Trend analysis:**
```
Track these four metrics every pulse:
1. Overall favorable score (% agree + strongly agree)
2. eNPS
3. Top 3 scoring questions (what's working)
4. Bottom 3 scoring questions (what needs attention)
Flag when:
- Any driver drops more than 5 points quarter-over-quarter
- eNPS drops below 0
- Manager score falls below 60% favorable
- Psychological safety is in the bottom quartile
```
### Build action plans from results
**The 90-day action plan format:**
```
Survey results briefing: Share results with the team within 2 weeks.
Present top strengths and top areas for improvement.
Acknowledge uncomfortable findings directly.
Team prioritization: Let the team vote on 1-2 areas to focus on.
Avoid the trap of trying to fix everything at once.
Action commitments: For each priority area:
- What we will do (specific, observable action)
- Who owns it
- By when
- How we will know it worked
Progress check-in: 30-day and 60-day check-ins at team meetings.
Close-the-loop update: At 90 days, share what changed and what was learned.
Run a mini pulse on the focus areas.
```
**Manager coaching checklist:**
- Did the manager share results within 14 days? (yes/no)
- Did the manager facilitate a team discussion? (yes/no)
- Did the manager commit to at least one specific action? (yes/no)
- Is the action tracked somewhere visible to the team? (yes/no)
People teams should track these four checkboxes for every manager after every survey.
### Design retention programs
**Segmented by risk factor:**
| Risk factor | Retention intervention |
|---|---|
| No growth in 18+ months | Career path conversation; stretch assignment; lateral move |
| Poor manager relationship | Manager coaching; skip-level meetings; team restructure if severe |
| Compensation gap | Compensation review; equity refresh; off-cycle adjustment |
| Low belonging | ERG connection; mentorship pairing; manager inclusive behaviors coaching |
| Burnout / unsustainable workload | Immediate headcount plan; work redistribution; protected recovery time |
| Peer attrition ("my team is falling apart") | Accelerated backfill; knowledge transfer plan; temporary stabilization bonus |
| High recruiter activity | Stay interview; retention bonus with vesting; role enrichment |
**Stay interview template (6 questions):**
1. What are you most looking forward to at work right now?
2. What keeps you here when you could work somewhere else?
3. When was the last time you thought about leaving - and what prompted it?
4. What would make you think about leaving in the future?
5. Is there anything about your current role, team, or manager that we should change?
6. What does your ideal career path look like over the next 2 years - and are we on track?
Conduct stay interviews with high performers and flight-risk employees quarterly.
Document responses and review with the manager after each session.
### Improve team health
**Retrospective formats by problem type:**
| Team health problem | Retrospective format | Cadence |
|---|---|---|
| Low psychological safety | Anonymous async retro (GitHub/Notion); IC presents themes | Monthly |
| Team not gelling (new or reorganized team) | Team charter session: values, working agreements, communication norms | Once, then review quarterly |
| High conflict or interpersonal tension | Facilitated retro with external HR facilitator; private 1:1s first | As needed |
| Workload imbalance | Capacity mapping exercise; sprint load review | Monthly |
| Unclear priorities causing frustration | OKR alignment session; stakeholder mapping | Quarterly |
| Recognition drought | Kudos round-robin in retro; manager recognition training | Monthly |
**Psychological safety assessment (4 questions):**
1. "I can speak up on this team without fear of negative consequences." (5-pt agree/disagree)
2. "When I make a mistake, I am not held against for it." (5-pt agree/disagree)
3. "It is easy to ask others on this team for help." (5-pt agree/disagree)
4. "Team members value and build on each other's ideas." (5-pt agree/disagree)
Score below 70% favorable on any question indicates a safety issue requiring immediate
attention before broader engagement programs will have meaningful impact.
### Measure culture
**Leading indicators (measure monthly):**
| Indicator | How to measure | Healthy signal |
|---|---|---|
| Internal mobility rate | % open roles filled internally | > 20% |
| Manager approval rating | Pulse survey "My manager helps me do my best work" | > 75% favorable |
| Voluntary attrition rate | Headcount who resigned / avg headcount | < 10% annually |
| 90-day new hire attrition | % who leave within 90 days of start | < 5% |
| Promotion rate | % of ICs promoted per year | 10-15% |
| Recognition frequency | Avg peer recognitions sent per employee per month | > 1 |
| Meeting load | Avg hours per week in meetings for ICs | < 12 hours |
**Lagging indicators (measure quarterly):**
- eNPS trend (are promoters growing?)
- Overall engagement score (favorable %)
- Regrettable attrition (high performers who left voluntarily)
- Exit survey themes (top 3 departure reasons - are they shifting?)
---
## Anti-patterns / common mistakes
| Mistake | Why it is wrong | What to do instead |
|---|---|---|
| Annual survey only | Problems fester for 12 months before surfacing; no chance for early intervention | Add a monthly or quarterly pulse for continuous signal |
| Reporting only company-wide averages | Hides the manager-level variance where action actually lives | Always segment by team, tenure, and level |
| Survey without pre-committed action | Employees recognize "data collection theater"; response rates drop and honesty disappears | Define at least one action you will take before the survey launches |
| Confidentiality theater | Claiming anonymity but reporting team scores of 3 people (easily de-anonymized) | Enforce a minimum group size of 5 for any reported segment |
| Fixing the bottom quintile first | Disproportionate effort on the most disengaged often means the most engaged are neglected and leave | Invest in high performers and promoters - they are the most mobile |
| Over-surveying | Monthly 30-question surveys cause fatigue and declining response rates | Pulse surveys should be 5-10 questions max; reserve long surveys for annual |
---
## Gotchas
1. **Survey results shared without manager-level breakdowns are nearly useless for action** - Org-wide averages hide the teams where engagement is critically low and the managers who are the problem. Sharing only top-line scores protects poor managers while demoralizing the employees under them. Always segment by team, even if it requires a minimum respondent threshold to protect anonymity.
2. **Response rates below 60% make results unrepresentative** - The employees who skip surveys are systematically different from those who complete them - often the most disengaged or the most burned out. A 40% response rate means your "engagement score" reflects the more motivated half of your workforce, not the whole.
3. **Psychological safety scores below 70% favorable invalidate all other engagement data** - If people don't feel safe answering honestly, every other metric is distorted. Low-scoring teams will rate everything higher to avoid identification. Fix psychological safety before running any other diagnostic.
4. **Annual surveys measure the mood of the month the survey was sent, not the year** - Sending the annual survey during a high-energy product launch or immediately after layoffs captures a snapshot, not a trend. Establish a fixed calendar cadence and stick to it, or use rolling pulse data that normalizes seasonal variation.
5. **eNPS without a follow-up open-text question produces unactionable scores** - Knowing that 30% of employees are detractors tells you nothing about why. Always pair the eNPS question with "What is the primary reason for your score?" to get the qualitative themes that drive action planning.
---
## References
For detailed content on specific topics, read the relevant file from `references/`:
- `references/survey-question-bank.md` - Categorized bank of engagement survey questions by driver, with guidance on selection and scale
Only load a references file when the current task requires it.
---
## Companion check
> On first activation of this skill in a conversation: check which companion skills are installed by running `ls ~/.claude/skills/ ~/.agent/skills/ ~/.agents/skills/ .claude/skills/ .agent/skills/ .agents/skills/ 2>/dev/null`. Compare the results against the `recommended_skills` field in this file's frontmatter. For any that are missing, mention them once and offer to install:
> ```
> npx skills add AbsolutelySkilled/AbsolutelySkilled --skill <name>
> ```
> Skip entirely if `recommended_skills` is empty or all companions are already installed.
More from mkurman/zorai
- account-management>
- agile-scrum>
- albumentationsFast image augmentation library (Albumentations). 70+ transforms for classification, segmentation, object detection, keypoints, and pose estimation. Optimized OpenCV-based pipeline with unified API across all CV tasks. Supports images, masks, bounding boxes, and keypoints simultaneously. Note: classic Albumentations (MIT) is no longer maintained; successor AlbumentationsX uses AGPL-3.0. For torchvision-native augmentations, use torchvision.transforms.v2.
- aml-complianceAnti-Money Laundering (AML) and Know Your Customer (KYC) compliance workflow. Sanctions screening, PEP detection, transaction monitoring, suspicious activity reporting (SAR), and OFAC compliance.
- anki-connectThis skill is for interacting with Anki through AnkiConnect, and should be used whenever a user asks to interact with Anki, including to read or modify decks, notes, cards, models, media, or sync operations.
- approval-checkpoint-long-taskCanonical long-task pack for daemon-managed work with deliberate approval checkpoints, status summaries, rollback notes, and mobile-safe governance-aware updates.
- auditing-goal-artifactsUse when reviewing recent zorai goal run outputs, closure markers, ledgers, or evidence bundles to judge whether completion is credible or to identify remaining uncertainty.
- autogenAutoGen (Microsoft) — multi-agent conversation framework. Agent-to-agent chat, code generation & execution, tool use, group chat, and human-in-the-loop. Build collaborative AI systems with specialized agents.
- backtraderPython backtesting framework for trading strategies. Data feeds, brokers, analyzers, and live trading support. Strategy development with commission models, slippage, and signal-based execution.
- beautiful-mermaidRender Mermaid diagrams as SVG and PNG using the Beautiful Mermaid library. Use when the user asks to render a Mermaid diagram.