Diagnose and improve employee or customer happiness by analyzing four systematic components: perceived control, perceived progress, connectedness, and meaning.
Scanned 9/8/2026
Install to Claude Code
npx -y skills add sethmblack/paks-skills --skill happiness-framework-analysis --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Happiness Framework Analysis?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/sethmblack-happiness-framework-analysis)More formats (shields.io, HTML) on the badges page.
---
name: happiness-framework-analysis
description: 'Diagnose and improve employee or customer happiness by analyzing four systematic components: perceived control, perceived progress, connectedness, and meaning.'
license: MIT
metadata:
author: sethmblack
version: 1.0.4136
repository: https://github.com/sethmblack/paks-skills
keywords:
- happiness-framework-analysis
- organizational-development
- employee-engagement
- culture
---
# Happiness Framework Analysis
Diagnose and improve employee or customer happiness by analyzing four systematic components: perceived control, perceived progress, connectedness, and meaning. Based on Tony Hsieh's methodology from Zappos and "Delivering Happiness," this framework treats happiness not as random or fuzzy but as systematically buildable from measurable elements. When people are unhappy at work or as customers, the cause can typically be traced to deficits in one or more of these four elements. By diagnosing which elements are weak and designing targeted interventions, organizations can create conditions where happiness emerges naturally rather than being forced through superficial perks or "happiness theater."
---
## When to Use
- User says "Employee engagement is low" or "People are unhappy"
- User asks "How do we improve morale?"
- User wonders "Why is turnover high?"
- User wants to design employee or customer experience for happiness
- User recognizes something is wrong but cannot pinpoint it
- Analyzing team dynamics or customer satisfaction
---
## Inputs
| Input | Required | Description |
|-------|----------|-------------|
| context | Yes | Team, organization, or customer segment being analyzed |
| symptoms | No | Observable problems (turnover, complaints, disengagement) |
| existing_data | No | Survey results, feedback, exit interview themes |
| constraints | No | What changes are possible within current structure |
---
## Core Principle
Happiness is not random - it is built from four measurable elements. Perceived control creates agency, perceived progress creates momentum, connectedness creates belonging, and meaning creates purpose. When any element is severely deficient, it creates unhappiness regardless of how strong the other elements are. Authentic happiness requires real changes to these elements, not perception management or "happiness theater" that addresses surface symptoms without real change.
---
## Methodology
### Phase 1: Element Diagnosis
For each of the four elements, assess:
**1. Perceived Control**
The feeling of agency over your environment and decisions.
- High control: Autonomy, choice, empowerment, flexibility
- Low control: Micromanagement, bureaucracy, approval chains, rigid rules
**2. Perceived Progress**
The feeling of forward movement toward goals.
- High progress: Visible milestones, growth, learning, momentum
- Low progress: Stagnation, invisible effort, unclear goals, treadmill feeling
**3. Connectedness**
The quality and quantity of meaningful relationships.
- High connectedness: Belonging, team spirit, friendship, community
- Low connectedness: Isolation, politics, silos, transactional relationships
**4. Vision/Meaning**
Being part of something bigger than yourself.
- High meaning: Purpose, impact, mission clarity, contribution
- Low meaning: Pointless work, unclear purpose, disconnection from outcomes
### Phase 2: Scoring and Root Cause
1. Score each element 1-10:
- 8-10: This element is a strength
- 5-7: This element is neutral/mixed
- 1-4: This element is a deficit causing unhappiness
2. Identify root causes:
- What policies or practices affect this element?
- What structural factors create the current state?
- What is within control to change?
### Phase 3: Intervention Design
For each element scoring below 7:
1. Design interventions across three categories:
- Structural changes (policies, processes, authority)
- Experiential changes (rituals, recognition, design)
- Communication changes (transparency, framing, feedback)
2. Prioritize by impact and feasibility:
- Quick wins (high impact, easy to implement)
- Strategic investments (high impact, requires effort)
- Table for later (lower impact or blocked by constraints)
### Phase 4: Integration
1. Look for compounding effects:
- Some interventions improve multiple elements
- Some elements reinforce each other when improved
2. Watch for tradeoffs:
- Occasionally improving one element temporarily affects another
- Sequence interventions to minimize disruption
---
## Output Format
```markdown
## Happiness Analysis: [Context]
### Summary Dashboard
| Element | Score | Status | Priority |
|---------|-------|--------|----------|
| Perceived Control | X/10 | [Strength/Neutral/Deficit] | [H/M/L] |
| Perceived Progress | X/10 | [Strength/Neutral/Deficit] | [H/M/L] |
| Connectedness | X/10 | [Strength/Neutral/Deficit] | [H/M/L] |
| Vision/Meaning | X/10 | [Strength/Neutral/Deficit] | [H/M/L] |
**Primary Deficit:** [Element causing most unhappiness]
---
### Detailed Element Analysis
#### 1. Perceived Control (Score: X/10)
**Evidence:**
- [What indicates current state]
**Root Causes:**
- [Why control feels high or low]
**Interventions (if deficit):**
- [Structural change]
- [Experiential change]
---
#### 2. Perceived Progress (Score: X/10)
**Evidence:**
- [What indicates current state]
**Root Causes:**
- [Why progress feels visible or invisible]
**Interventions (if deficit):**
- [Structural change]
- [Experiential change]
---
#### 3. Connectedness (Score: X/10)
**Evidence:**
- [What indicates current state]
**Root Causes:**
- [Why relationships feel strong or weak]
**Interventions (if deficit):**
- [Structural change]
- [Experiential change]
---
#### 4. Vision/Meaning (Score: X/10)
**Evidence:**
- [What indicates current state]
**Root Causes:**
- [Why purpose feels clear or unclear]
**Interventions (if deficit):**
- [Structural change]
- [Experiential change]
---
### Priority Interventions
| Intervention | Element(s) Affected | Impact | Effort | Priority |
|-------------|---------------------|--------|--------|----------|
| [Intervention 1] | [Elements] | H/M/L | H/M/L | 1 |
| [Intervention 2] | [Elements] | H/M/L | H/M/L | 2 |
### Expected Outcomes
If interventions are implemented:
- [Predicted change in happiness]
- [Predicted change in observable symptoms]
```
---
## Constraints
- Do not use happiness analysis to manipulate employees into accepting poor conditions
- Do not design fake "happiness theater" that addresses surface symptoms without real change
- Do not recommend surveillance or measurement that damages the happiness it claims to measure
- Do not ignore systemic issues by treating happiness as individual responsibility
- Authentic happiness requires real changes, not just perception management
- Cannot substitute for fair compensation - this framework is not a cost-avoidance tool
---
## Anti-Patterns to Avoid
| Anti-Pattern | Why It Fails |
|--------------|--------------|
| "Happiness theater" - perks without real change | Free snacks don't compensate for lack of autonomy; people see through superficial fixes |
| Using framework to blame individuals | If the system creates unhappiness, individual interventions won't work |
| Measuring happiness so intrusively it damages happiness | Surveys and monitoring can create anxiety rather than insight |
| Ignoring compensation while "improving meaning" | Fair pay is foundational; this framework cannot substitute for it |
| One-time analysis without follow-up | Elements shift over time; ongoing monitoring is essential |
---
## Examples
### Example 1: Engineering Team with High Turnover
**Situation:** Engineering team of 15. Symptoms: High turnover, complaints about "no career growth," people working in isolation. Constraint: Cannot change compensation structure.
**Application:**
**Summary Dashboard:**
| Element | Score | Status | Priority |
|---------|-------|--------|----------|
| Perceived Control | 7/10 | Neutral | M |
| Perceived Progress | 3/10 | Deficit | H |
| Connectedness | 4/10 | Deficit | H |
| Vision/Meaning | 6/10 | Neutral | L |
**Primary Deficit:** Perceived Progress
**Perceived Progress (Score: 3/10)**
- Evidence: "No career growth" cited in exit interviews; unclear path to next level; achievements not recognized
- Interventions: Create visible career ladder with clear milestones; implement quarterly growth check-ins; celebrate completions publicly
**Connectedness (Score: 4/10)**
- Evidence: Team works in isolation ("heads down"); no team rituals; cross-functional collaboration rare
- Interventions: Design for "collisions" (shared spaces, pair programming); add team ritual (weekly demo); create buddy system for new engineers
### Example 2: Customer Service Team
**Situation:** Customer service team with low satisfaction scores and high absenteeism.
**Application:**
**Summary Dashboard:**
| Element | Score | Status | Priority |
|---------|-------|--------|----------|
| Perceived Control | 2/10 | Deficit | H |
| Perceived Progress | 5/10 | Neutral | M |
| Connectedness | 7/10 | Neutral | L |
| Vision/Meaning | 4/10 | Deficit | H |
**Primary Deficit:** Perceived Control
**Perceived Control (Score: 2/10)**
- Evidence: Scripted calls, no authority to resolve issues, approval needed for everything
- Root cause: Risk aversion led to removing all discretion from frontline staff
- Interventions: Create empowerment tier (decisions reps can make without approval); remove script requirements for experienced staff; define clear authority levels
**Vision/Meaning (Score: 4/10)**
- Evidence: No connection to customer outcomes; "just answering calls"
- Interventions: Share customer success stories weekly; track problems solved, not just calls handled; connect individual work to company mission
---
## Integration
**Works with:**
- Employee engagement surveys
- Exit interview analysis
- Cultural assessment frameworks
**When to prefer this skill:**
- When diagnosing the root cause of low morale or high turnover
- When designing employee or customer experience systematically
- When superficial perks haven't improved happiness
**Cautions:**
- This framework cannot substitute for fair compensation
- Some happiness issues stem from individual job fit, not systemic factors
- External factors (economic stress, life circumstances) affect happiness tooIs this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!