{"id":"77c9d6da-3039-4d4a-b1a2-c70ed2d26430","entityType":"agent","slug":"clawhub-deciqai-herzberg-two-factor","name":"Herzberg Two-Factor Theory","canonicalUrl":"https://www.xpersona.co/agent/clawhub-deciqai-herzberg-two-factor","canonicalPath":"/agent/clawhub-deciqai-herzberg-two-factor","generatedAt":"2026-10-11T07:41:14.236Z","source":"CLAWHUB","claimStatus":"UNCLAIMED","verificationTier":"NONE","summary":{"evidence":{"source":"editorial-content","verified":true,"confidence":"high","updatedAt":"2026-10-11T05:39:05.352Z","emptyReason":null},"description":"Activate when: someone says 'why isn't the team motivated,' 'we raised salaries but morale didn't improve,' 'people keep leaving for better opportunities,' '... Skill: Herzberg Two-Factor Theory Owner: deciqai Summary: Activate when: someone says 'why isn't the team motivated,' 'we raised salaries but morale didn't improve,' 'people keep leaving for better opportunities,' '... Tags: latest:1.0.5 Version history: v1.0.5 | 2026-07-16T18:02:04.371Z | user Description tail link + agents machine-readable metadata line (deciqai.com/s/herzberg-two-factor.json) v1.0.4 | 2026-07-09T1","descriptionLabel":"Technical summary","evidenceSummary":"Capability contract not published. No trust telemetry is available yet. 1.1K downloads reported by the source. Last updated 10/11/2026.","installCommand":"clawhub skill install s17a4mqcnk515kvaca5ze55d0x88pfpx:herzberg-two-factor","sourceUrl":"https://clawhub.ai/deciqai/herzberg-two-factor","homepage":"https://clawhub.ai/deciqai/skills/herzberg-two-factor","primaryLinks":[{"label":"View on ClawHub","url":"https://clawhub.ai/deciqai/herzberg-two-factor","kind":"source"},{"label":"Homepage","url":"https://clawhub.ai/deciqai/skills/herzberg-two-factor","kind":"homepage"}],"safetyScore":84,"overallRank":62,"popularityScore":61,"trustScore":null,"claimedByName":null,"isOwner":false,"seoDescription":"Activate when: someone says 'why isn't the team motivated,' 'we raised salaries but morale didn't improve,' 'people keep leaving for better opportunities,' '..."},"coverage":{"evidence":{"source":"public-profile","verified":false,"confidence":"medium","updatedAt":"2026-10-11T05:39:05.352Z","emptyReason":null},"protocols":[{"protocol":"OPENCLEW","label":"OpenClaw","status":"self-declared","notes":"Declared in the public agent profile."}],"capabilities":[],"verifiedCount":0,"selfDeclaredCount":1,"capabilityMatrix":{"rows":[{"key":"OPENCLEW","type":"protocol","support":"unknown","confidenceSource":"profile","notes":"Listed on profile"}],"flattenedTokens":"protocol:OPENCLEW|unknown|profile"}},"adoption":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-11T05:39:05.352Z","emptyReason":null},"stars":null,"forks":null,"downloads":1144,"packageName":null,"latestVersion":"1.0.5","tractionLabel":"1.1K downloads"},"release":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-11T05:39:05.292Z","emptyReason":null},"lastUpdatedAt":"2026-10-11T05:39:05.352Z","lastCrawledAt":"2026-10-11T05:39:05.292Z","lastIndexedAt":null,"nextCrawlAt":"2026-10-12T05:39:05.292Z","lastVerifiedAt":null,"highlights":[{"version":"1.0.5","createdAt":"2026-07-16T18:02:04.371Z","changelog":"Description tail link + agents machine-readable metadata line (deciqai.com/s/herzberg-two-factor.json)","fileCount":6,"zipByteSize":14324},{"version":"1.0.4","createdAt":"2026-07-09T11:18:04.447Z","changelog":"Refresh: 2024-2026 AI-era worked examples added (strategy/leadership + systems/game-theory batch)","fileCount":6,"zipByteSize":14331},{"version":"1.0.3","createdAt":"2026-07-08T11:04:46.158Z","changelog":"Footer now uses /c/<slug> short link (fixes UTM truncation when SKILL.md is read in a terminal)","fileCount":5,"zipByteSize":9698},{"version":"1.0.2","createdAt":"2026-07-08T00:49:50.970Z","changelog":"Refreshed content + GitHub star link in footer","fileCount":5,"zipByteSize":9823},{"version":"1.0.1","createdAt":"2026-07-07T20:33:50.330Z","changelog":"Add catalog categories and topics","fileCount":5,"zipByteSize":9456},{"version":"1.0.0","createdAt":"2026-06-29T06:17:37.514Z","changelog":"Initial publish","fileCount":5,"zipByteSize":9575}]},"execution":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No published capability contract is available yet."},"installCommand":"clawhub skill install s17a4mqcnk515kvaca5ze55d0x88pfpx:herzberg-two-factor","setupComplexity":"low","setupSteps":["Setup complexity is classified as HIGH. You must provision dedicated cloud infrastructure or an isolated VM. Do not run this directly on your local workstation.","Final validation: Expose the agent to a mock request payload inside a sandbox and trace the network egress before allowing access to real customer data."],"contract":{"contractStatus":"missing","authModes":[],"requires":[],"forbidden":[],"supportsMcp":false,"supportsA2a":false,"supportsStreaming":false,"inputSchemaRef":null,"outputSchemaRef":null,"dataRegion":null,"contractUpdatedAt":null,"sourceUpdatedAt":null,"freshnessSeconds":null},"invocationGuide":{"preferredApi":{"snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-deciqai-herzberg-two-factor/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-deciqai-herzberg-two-factor/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-deciqai-herzberg-two-factor/trust"},"curlExamples":["curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-deciqai-herzberg-two-factor/snapshot\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-deciqai-herzberg-two-factor/contract\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-deciqai-herzberg-two-factor/trust\""],"jsonRequestTemplate":{"query":"summarize this repo","constraints":{"maxLatencyMs":2000,"protocolPreference":["OPENCLEW"]}},"jsonResponseTemplate":{"ok":true,"result":{"summary":"...","confidence":0.9},"meta":{"source":"CLAWHUB","generatedAt":"2026-10-11T07:41:14.231Z"}},"retryPolicy":{"maxAttempts":3,"backoffMs":[500,1500,3500],"retryableConditions":["HTTP_429","HTTP_503","NETWORK_TIMEOUT"]}},"endpoints":{"dossierUrl":"https://www.xpersona.co/api/v1/agents/clawhub-deciqai-herzberg-two-factor/dossier","snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-deciqai-herzberg-two-factor/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-deciqai-herzberg-two-factor/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-deciqai-herzberg-two-factor/trust"}},"reliability":{"evidence":{"source":"runtime-metrics","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No trust, reliability, or runtime telemetry is available."},"trust":{"status":"unavailable","handshakeStatus":"UNKNOWN","verificationFreshnessHours":null,"reputationScore":null,"p95LatencyMs":null,"successRate30d":null,"fallbackRate":null,"attempts30d":null,"trustUpdatedAt":null,"trustConfidence":"unknown","sourceUpdatedAt":null,"freshnessSeconds":null},"decisionGuardrails":{"doNotUseIf":["Contract metadata is missing or unavailable for deterministic execution."],"safeUseWhen":[],"riskFlags":["missing_or_unavailable_contract","trust_data_unavailable","schema_references_missing"],"operationalConfidence":"low"},"executionMetrics":{"observedLatencyMsP50":null,"observedLatencyMsP95":null,"estimatedCostUsd":null,"uptime30d":null,"rateLimitRpm":null,"rateLimitBurst":null,"lastVerifiedAt":null,"verificationSource":null},"runtimeMetrics":{"successRate":null,"avgLatencyMs":null,"avgCostUsd":null,"hallucinationRate":null,"retryRate":null,"disputeRate":null,"p50Latency":null,"p95Latency":null,"lastUpdated":null}},"benchmarks":{"evidence":{"source":"no-benchmark-data","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No benchmark suites or observed failure patterns are available."},"suites":[],"failurePatterns":[]},"artifacts":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"high","updatedAt":"2026-10-11T05:39:05.352Z","emptyReason":null},"readme":"Skill: Herzberg Two-Factor Theory\n\nOwner: deciqai\n\nSummary: Activate when: someone says 'why isn't the team motivated,' 'we raised salaries but morale didn't improve,' 'people keep leaving for better opportunities,' '...\n\nTags: latest:1.0.5\n\nVersion history:\n\nv1.0.5 | 2026-07-16T18:02:04.371Z | user\n\nDescription tail link + agents machine-readable metadata line (deciqai.com/s/herzberg-two-factor.json)\n\nv1.0.4 | 2026-07-09T11:18:04.447Z | user\n\nRefresh: 2024-2026 AI-era worked examples added (strategy/leadership + systems/game-theory batch)\n\nv1.0.3 | 2026-07-08T11:04:46.158Z | user\n\nFooter now uses /c/<slug> short link (fixes UTM truncation when SKILL.md is read in a terminal)\n\nv1.0.2 | 2026-07-08T00:49:50.970Z | user\n\nRefreshed content + GitHub star link in footer\n\nv1.0.1 | 2026-07-07T20:33:50.330Z | user\n\nAdd catalog categories and topics\n\nv1.0.0 | 2026-06-29T06:17:37.514Z | user\n\nInitial publish\n\nArchive index:\n\nArchive v1.0.5: 6 files, 14324 bytes\n\nFiles: examples/herzbergs-pittsburgh-study-and-the-critical-incident-method-1959.md (3610b), examples/retaining-scarce-ai-ml-talent-2024-2026.md (7568b), references/sources.md (3533b), skill-card.md (2693b), SKILL.md (10331b), _meta.json (138b)\n\nFile v1.0.5:SKILL.md\n\n---\nname: herzberg-two-factor\ndescription: \"Activate when: someone says 'why isn't the team motivated,' 'we raised salaries but morale didn't improve,' 'people keep leaving for better opportunities,' 'employee engagement is low,' 'how do I retain engineers,' or when designing compensation, job roles, or performance systems.\n  Do NOT activate when: the problem is a skill gap (people lack capability, not motivation); or the worker is in extreme economic precarity where basic survival income is the issue. More: deciqai.com/c/herzberg-two-factor\"\n---\n\n# Herzberg Two-Factor Theory\n\n## Overview\n\nHerzberg's 1959 Pittsburgh study found satisfaction and dissatisfaction are **two independent axes**. **Hygiene factors** (salary, working conditions, job security) only remove dissatisfaction — never create motivation. **Motivators** (achievement, recognition, responsibility, growth, the work itself) create genuine engagement. More hygiene spending never produces motivation; only **job enrichment** — redesigning work for higher responsibility and autonomy — does.\n\n**Composition with neighbors:** Use principal-agent when incentive structures keep failing (designers mistake hygiene for motivators). Use nudge-theory after Herzberg to design low-friction paths to the motivating actions identified.\n\n## When to Use\n\n- Team shows **adequate performance but low energy** — people meet the minimum but go no further\n- Talent **leaving for \"better opportunities\"** and exit interviews are uninformative\n- **Compensation recently increased** but morale didn't improve, or reset within months\n- **Designing** compensation structure, job role, or performance review system\n- **Bidding wars for scarce AI/ML talent** — matched counter-offers still lose people; AI-capex-driven pay bands keep rising but engagement doesn't follow (an AI-native competitor is out-motivating, not just out-paying, you)\n- Someone says: *\"motivation,\" \"engagement,\" \"retention,\" \"why isn't the team energized\"*\n\n**When NOT to use:** Clear hygiene gap exists (salary below market, unsafe conditions) — fix those first. Skill gap, not motivation gap. Very short time horizon (72-hour sprint).\n\n## Coaching Novices (Adaptive Front Door)\n\n- **Engine mode:** specific team/role described → run The Process directly.\n- **Coach mode:** unfamiliar or no concrete case → guide step by step.\n\nIn Coach mode, respond one step at a time. Each [WAIT] is a hard stop — output only that step's question, then stop.\n\n1. One-line what-it-is: salary/benefits can only *remove unhappiness* — only challenging work, real responsibility, and recognition for achievement create genuine motivation.\n2. Check fit against When to Use / When NOT to use. If clear hygiene gap exists, redirect to fixing hygiene first.\n3. Elicit their real case — \"people aren't motivated\" is not a case; get the specific behavioral signal.\n> **[WAIT — do not advance until user responds]**\n4. Classify each complaint/satisfaction item as hygiene or motivator one at a time before prescribing.\n> **[WAIT — do not advance until user responds]**\n5. Close: \"The reason raising salary didn't fix this is ___. The one motivator intervention most likely to move engagement here is ___.\"\n> **[WAIT — do not advance until user responds]**\n\n## The Process\n\nRun the **Two-Factor Diagnosis**. **Stop-rule:** if Step 2 reveals clear hygiene gaps (pay below market, unsafe environment), stop and address those before any motivator work.\n\n1. **Collect complaint/satisfaction inventory** via exit interviews, stay interviews, 1:1s, or surveys — specific behavioral events, not abstract ratings.\n2. **Classify each item:** Hygiene (context of work: salary, benefits, security, working conditions, policy, supervision, peer relationships) vs. Motivator (content of work: achievement, recognition for achievement, work itself, responsibility/autonomy, growth/advancement). Classification test: if removing it causes active unhappiness but adding more habituates quickly → hygiene.\n3. **Assess hygiene baseline** vs. market standard. Set a \"hygiene floor\" — the threshold where it no longer drives active dissatisfaction. Prioritize: salary → job security → working conditions → interpersonal environment.\n4. **Diagnose motivator gaps** across five core motivators: Achievement (challenging, completable goals?), Recognition (specific, prompt, tied to achievement?), Work itself (varied, challenging?), Responsibility (real ownership?), Growth (visible path forward?).\n5. **Design job enrichment (vertical loading):** remove procedural controls while keeping accountability; give direct feedback from the work; assign whole units of work; add direct client/user contact; increase technical scope. Not horizontal loading (more same-type tasks).\n6. **Monitor and iterate** quarterly — hygiene satisfaction habituates in weeks; motivator satisfaction is durable but evolves as people grow.\n\n### Output: Two-Factor Diagnosis\n\n```\n# Two-Factor Diagnosis: <team / role>\nHygiene floor status: <below / at / above floor> | Required fixes: <>\n| Hygiene Factor | Current | Market std | Gap | Priority |\n| Motivator | Signal (strong/weak/absent) | Evidence |\nPrimary motivator gap: <>\n| Enrichment Intervention | Motivator targeted | What changes | Owner |\nMonitoring: hygiene cadence <> | motivator cadence <> | lead indicator <>\n```\n\n*→ Method in Action: [Herzberg's Pittsburgh Study and the Critical Incident Method (1959)](examples/herzbergs-pittsburgh-study-and-the-critical-incident-method-1959.md)*\n\n*→ 2026 lens: [Retaining Scarce AI/ML Talent in a Red-Hot Market (2024–2026)](examples/retaining-scarce-ai-ml-talent-2024-2026.md)*\n\n## Motivation Packs\n\n- **Software engineering:** hygiene failures = opaque promotion, inconsistent code review. Motivators: full-feature ownership, tech decision authority, open-source/conference recognition.\n- **Early-stage startups:** fix hygiene (salary at living-cost threshold, equity clarity) before mission rhetoric — narrative doesn't motivate someone who can't pay rent.\n- **Sales:** commission is hygiene when expected at market; becomes motivator only tied to specific achievement. Recognize wins publicly; give territory/account ownership.\n- **Product management:** dominant gap = work fragmentation (PMs as request-gatherers). Enrichment: direct user access, full problem-space ownership, visible path to measurable outcomes.\n\n## Applying It Well\n\n- Fix hygiene to the floor, not best-in-class — above-market hygiene costs more with zero retention advantage.\n- Salary raises decay in weeks; design for motivators, not raises.\n- Recognition must be specific, proximate, and tied to a named achievement — not generic and annual.\n- Vertical loading only: more authority, accountability, direct feedback, complete ownership — not more tasks of the same type.\n- Motivators habituate upward; job enrichment is continuous design, not a one-time fix.\n\n*→ Primary sources: [references/sources.md](references/sources.md)*\n\n## Common Rationalizations\n\n**[D] = designed upfront | [O] = observed in real use. [O] entries are more valuable.**\n\n| Fake move | Reality |\n|---|---|\n| [D] **\"We gave everyone a 15% raise and retention improved, so salary is a motivator.\"** | Short-term retention = hygiene restoration. Track the same cohort 6–12 months: discretionary effort returns to pre-raise baseline. |\n| [D] **\"Our employees say they care most about compensation in surveys.\"** | Surveys skew toward hygiene factors (legible, discussable). Critical incident data consistently surfaces achievement and recognition as primary. |\n| [D] **\"We added flexible hours and a gym benefit — that should help motivation.\"** | Both are hygiene factors. Neither creates engagement when work is unchallenging and responsibility is absent. |\n| [D] **\"If we give people more autonomy, they'll make mistakes.\"** | Studies show increased autonomy improves both performance and retention when paired with clear accountability structures. |\n| [D] **\"We recognize people with annual awards.\"** | Annual generic awards sever the motivational connection. Recognition must be specific, proximate, and tied to a named achievement. |\n| [D] **\"Our engineers leave for Google salaries — this is a hygiene problem.\"** | When they leave for similar-level roles at similar salaries, it's almost always a motivator failure wearing hygiene language in the exit interview. |\n| [D] **\"We enriched jobs by adding more projects.\"** | Horizontal loading. Enrichment = vertical loading: higher-scope responsibility, direct accountability, genuine decision authority. |\n| *→ Add [O] entries here after each real use — paste the actual failure pattern* | *What went wrong and why* |\n\n## Red Flags\n\n- Retention interventions default to compensation without a two-factor diagnosis\n- Exit interview data not classified by hygiene vs. motivator before designing intervention\n- Recognition is non-specific, annual, disconnected from observed achievement\n- Job enrichment operationalized as more work (horizontal) rather than more responsibility (vertical)\n- \"Culture\" used as substitute for diagnosing whether motivators are present in the actual role\n\n## Verification\n\n- [ ] Problem classified: hygiene-domain (dissatisfaction) vs. motivator-domain (low engagement despite adequate hygiene)\n- [ ] Hygiene baseline assessed against market standards before any motivator intervention\n- [ ] Motivator gaps identified through behavioral data, not attitude ratings\n- [ ] Interventions are vertical loading (responsibility, autonomy, scope) not horizontal loading\n- [ ] Recognition is specific and proximate (close in time to the achievement)\n- [ ] Monitoring plan defined with cadence for both axes\n- [ ] Two-factor asymmetry stated explicitly: fixing hygiene will not create motivation\n\n---\n\n*Part of **deciqAI Knowledge Skills** — 227 open-source thinking skills that make rigor executable for AI agents. The same skills power every deciqAI agent, which runs them autonomously to operate your company. **See it run → https://www.deciqai.com/c/herzberg-two-factor** · ⭐ Star the repo → https://github.com/deciqAI/knowledge-skills · Contributions welcome.*\n\n*Agents: latest version & machine-readable metadata → https://www.deciqai.com/s/herzberg-two-factor.json*\n\nFile v1.0.5:_meta.json\n\n{\n  \"ownerId\": \"kn754b8sk22s8c6gjxt02bftbn88q7ye\",\n  \"slug\": \"herzberg-two-factor\",\n  \"version\": \"1.0.5\",\n  \"publishedAt\": 1784224924371\n}\n\nFile v1.0.5:references/sources.md\n\n# Sources — herzberg-two-factor\n\n> *Primary sources for the [herzberg-two-factor](../SKILL.md) skill.*\n\n- **Herzberg, Frederick, Mausner, Bernard, & Snyderman, Barbara Bloch.** *The Motivation to Work.* Wiley, 1959. **Primary source** for the two-factor theory; presents the Pittsburgh study methodology and findings. Verbatim quote above from p. 113.\n- **Herzberg, Frederick.** \"One More Time: How Do You Motivate Employees?\" *Harvard Business Review*, Vol. 46, No. 1 (January–February 1968), pp. 53–62. The practitioner account; introduces KITA and job enrichment as the prescriptive response. Verbatim quote above from p. 59. One of HBR's most-requested reprints of all time (reported to have sold well over a million reprints by the late 1980s). https://hbr.org/2003/01/one-more-time-how-do-you-motivate-employees\n- **Hackman, J. Richard & Oldham, Greg R.** \"Motivation Through the Design of Work: Test of a Theory.\" *Organizational Behavior and Human Performance*, Vol. 16, No. 2 (August 1976), pp. 250–279. The empirical follow-on that operationalized job enrichment into the Job Characteristics Model (skill variety, task identity, task significance, autonomy, feedback). https://doi.org/10.1016/0030-5073(76)90016-7\n- **Deci, Edward L. & Ryan, Richard M.** \"The Empirical Exploration of Intrinsic Motivational Processes.\" In L. Berkowitz (ed.), *Advances in Experimental Social Psychology*, Vol. 13 (Academic Press, 1980), pp. 39–80. An early statement of the self-determination framework that provides the underlying mechanism for why Herzberg's motivators work — autonomy, competence, and relatedness as basic psychological needs. https://doi.org/10.1016/S0065-2601(08)60130-6\n- **Flanagan, John C.** \"The Critical Incident Technique.\" *Psychological Bulletin*, Vol. 51, No. 4 (July 1954), pp. 327–358. The methodological source for the data collection technique Herzberg used; establishes what critical incident data actually measures and its limitations. https://doi.org/10.1037/h0061470\n- **Ryan, Richard M. & Deci, Edward L.** *Self-Determination Theory: Basic Psychological Needs in Motivation, Development, and Wellness.* Guilford Press, 2017. The consolidated modern statement of SDT — autonomy, competence, and relatedness — which supplies the mechanism for why Herzberg's motivators (responsibility, achievement, growth) durably drive engagement while hygiene (pay, conditions) does not. Used to ground the 2024–2026 AI-talent example.\n- **Contemporary AI-talent market context (2024–2026):** Public business reporting through 2024–2025 broadly documented (a) record capital-expenditure commitments to AI infrastructure by major AI labs and hyperscalers, and (b) sharply elevated compensation and aggressive cross-lab recruiting for scarce frontier AI/ML researchers and engineers. These are widely-reported, durable market facts used as *setting* for the example; no single proprietary figure or specific dollar amount is asserted as evidence here. Confirm current specifics against primary reporting before quoting numbers.\n- **Not cited as evidence:** Generic management consulting surveys (\"% of employees are disengaged\") that do not distinguish hygiene and motivator dimensions are not cited here. They measure aggregate satisfaction without the two-factor decomposition, making them unsuitable for prescriptive use in this framework. Gallup Q12 scores, for example, conflate hygiene and motivator items. Use the framework to design data collection that separates the two dimensions.\n\nFile v1.0.5:examples/herzbergs-pittsburgh-study-and-the-critical-incident-method-1959.md\n\n# Method in Action: Herzberg's Pittsburgh Study and the Critical Incident Method (1959)\n\n> *Example for the [herzberg-two-factor](../SKILL.md) skill.*\n\nThe primary-source case is the original research itself — 203 accountants and engineers in Pittsburgh, 1844 incidents coded and analyzed. This is not a retrospective pop account; it is the founding empirical event.\n\n**Behavioral specification (Step 1):** Herzberg, Mausner, and Snyderman used the critical incident technique (developed by John Flanagan at the American Institutes for Research): ask people to describe a specific time at work when they felt exceptionally good or bad, what the circumstances were, what led to those feelings, and how long the feeling lasted. This produces behavioral data, not attitude ratings — it forces respondents to name actual events.\n\n**Classification (Step 2):** Across 1,844 coded incidents, the researchers found a systematic asymmetry. Factors cited when people felt *good* were predominantly: achievement (a project completed, a problem solved, a sale made), recognition (being told specifically that they had done something well), the work itself (finding the work engaging, varied, or demanding), responsibility (having real authority over outcomes), and advancement. Factors cited when people felt *bad* were predominantly: company policy and administration (arbitrary or bureaucratic rules), supervision (incompetent or unfair managers), working conditions, salary (not \"too little\" but the *process* — arbitrary raises, opaque criteria), and interpersonal relations.\n\n**Hygiene assessment (Step 3):** Salary appeared in the \"bad feelings\" data as a consistent factor — not the amount per se, but the *unfairness or opacity* of the salary process. When salary was perceived as fairly administered and at or above market, it did not appear as a satisfaction driver; it was simply absent from the \"good feelings\" accounts.\n\n**Motivator gap (Step 4):** The most powerful single predictor of extreme positive feelings was *achievement* — a concrete sense of having accomplished something. The second was *recognition* specifically tied to achievement. What was largely absent from either list: salary increases, benefits improvements, or office upgrades on the positive side; lack of achievement or recognition on the negative side.\n\n**Enrichment prescription (Step 5):** Herzberg's prescriptive conclusion — developed at length in the 1968 HBR article — was that companies systematically over-invested in KITA (Kick In The Ass, his term for hygiene interventions: raises, perks, threats) and under-invested in job enrichment. The practical prescription: increase the vertical complexity of jobs by giving people genuine ownership of outcomes, removing supervisory controls while maintaining accountability, providing direct feedback from the work, and creating visible advancement paths.\n\n**Legacy (Step 6):** The *Motivation to Work* has been cited over 1.4 million times according to Google Scholar. Herzberg's subsequent studies replicated the finding across 12 countries and multiple occupational groups, with consistent core results: the two-factor asymmetry holds across cultural contexts for knowledge workers, though the specific factor weights shift.\n\n**Sources:** Herzberg, Frederick, Mausner, Bernard, & Snyderman, Barbara Bloch. *The Motivation to Work.* Wiley, 1959. Herzberg, Frederick. \"One More Time: How Do You Motivate Employees?\" *Harvard Business Review*, Vol. 46, No. 1 (January–February 1968), pp. 53–62. https://hbr.org/2003/01/one-more-time-how-do-you-motivate-employees\n\nFile v1.0.5:examples/retaining-scarce-ai-ml-talent-2024-2026.md\n\n# Method in Action: Retaining Scarce AI/ML Talent in a Red-Hot Market (2024–2026)\n\n> *Example for the [herzberg-two-factor](../SKILL.md) skill.*\n\nBetween 2024 and 2026 the market for frontier AI/ML researchers and engineers became one of the most extreme talent markets in the history of the technology industry. Multiple large AI labs and hyperscalers publicly committed to unprecedented capital spending on AI infrastructure, and compensation for scarce senior AI talent reached widely reported levels far above typical software-engineering pay. Press reporting through late 2025 documented aggressive cross-lab poaching, headline-grabbing offers, and public statements from lab leaders about retention pressure. This is a textbook setting for the two-factor asymmetry: a market where *pay is table-stakes hygiene*, so throwing more money at retention often fails to move engagement — yet leaders keep reaching for it because it is the most legible lever.\n\nThe anchor case: a well-funded AI product company (Series B+, ~40 ML/research staff) sees its most valuable researchers being recruited away, and its instinct is to counter every offer with cash. This example runs that situation through the skill's Process.\n\n**Step 1 — Collect complaint/satisfaction inventory (specific behavioral events, not ratings).** Instead of an engagement survey, run stay interviews and code recent departures as critical incidents. Illustrative events the company surfaces: a departing researcher who left despite a matched counter-offer said the deciding factor was that a competitor let her own a research direction end-to-end rather than service a product roadmap; an engineer who stayed cited a specific week where he shipped a model improvement directly to production and saw the metric move; a complaint recurring in 1:1s is that model-launch decisions are made two layers up and researchers learn of them after the fact; another complaint is that GPU allocation and experiment approval require slow, opaque sign-off. These are events, not opinions.\n\n**Step 2 — Classify each item as hygiene or motivator.** Cash compensation and equity: hygiene (in this market, absence below the top-lab band drives active dissatisfaction, but matching it produces no durable engagement — the classic \"we matched the offer and they left anyway\"). Compute access being throttled by slow approval: hygiene (a *working-conditions* failure — the tooling of the job). Owning a research direction end-to-end: motivator (responsibility + the work itself). Shipping to production and seeing the metric move: motivator (achievement + direct feedback from the work). Being excluded from launch decisions: a motivator gap (responsibility withheld). The classification test from the skill applies: matched pay habituates within weeks; direction-ownership does not.\n\n**Step 3 — Assess hygiene baseline vs. market and set the floor.** In the 2024–2026 market the hygiene floor for scarce AI talent moved sharply upward, so the floor must be re-benchmarked against *frontier-lab* bands, not generic software bands. Prioritize per the skill: salary/equity to a credible top-tier-competitive band → job security (fundraising runway clarity so people aren't gambling on the company surviving the capex arms race) → working conditions (here, *compute and tooling latency* is the dominant condition — abundant GPU access and fast experiment turnaround). Stop-rule check: if pay is below the frontier band, fix that *first* — mission rhetoric does not retain a researcher fielding a doubled offer. But once at the floor, additional cash buys little retention; that is the asymmetry.\n\n**Step 4 — Diagnose motivator gaps across the five motivators.** Achievement: weak — researchers rarely see their work reach users; results die in internal decks. Recognition: weak — no specific, prompt acknowledgment tied to a shipped result; recognition is annual and generic. Work itself: mixed — genuinely frontier problems exist, but they are fragmented into roadmap-service tasks. Responsibility: absent — direction and launch calls sit two layers up. Growth: unclear — no visible path from IC researcher to owning a research agenda. The primary motivator gap here is **responsibility (real ownership of a research direction)**, closely followed by **achievement made visible (work reaching production and being recognized promptly)**.\n\n**Step 5 — Design job enrichment (vertical loading).** Give named researchers genuine ownership of a research direction with real decision authority over approach — not more assignments (that would be horizontal loading). Remove the procedural control on compute: replace slow sign-off with a standing per-researcher compute budget they spend at their own discretion, while keeping accountability for results. Give direct feedback from the work: instrument a path so a researcher's model change ships to real users and they see the metric, closing the achievement loop. Add direct user/customer contact for researchers whose work touches the product. Make recognition specific and proximate — acknowledge a named shipped result the week it lands, not at the annual review. Create a visible growth ladder from IC to research-lead that is about scope of ownership, not headcount managed.\n\n**Step 6 — Monitor and iterate on two cadences.** Track hygiene on a slower cadence (re-benchmark comp against frontier bands roughly semi-annually as the market moves) but expect its retention effect to habituate within weeks. Track motivators as the *lead indicator*: quarterly stay interviews coded for whether researchers report ownership, shipped-and-recognized achievement, and a visible path. The trap to watch, straight from the skill's rationalizations: a wave of cash counter-offers will show a short-term retention bump; follow the same cohort 6–12 months out — if the ownership and achievement gaps weren't closed, discretionary effort and attrition revert to baseline, and you will have paid frontier-band premiums for hygiene restoration with no motivation gained.\n\n**Takeaway.** In the 2024–2026 AI talent market, competitive compensation is a *necessary* hygiene floor — set it against frontier-lab bands or you lose people outright. But it is not what makes scarce researchers stay and do their best work. The durable retention lever is motivator design: frontier problems owned end-to-end, autonomy over compute and approach, and achievement that reaches users and is recognized promptly.\n\n*Sources: Herzberg, Frederick, Mausner, Bernard, & Snyderman, Barbara Bloch. *The Motivation to Work.* Wiley, 1959. Herzberg, Frederick, \"One More Time: How Do You Motivate Employees?\" *Harvard Business Review* 46, no. 1 (Jan–Feb 1968): 53–62, https://hbr.org/2003/01/one-more-time-how-do-you-motivate-employees. Deci, Edward L. & Ryan, Richard M., \"The Empirical Exploration of Intrinsic Motivational Processes,\" in L. Berkowitz (ed.), *Advances in Experimental Social Psychology*, Vol. 13 (Academic Press, 1980): 39–80 (mechanism for why autonomy/mastery motivate); further developed in Ryan & Deci, *Self-Determination Theory*, Guilford Press, 2017. Contemporary market context (record AI infrastructure capex commitments by major labs/hyperscalers, and widely reported elevated compensation and cross-lab recruiting for scarce AI/ML talent through 2024–2025) is drawn from broad, well-documented public business reporting rather than any single proprietary figure; specific dollar amounts are deliberately not asserted here.*\n\nFile v1.0.5:skill-card.md\n\n## Description:\n\nActivates for workplace motivation, engagement, retention, compensation, job-role, and performance-system questions where Herzberg's hygiene-versus-motivator framework can guide diagnosis and job enrichment.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[deciqai](https://clawhub.ai/user/deciqai)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nEmployees, managers, founders, and people-operations teams use this skill to diagnose low engagement or retention problems by separating hygiene gaps from true motivator gaps. It helps produce a two-factor diagnosis and job-enrichment guidance before choosing compensation, recognition, autonomy, or growth interventions.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: Sensitive employee, compensation, or exit-interview details could be exposed if users paste them into persistent examples, shared notes, or reusable skill artifacts.\n\nMitigation: Anonymize or omit confidential employee details before using the skill in persistent or shared contexts.\n\nRisk: The framework can produce poor workplace guidance when applied to a skill gap, unsafe conditions, below-market pay, or other unresolved hygiene failure.\n\nMitigation: Apply the skill's stop-rule: address clear hygiene gaps or capability gaps before using motivator interventions.\n\n## Reference(s):\n\n- [Sources - herzberg-two-factor](references/sources.md)\n- [Herzberg's Pittsburgh Study and the Critical Incident Method (1959)](examples/herzbergs-pittsburgh-study-and-the-critical-incident-method-1959.md)\n- [Retaining Scarce AI/ML Talent in a Red-Hot Market (2024-2026)](examples/retaining-scarce-ai-ml-talent-2024-2026.md)\n- [One More Time: How Do You Motivate Employees?](https://hbr.org/2003/01/one-more-time-how-do-you-motivate-employees)\n- [Motivation Through the Design of Work](https://doi.org/10.1016/0030-5073(76)90016-7)\n- [The Critical Incident Technique](https://doi.org/10.1037/h0061470)\n- [Skill release page](https://clawhub.ai/deciqai/skills/herzberg-two-factor)\n\n## Skill Output:\n\n**Output Type(s):** [guidance, markdown, analysis]\n\n**Output Format:** [Markdown diagnosis, coaching prompts, and structured tables]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [May ask step-by-step follow-up questions before producing recommendations.]\n\n## Skill Version(s):\n\n1.0.5 (source: server release evidence)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nArchive v1.0.4: 6 files, 14331 bytes\n\nFiles: examples/herzbergs-pittsburgh-study-and-the-critical-incident-method-1959.md (3610b), examples/retaining-scarce-ai-ml-talent-2024-2026.md (7568b), references/sources.md (3533b), skill-card.md (2935b), SKILL.md (10182b), _meta.json (138b)\n\nFile v1.0.4:SKILL.md\n\n---\nname: herzberg-two-factor\ndescription: \"Activate when: someone says 'why isn't the team motivated,' 'we raised salaries but morale didn't improve,' 'people keep leaving for better opportunities,' 'employee engagement is low,' 'how do I retain engineers,' or when designing compensation, job roles, or performance systems.\n  Do NOT activate when: the problem is a skill gap (people lack capability, not motivation); or the worker is in extreme economic precarity where basic survival income is the issue.\"\n---\n\n# Herzberg Two-Factor Theory\n\n## Overview\n\nHerzberg's 1959 Pittsburgh study found satisfaction and dissatisfaction are **two independent axes**. **Hygiene factors** (salary, working conditions, job security) only remove dissatisfaction — never create motivation. **Motivators** (achievement, recognition, responsibility, growth, the work itself) create genuine engagement. More hygiene spending never produces motivation; only **job enrichment** — redesigning work for higher responsibility and autonomy — does.\n\n**Composition with neighbors:** Use principal-agent when incentive structures keep failing (designers mistake hygiene for motivators). Use nudge-theory after Herzberg to design low-friction paths to the motivating actions identified.\n\n## When to Use\n\n- Team shows **adequate performance but low energy** — people meet the minimum but go no further\n- Talent **leaving for \"better opportunities\"** and exit interviews are uninformative\n- **Compensation recently increased** but morale didn't improve, or reset within months\n- **Designing** compensation structure, job role, or performance review system\n- **Bidding wars for scarce AI/ML talent** — matched counter-offers still lose people; AI-capex-driven pay bands keep rising but engagement doesn't follow (an AI-native competitor is out-motivating, not just out-paying, you)\n- Someone says: *\"motivation,\" \"engagement,\" \"retention,\" \"why isn't the team energized\"*\n\n**When NOT to use:** Clear hygiene gap exists (salary below market, unsafe conditions) — fix those first. Skill gap, not motivation gap. Very short time horizon (72-hour sprint).\n\n## Coaching Novices (Adaptive Front Door)\n\n- **Engine mode:** specific team/role described → run The Process directly.\n- **Coach mode:** unfamiliar or no concrete case → guide step by step.\n\nIn Coach mode, respond one step at a time. Each [WAIT] is a hard stop — output only that step's question, then stop.\n\n1. One-line what-it-is: salary/benefits can only *remove unhappiness* — only challenging work, real responsibility, and recognition for achievement create genuine motivation.\n2. Check fit against When to Use / When NOT to use. If clear hygiene gap exists, redirect to fixing hygiene first.\n3. Elicit their real case — \"people aren't motivated\" is not a case; get the specific behavioral signal.\n> **[WAIT — do not advance until user responds]**\n4. Classify each complaint/satisfaction item as hygiene or motivator one at a time before prescribing.\n> **[WAIT — do not advance until user responds]**\n5. Close: \"The reason raising salary didn't fix this is ___. The one motivator intervention most likely to move engagement here is ___.\"\n> **[WAIT — do not advance until user responds]**\n\n## The Process\n\nRun the **Two-Factor Diagnosis**. **Stop-rule:** if Step 2 reveals clear hygiene gaps (pay below market, unsafe environment), stop and address those before any motivator work.\n\n1. **Collect complaint/satisfaction inventory** via exit interviews, stay interviews, 1:1s, or surveys — specific behavioral events, not abstract ratings.\n2. **Classify each item:** Hygiene (context of work: salary, benefits, security, working conditions, policy, supervision, peer relationships) vs. Motivator (content of work: achievement, recognition for achievement, work itself, responsibility/autonomy, growth/advancement). Classification test: if removing it causes active unhappiness but adding more habituates quickly → hygiene.\n3. **Assess hygiene baseline** vs. market standard. Set a \"hygiene floor\" — the threshold where it no longer drives active dissatisfaction. Prioritize: salary → job security → working conditions → interpersonal environment.\n4. **Diagnose motivator gaps** across five core motivators: Achievement (challenging, completable goals?), Recognition (specific, prompt, tied to achievement?), Work itself (varied, challenging?), Responsibility (real ownership?), Growth (visible path forward?).\n5. **Design job enrichment (vertical loading):** remove procedural controls while keeping accountability; give direct feedback from the work; assign whole units of work; add direct client/user contact; increase technical scope. Not horizontal loading (more same-type tasks).\n6. **Monitor and iterate** quarterly — hygiene satisfaction habituates in weeks; motivator satisfaction is durable but evolves as people grow.\n\n### Output: Two-Factor Diagnosis\n\n```\n# Two-Factor Diagnosis: <team / role>\nHygiene floor status: <below / at / above floor> | Required fixes: <>\n| Hygiene Factor | Current | Market std | Gap | Priority |\n| Motivator | Signal (strong/weak/absent) | Evidence |\nPrimary motivator gap: <>\n| Enrichment Intervention | Motivator targeted | What changes | Owner |\nMonitoring: hygiene cadence <> | motivator cadence <> | lead indicator <>\n```\n\n*→ Method in Action: [Herzberg's Pittsburgh Study and the Critical Incident Method (1959)](examples/herzbergs-pittsburgh-study-and-the-critical-incident-method-1959.md)*\n\n*→ 2026 lens: [Retaining Scarce AI/ML Talent in a Red-Hot Market (2024–2026)](examples/retaining-scarce-ai-ml-talent-2024-2026.md)*\n\n## Motivation Packs\n\n- **Software engineering:** hygiene failures = opaque promotion, inconsistent code review. Motivators: full-feature ownership, tech decision authority, open-source/conference recognition.\n- **Early-stage startups:** fix hygiene (salary at living-cost threshold, equity clarity) before mission rhetoric — narrative doesn't motivate someone who can't pay rent.\n- **Sales:** commission is hygiene when expected at market; becomes motivator only tied to specific achievement. Recognize wins publicly; give territory/account ownership.\n- **Product management:** dominant gap = work fragmentation (PMs as request-gatherers). Enrichment: direct user access, full problem-space ownership, visible path to measurable outcomes.\n\n## Applying It Well\n\n- Fix hygiene to the floor, not best-in-class — above-market hygiene costs more with zero retention advantage.\n- Salary raises decay in weeks; design for motivators, not raises.\n- Recognition must be specific, proximate, and tied to a named achievement — not generic and annual.\n- Vertical loading only: more authority, accountability, direct feedback, complete ownership — not more tasks of the same type.\n- Motivators habituate upward; job enrichment is continuous design, not a one-time fix.\n\n*→ Primary sources: [references/sources.md](references/sources.md)*\n\n## Common Rationalizations\n\n**[D] = designed upfront | [O] = observed in real use. [O] entries are more valuable.**\n\n| Fake move | Reality |\n|---|---|\n| [D] **\"We gave everyone a 15% raise and retention improved, so salary is a motivator.\"** | Short-term retention = hygiene restoration. Track the same cohort 6–12 months: discretionary effort returns to pre-raise baseline. |\n| [D] **\"Our employees say they care most about compensation in surveys.\"** | Surveys skew toward hygiene factors (legible, discussable). Critical incident data consistently surfaces achievement and recognition as primary. |\n| [D] **\"We added flexible hours and a gym benefit — that should help motivation.\"** | Both are hygiene factors. Neither creates engagement when work is unchallenging and responsibility is absent. |\n| [D] **\"If we give people more autonomy, they'll make mistakes.\"** | Studies show increased autonomy improves both performance and retention when paired with clear accountability structures. |\n| [D] **\"We recognize people with annual awards.\"** | Annual generic awards sever the motivational connection. Recognition must be specific, proximate, and tied to a named achievement. |\n| [D] **\"Our engineers leave for Google salaries — this is a hygiene problem.\"** | When they leave for similar-level roles at similar salaries, it's almost always a motivator failure wearing hygiene language in the exit interview. |\n| [D] **\"We enriched jobs by adding more projects.\"** | Horizontal loading. Enrichment = vertical loading: higher-scope responsibility, direct accountability, genuine decision authority. |\n| *→ Add [O] entries here after each real use — paste the actual failure pattern* | *What went wrong and why* |\n\n## Red Flags\n\n- Retention interventions default to compensation without a two-factor diagnosis\n- Exit interview data not classified by hygiene vs. motivator before designing intervention\n- Recognition is non-specific, annual, disconnected from observed achievement\n- Job enrichment operationalized as more work (horizontal) rather than more responsibility (vertical)\n- \"Culture\" used as substitute for diagnosing whether motivators are present in the actual role\n\n## Verification\n\n- [ ] Problem classified: hygiene-domain (dissatisfaction) vs. motivator-domain (low engagement despite adequate hygiene)\n- [ ] Hygiene baseline assessed against market standards before any motivator intervention\n- [ ] Motivator gaps identified through behavioral data, not attitude ratings\n- [ ] Interventions are vertical loading (responsibility, autonomy, scope) not horizontal loading\n- [ ] Recognition is specific and proximate (close in time to the achievement)\n- [ ] Monitoring plan defined with cadence for both axes\n- [ ] Two-factor asymmetry stated explicitly: fixing hygiene will not create motivation\n\n---\n\n*Part of **deciqAI Knowledge Skills** — 189 open-source thinking skills that make rigor executable for AI agents. The same skills power every deciqAI agent, which runs them autonomously to operate your company. **See it run → https://www.deciqai.com/c/herzberg-two-factor** · ⭐ Star the repo → https://github.com/deciqAI/knowledge-skills · Contributions welcome.*\n\nFile v1.0.4:_meta.json\n\n{\n  \"ownerId\": \"kn754b8sk22s8c6gjxt02bftbn88q7ye\",\n  \"slug\": \"herzberg-two-factor\",\n  \"version\": \"1.0.4\",\n  \"publishedAt\": 1783595884447\n}\n\nFile v1.0.4:references/sources.md\n\n# Sources — herzberg-two-factor\n\n> *Primary sources for the [herzberg-two-factor](../SKILL.md) skill.*\n\n- **Herzberg, Frederick, Mausner, Bernard, & Snyderman, Barbara Bloch.** *The Motivation to Work.* Wiley, 1959. **Primary source** for the two-factor theory; presents the Pittsburgh study methodology and findings. Verbatim quote above from p. 113.\n- **Herzberg, Frederick.** \"One More Time: How Do You Motivate Employees?\" *Harvard Business Review*, Vol. 46, No. 1 (January–February 1968), pp. 53–62. The practitioner account; introduces KITA and job enrichment as the prescriptive response. Verbatim quote above from p. 59. One of HBR's most-requested reprints of all time (reported to have sold well over a million reprints by the late 1980s). https://hbr.org/2003/01/one-more-time-how-do-you-motivate-employees\n- **Hackman, J. Richard & Oldham, Greg R.** \"Motivation Through the Design of Work: Test of a Theory.\" *Organizational Behavior and Human Performance*, Vol. 16, No. 2 (August 1976), pp. 250–279. The empirical follow-on that operationalized job enrichment into the Job Characteristics Model (skill variety, task identity, task significance, autonomy, feedback). https://doi.org/10.1016/0030-5073(76)90016-7\n- **Deci, Edward L. & Ryan, Richard M.** \"The Empirical Exploration of Intrinsic Motivational Processes.\" In L. Berkowitz (ed.), *Advances in Experimental Social Psychology*, Vol. 13 (Academic Press, 1980), pp. 39–80. An early statement of the self-determination framework that provides the underlying mechanism for why Herzberg's motivators work — autonomy, competence, and relatedness as basic psychological needs. https://doi.org/10.1016/S0065-2601(08)60130-6\n- **Flanagan, John C.** \"The Critical Incident Technique.\" *Psychological Bulletin*, Vol. 51, No. 4 (July 1954), pp. 327–358. The methodological source for the data collection technique Herzberg used; establishes what critical incident data actually measures and its limitations. https://doi.org/10.1037/h0061470\n- **Ryan, Richard M. & Deci, Edward L.** *Self-Determination Theory: Basic Psychological Needs in Motivation, Development, and Wellness.* Guilford Press, 2017. The consolidated modern statement of SDT — autonomy, competence, and relatedness — which supplies the mechanism for why Herzberg's motivators (responsibility, achievement, growth) durably drive engagement while hygiene (pay, conditions) does not. Used to ground the 2024–2026 AI-talent example.\n- **Contemporary AI-talent market context (2024–2026):** Public business reporting through 2024–2025 broadly documented (a) record capital-expenditure commitments to AI infrastructure by major AI labs and hyperscalers, and (b) sharply elevated compensation and aggressive cross-lab recruiting for scarce frontier AI/ML researchers and engineers. These are widely-reported, durable market facts used as *setting* for the example; no single proprietary figure or specific dollar amount is asserted as evidence here. Confirm current specifics against primary reporting before quoting numbers.\n- **Not cited as evidence:** Generic management consulting surveys (\"% of employees are disengaged\") that do not distinguish hygiene and motivator dimensions are not cited here. They measure aggregate satisfaction without the two-factor decomposition, making them unsuitable for prescriptive use in this framework. Gallup Q12 scores, for example, conflate hygiene and motivator items. Use the framework to design data collection that separates the two dimensions.\n\nFile v1.0.4:examples/herzbergs-pittsburgh-study-and-the-critical-incident-method-1959.md\n\n# Method in Action: Herzberg's Pittsburgh Study and the Critical Incident Method (1959)\n\n> *Example for the [herzberg-two-factor](../SKILL.md) skill.*\n\nThe primary-source case is the original research itself — 203 accountants and engineers in Pittsburgh, 1844 incidents coded and analyzed. This is not a retrospective pop account; it is the founding empirical event.\n\n**Behavioral specification (Step 1):** Herzberg, Mausner, and Snyderman used the critical incident technique (developed by John Flanagan at the American Institutes for Research): ask people to describe a specific time at work when they felt exceptionally good or bad, what the circumstances were, what led to those feelings, and how long the feeling lasted. This produces behavioral data, not attitude ratings — it forces respondents to name actual events.\n\n**Classification (Step 2):** Across 1,844 coded incidents, the researchers found a systematic asymmetry. Factors cited when people felt *good* were predominantly: achievement (a project completed, a problem solved, a sale made), recognition (being told specifically that they had done something well), the work itself (finding the work engaging, varied, or demanding), responsibility (having real authority over outcomes), and advancement. Factors cited when people felt *bad* were predominantly: company policy and administration (arbitrary or bureaucratic rules), supervision (incompetent or unfair managers), working conditions, salary (not \"too little\" but the *process* — arbitrary raises, opaque criteria), and interpersonal relations.\n\n**Hygiene assessment (Step 3):** Salary appeared in the \"bad feelings\" data as a consistent factor — not the amount per se, but the *unfairness or opacity* of the salary process. When salary was perceived as fairly administered and at or above market, it did not appear as a satisfaction driver; it was simply absent from the \"good feelings\" accounts.\n\n**Motivator gap (Step 4):** The most powerful single predictor of extreme positive feelings was *achievement* — a concrete sense of having accomplished something. The second was *recognition* specifically tied to achievement. What was largely absent from either list: salary increases, benefits improvements, or office upgrades on the positive side; lack of achievement or recognition on the negative side.\n\n**Enrichment prescription (Step 5):** Herzberg's prescriptive conclusion — developed at length in the 1968 HBR article — was that companies systematically over-invested in KITA (Kick In The Ass, his term for hygiene interventions: raises, perks, threats) and under-invested in job enrichment. The practical prescription: increase the vertical complexity of jobs by giving people genuine ownership of outcomes, removing supervisory controls while maintaining accountability, providing direct feedback from the work, and creating visible advancement paths.\n\n**Legacy (Step 6):** The *Motivation to Work* has been cited over 1.4 million times according to Google Scholar. Herzberg's subsequent studies replicated the finding across 12 countries and multiple occupational groups, with consistent core results: the two-factor asymmetry holds across cultural contexts for knowledge workers, though the specific factor weights shift.\n\n**Sources:** Herzberg, Frederick, Mausner, Bernard, & Snyderman, Barbara Bloch. *The Motivation to Work.* Wiley, 1959. Herzberg, Frederick. \"One More Time: How Do You Motivate Employees?\" *Harvard Business Review*, Vol. 46, No. 1 (January–February 1968), pp. 53–62. https://hbr.org/2003/01/one-more-time-how-do-you-motivate-employees\n\nFile v1.0.4:examples/retaining-scarce-ai-ml-talent-2024-2026.md\n\n# Method in Action: Retaining Scarce AI/ML Talent in a Red-Hot Market (2024–2026)\n\n> *Example for the [herzberg-two-factor](../SKILL.md) skill.*\n\nBetween 2024 and 2026 the market for frontier AI/ML researchers and engineers became one of the most extreme talent markets in the history of the technology industry. Multiple large AI labs and hyperscalers publicly committed to unprecedented capital spending on AI infrastructure, and compensation for scarce senior AI talent reached widely reported levels far above typical software-engineering pay. Press reporting through late 2025 documented aggressive cross-lab poaching, headline-grabbing offers, and public statements from lab leaders about retention pressure. This is a textbook setting for the two-factor asymmetry: a market where *pay is table-stakes hygiene*, so throwing more money at retention often fails to move engagement — yet leaders keep reaching for it because it is the most legible lever.\n\nThe anchor case: a well-funded AI product company (Series B+, ~40 ML/research staff) sees its most valuable researchers being recruited away, and its instinct is to counter every offer with cash. This example runs that situation through the skill's Process.\n\n**Step 1 — Collect complaint/satisfaction inventory (specific behavioral events, not ratings).** Instead of an engagement survey, run stay interviews and code recent departures as critical incidents. Illustrative events the company surfaces: a departing researcher who left despite a matched counter-offer said the deciding factor was that a competitor let her own a research direction end-to-end rather than service a product roadmap; an engineer who stayed cited a specific week where he shipped a model improvement directly to production and saw the metric move; a complaint recurring in 1:1s is that model-launch decisions are made two layers up and researchers learn of them after the fact; another complaint is that GPU allocation and experiment approval require slow, opaque sign-off. These are events, not opinions.\n\n**Step 2 — Classify each item as hygiene or motivator.** Cash compensation and equity: hygiene (in this market, absence below the top-lab band drives active dissatisfaction, but matching it produces no durable engagement — the classic \"we matched the offer and they left anyway\"). Compute access being throttled by slow approval: hygiene (a *working-conditions* failure — the tooling of the job). Owning a research direction end-to-end: motivator (responsibility + the work itself). Shipping to production and seeing the metric move: motivator (achievement + direct feedback from the work). Being excluded from launch decisions: a motivator gap (responsibility withheld). The classification test from the skill applies: matched pay habituates within weeks; direction-ownership does not.\n\n**Step 3 — Assess hygiene baseline vs. market and set the floor.** In the 2024–2026 market the hygiene floor for scarce AI talent moved sharply upward, so the floor must be re-benchmarked against *frontier-lab* bands, not generic software bands. Prioritize per the skill: salary/equity to a credible top-tier-competitive band → job security (fundraising runway clarity so people aren't gambling on the company surviving the capex arms race) → working conditions (here, *compute and tooling latency* is the dominant condition — abundant GPU access and fast experiment turnaround). Stop-rule check: if pay is below the frontier band, fix that *first* — mission rhetoric does not retain a researcher fielding a doubled offer. But once at the floor, additional cash buys little retention; that is the asymmetry.\n\n**Step 4 — Diagnose motivator gaps across the five motivators.** Achievement: weak — researchers rarely see their work reach users; results die in internal decks. Recognition: weak — no specific, prompt acknowledgment tied to a shipped result; recognition is annual and generic. Work itself: mixed — genuinely frontier problems exist, but they are fragmented into roadmap-service tasks. Responsibility: absent — direction and launch calls sit two layers up. Growth: unclear — no visible path from IC researcher to owning a research agenda. The primary motivator gap here is **responsibility (real ownership of a research direction)**, closely followed by **achievement made visible (work reaching production and being recognized promptly)**.\n\n**Step 5 — Design job enrichment (vertical loading).** Give named researchers genuine ownership of a research direction with real decision authority over approach — not more assignments (that would be horizontal loading). Remove the procedural control on compute: replace slow sign-off with a standing per-researcher compute budget they spend at their own discretion, while keeping accountability for results. Give direct feedback from the work: instrument a path so a researcher's model change ships to real users and they see the metric, closing the achievement loop. Add direct user/customer contact for researchers whose work touches the product. Make recognition specific and proximate — acknowledge a named shipped result the week it lands, not at the annual review. Create a visible growth ladder from IC to research-lead that is about scope of ownership, not headcount managed.\n\n**Step 6 — Monitor and iterate on two cadences.** Track hygiene on a slower cadence (re-benchmark comp against frontier bands roughly semi-annually as the market moves) but expect its retention effect to habituate within weeks. Track motivators as the *lead indicator*: quarterly stay interviews coded for whether researchers report ownership, shipped-and-recognized achievement, and a visible path. The trap to watch, straight from the skill's rationalizations: a wave of cash counter-offers will show a short-term retention bump; follow the same cohort 6–12 months out — if the ownership and achievement gaps weren't closed, discretionary effort and attrition revert to baseline, and you will have paid frontier-band premiums for hygiene restoration with no motivation gained.\n\n**Takeaway.** In the 2024–2026 AI talent market, competitive compensation is a *necessary* hygiene floor — set it against frontier-lab bands or you lose people outright. But it is not what makes scarce researchers stay and do their best work. The durable retention lever is motivator design: frontier problems owned end-to-end, autonomy over compute and approach, and achievement that reaches users and is recognized promptly.\n\n*Sources: Herzberg, Frederick, Mausner, Bernard, & Snyderman, Barbara Bloch. *The Motivation to Work.* Wiley, 1959. Herzberg, Frederick, \"One More Time: How Do You Motivate Employees?\" *Harvard Business Review* 46, no. 1 (Jan–Feb 1968): 53–62, https://hbr.org/2003/01/one-more-time-how-do-you-motivate-employees. Deci, Edward L. & Ryan, Richard M., \"The Empirical Exploration of Intrinsic Motivational Processes,\" in L. Berkowitz (ed.), *Advances in Experimental Social Psychology*, Vol. 13 (Academic Press, 1980): 39–80 (mechanism for why autonomy/mastery motivate); further developed in Ryan & Deci, *Self-Determination Theory*, Guilford Press, 2017. Contemporary market context (record AI infrastructure capex commitments by major labs/hyperscalers, and widely reported elevated compensation and cross-lab recruiting for scarce AI/ML talent through 2024–2025) is drawn from broad, well-documented public business reporting rather than any single proprietary figure; specific dollar amounts are deliberately not asserted here.*\n\nFile v1.0.4:skill-card.md\n\n## Description: <br>\nHelps agents diagnose workplace motivation, engagement, and retention problems by separating hygiene gaps from motivator gaps and producing a two-factor diagnosis. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[deciqai](https://clawhub.ai/user/deciqai) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nManagers, founders, and people leaders use this skill to analyze low motivation, retention pressure, compensation resets, and role-design problems. It guides the agent to classify work issues as hygiene factors or motivators, identify stop conditions, and propose job-enrichment interventions. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: The skill may activate during broad conversations about motivation, engagement, or retention where a Herzberg analysis is not intended. <br>\nMitigation: Review trigger wording before deployment and narrow activation rules if broad management conversations should not invoke the skill. <br>\nRisk: The skill provides advisory management-framework guidance that could be misleading if applied before basic hygiene gaps such as unsafe conditions or below-market pay are addressed. <br>\nMitigation: Require users to check the documented stop rule and resolve clear hygiene gaps before applying motivator or job-enrichment recommendations. <br>\n\n\n## Reference(s): <br>\n- [ClawHub Skill Page](https://clawhub.ai/deciqai/skills/herzberg-two-factor) <br>\n- [Primary Sources](references/sources.md) <br>\n- [Herzberg's Pittsburgh Study and the Critical Incident Method (1959)](examples/herzbergs-pittsburgh-study-and-the-critical-incident-method-1959.md) <br>\n- [Retaining Scarce AI/ML Talent in a Red-Hot Market (2024-2026)](examples/retaining-scarce-ai-ml-talent-2024-2026.md) <br>\n- [One More Time: How Do You Motivate Employees?](https://hbr.org/2003/01/one-more-time-how-do-you-motivate-employees) <br>\n- [Motivation Through the Design of Work](https://doi.org/10.1016/0030-5073(76)90016-7) <br>\n- [The Empirical Exploration of Intrinsic Motivational Processes](https://doi.org/10.1016/S0065-2601(08)60130-6) <br>\n- [The Critical Incident Technique](https://doi.org/10.1037/h0061470) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [text, markdown, guidance] <br>\n**Output Format:** [Markdown diagnosis with tables, questions, and recommended interventions] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [May pause for user input in coach mode before completing the diagnosis.] <br>\n\n## Skill Version(s): <br>\n1.0.4 (source: server release metadata) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>\n\nArchive v1.0.3: 5 files, 9698 bytes\n\nFiles: examples/herzbergs-pittsburgh-study-and-the-critical-incident-method-1959.md (3610b), references/sources.md (2348b), skill-card.md (2747b), SKILL.md (9818b), _meta.json (138b)\n\nFile v1.0.3:SKILL.md\n\n---\nname: herzberg-two-factor\ndescription: \"Activate when: someone says 'why isn't the team motivated,' 'we raised salaries but morale didn't improve,' 'people keep leaving for better opportunities,' 'employee engagement is low,' 'how do I retain engineers,' or when designing compensation, job roles, or performance systems.\n  Do NOT activate when: the problem is a skill gap (people lack capability, not motivation); or the worker is in extreme economic precarity where basic survival income is the issue.\"\n---\n\n# Herzberg Two-Factor Theory\n\n## Overview\n\nHerzberg's 1959 Pittsburgh study found satisfaction and dissatisfaction are **two independent axes**. **Hygiene factors** (salary, working conditions, job security) only remove dissatisfaction — never create motivation. **Motivators** (achievement, recognition, responsibility, growth, the work itself) create genuine engagement. More hygiene spending never produces motivation; only **job enrichment** — redesigning work for higher responsibility and autonomy — does.\n\n**Composition with neighbors:** Use principal-agent when incentive structures keep failing (designers mistake hygiene for motivators). Use nudge-theory after Herzberg to design low-friction paths to the motivating actions identified.\n\n## When to Use\n\n- Team shows **adequate performance but low energy** — people meet the minimum but go no further\n- Talent **leaving for \"better opportunities\"** and exit interviews are uninformative\n- **Compensation recently increased** but morale didn't improve, or reset within months\n- **Designing** compensation structure, job role, or performance review system\n- Someone says: *\"motivation,\" \"engagement,\" \"retention,\" \"why isn't the team energized\"*\n\n**When NOT to use:** Clear hygiene gap exists (salary below market, unsafe conditions) — fix those first. Skill gap, not motivation gap. Very short time horizon (72-hour sprint).\n\n## Coaching Novices (Adaptive Front Door)\n\n- **Engine mode:** specific team/role described → run The Process directly.\n- **Coach mode:** unfamiliar or no concrete case → guide step by step.\n\nIn Coach mode, respond one step at a time. Each [WAIT] is a hard stop — output only that step's question, then stop.\n\n1. One-line what-it-is: salary/benefits can only *remove unhappiness* — only challenging work, real responsibility, and recognition for achievement create genuine motivation.\n2. Check fit against When to Use / When NOT to use. If clear hygiene gap exists, redirect to fixing hygiene first.\n3. Elicit their real case — \"people aren't motivated\" is not a case; get the specific behavioral signal.\n> **[WAIT — do not advance until user responds]**\n4. Classify each complaint/satisfaction item as hygiene or motivator one at a time before prescribing.\n> **[WAIT — do not advance until user responds]**\n5. Close: \"The reason raising salary didn't fix this is ___. The one motivator intervention most likely to move engagement here is ___.\"\n> **[WAIT — do not advance until user responds]**\n\n## The Process\n\nRun the **Two-Factor Diagnosis**. **Stop-rule:** if Step 2 reveals clear hygiene gaps (pay below market, unsafe environment), stop and address those before any motivator work.\n\n1. **Collect complaint/satisfaction inventory** via exit interviews, stay interviews, 1:1s, or surveys — specific behavioral events, not abstract ratings.\n2. **Classify each item:** Hygiene (context of work: salary, benefits, security, working conditions, policy, supervision, peer relationships) vs. Motivator (content of work: achievement, recognition for achievement, work itself, responsibility/autonomy, growth/advancement). Classification test: if removing it causes active unhappiness but adding more habituates quickly → hygiene.\n3. **Assess hygiene baseline** vs. market standard. Set a \"hygiene floor\" — the threshold where it no longer drives active dissatisfaction. Prioritize: salary → job security → working conditions → interpersonal environment.\n4. **Diagnose motivator gaps** across five core motivators: Achievement (challenging, completable goals?), Recognition (specific, prompt, tied to achievement?), Work itself (varied, challenging?), Responsibility (real ownership?), Growth (visible path forward?).\n5. **Design job enrichment (vertical loading):** remove procedural controls while keeping accountability; give direct feedback from the work; assign whole units of work; add direct client/user contact; increase technical scope. Not horizontal loading (more same-type tasks).\n6. **Monitor and iterate** quarterly — hygiene satisfaction habituates in weeks; motivator satisfaction is durable but evolves as people grow.\n\n### Output: Two-Factor Diagnosis\n\n```\n# Two-Factor Diagnosis: <team / role>\nHygiene floor status: <below / at / above floor> | Required fixes: <>\n| Hygiene Factor | Current | Market std | Gap | Priority |\n| Motivator | Signal (strong/weak/absent) | Evidence |\nPrimary motivator gap: <>\n| Enrichment Intervention | Motivator targeted | What changes | Owner |\nMonitoring: hygiene cadence <> | motivator cadence <> | lead indicator <>\n```\n\n*→ Method in Action: [Herzberg's Pittsburgh Study and the Critical Incident Method (1959)](examples/herzbergs-pittsburgh-study-and-the-critical-incident-method-1959.md)*\n\n## Motivation Packs\n\n- **Software engineering:** hygiene failures = opaque promotion, inconsistent code review. Motivators: full-feature ownership, tech decision authority, open-source/conference recognition.\n- **Early-stage startups:** fix hygiene (salary at living-cost threshold, equity clarity) before mission rhetoric — narrative doesn't motivate someone who can't pay rent.\n- **Sales:** commission is hygiene when expected at market; becomes motivator only tied to specific achievement. Recognize wins publicly; give territory/account ownership.\n- **Product management:** dominant gap = work fragmentation (PMs as request-gatherers). Enrichment: direct user access, full problem-space ownership, visible path to measurable outcomes.\n\n## Applying It Well\n\n- Fix hygiene to the floor, not best-in-class — above-market hygiene costs more with zero retention advantage.\n- Salary raises decay in weeks; design for motivators, not raises.\n- Recognition must be specific, proximate, and tied to a named achievement — not generic and annual.\n- Vertical loading only: more authority, accountability, direct feedback, complete ownership — not more tasks of the same type.\n- Motivators habituate upward; job enrichment is continuous design, not a one-time fix.\n\n*→ Primary sources: [references/sources.md](references/sources.md)*\n\n## Common Rationalizations\n\n**[D] = designed upfront | [O] = observed in real use. [O] entries are more valuable.**\n\n| Fake move | Reality |\n|---|---|\n| [D] **\"We gave everyone a 15% raise and retention improved, so salary is a motivator.\"** | Short-term retention = hygiene restoration. Track the same cohort 6–12 months: discretionary effort returns to pre-raise baseline. |\n| [D] **\"Our employees say they care most about compensation in surveys.\"** | Surveys skew toward hygiene factors (legible, discussable). Critical incident data consistently surfaces achievement and recognition as primary. |\n| [D] **\"We added flexible hours and a gym benefit — that should help motivation.\"** | Both are hygiene factors. Neither creates engagement when work is unchallenging and responsibility is absent. |\n| [D] **\"If we give people more autonomy, they'll make mistakes.\"** | Studies show increased autonomy improves both performance and retention when paired with clear accountability structures. |\n| [D] **\"We recognize people with annual awards.\"** | Annual generic awards sever the motivational connection. Recognition must be specific, proximate, and tied to a named achievement. |\n| [D] **\"Our engineers leave for Google salaries — this is a hygiene problem.\"** | When they leave for similar-level roles at similar salaries, it's almost always a motivator failure wearing hygiene language in the exit interview. |\n| [D] **\"We enriched jobs by adding more projects.\"** | Horizontal loading. Enrichment = vertical loading: higher-scope responsibility, direct accountability, genuine decision authority. |\n| *→ Add [O] entries here after each real use — paste the actual failure pattern* | *What went wrong and why* |\n\n## Red Flags\n\n- Retention interventions default to compensation without a two-factor diagnosis\n- Exit interview data not classified by hygiene vs. motivator before designing intervention\n- Recognition is non-specific, annual, disconnected from observed achievement\n- Job enrichment operationalized as more work (horizontal) rather than more responsibility (vertical)\n- \"Culture\" used as substitute for diagnosing whether motivators are present in the actual role\n\n## Verification\n\n- [ ] Problem classified: hygiene-domain (dissatisfaction) vs. motivator-domain (low engagement despite adequate hygiene)\n- [ ] Hygiene baseline assessed against market standards before any motivator intervention\n- [ ] Motivator gaps identified through behavioral data, not attitude ratings\n- [ ] Interventions are vertical loading (responsibility, autonomy, scope) not horizontal loading\n- [ ] Recognition is specific and proximate (close in time to the achievement)\n- [ ] Monitoring plan defined with cadence for both axes\n- [ ] Two-factor asymmetry stated explicitly: fixing hygiene will not create motivation\n\n---\n\n*Part of **deciqAI Knowledge Skills** — 164 open-source thinking skills that make rigor executable for AI agents. The same skills power every deciqAI agent, which runs them autonomously to operate your company. **See it run → https://www.deciqai.com/c/herzberg-two-factor** · ⭐ Star the repo → https://github.com/deciqAI/knowledge-skills · Contributions welcome.*\n\nFile v1.0.3:_meta.json\n\n{\n  \"ownerId\": \"kn754b8sk22s8c6gjxt02bftbn88q7ye\",\n  \"slug\": \"herzberg-two-factor\",\n  \"version\": \"1.0.3\",\n  \"publishedAt\": 1783508686158\n}\n\nFile v1.0.3:references/sources.md\n\n# Sources — herzberg-two-factor\n\n> *Primary sources for the [herzberg-two-factor](../SKILL.md) skill.*\n\n- **Herzberg, Frederick, Mausner, Bernard, & Snyderman, Barbara Bloch.** *The Motivation to Work.* Wiley, 1959. **Primary source** for the two-factor theory; presents the Pittsburgh study methodology and findings. Verbatim quote above from p. 113.\n- **Herzberg, Frederick.** \"One More Time: How Do You Motivate Employees?\" *Harvard Business Review*, Vol. 46, No. 1 (January–February 1968), pp. 53–62. The practitioner account; introduces KITA and job enrichment as the prescriptive response. Verbatim quote above from p. 59. Cited approximately 1.4 million times per Google Scholar. https://hbr.org/2003/01/one-more-time-how-do-you-motivate-employees\n- **Hackman, J. Richard & Oldham, Greg R.** \"Motivation Through the Design of Work: Test of a Theory.\" *Organizational Behavior and Human Performance*, Vol. 16, No. 2 (August 1976), pp. 250–279. The empirical follow-on that operationalized job enrichment into the Job Characteristics Model (skill variety, task identity, task significance, autonomy, feedback). https://doi.org/10.1016/0030-5073(76)90016-7\n- **Deci, Edward L. & Ryan, Richard M.** \"Self-Determination and Intrinsic Motivation in Human Behavior.\" *Psychological Review*, Vol. 87, No. 1 (January 1980), pp. 1–41. The self-determination theory framework that provides the underlying mechanism for why Herzberg's motivators work — autonomy, competence, and relatedness as basic psychological needs. https://doi.org/10.1037/0033-295X.87.1.1\n- **Flanagan, John C.** \"The Critical Incident Technique.\" *Psychological Bulletin*, Vol. 51, No. 4 (July 1954), pp. 327–358. The methodological source for the data collection technique Herzberg used; establishes what critical incident data actually measures and its limitations. https://doi.org/10.1037/h0061470\n- **Not cited as evidence:** Generic management consulting surveys (\"% of employees are disengaged\") that do not distinguish hygiene and motivator dimensions are not cited here. They measure aggregate satisfaction without the two-factor decomposition, making them unsuitable for prescriptive use in this framework. Gallup Q12 scores, for example, conflate hygiene and motivator items. Use the framework to design data collection that separates the two dimensions.\n\nFile v1.0.3:examples/herzbergs-pittsburgh-study-and-the-critical-incident-method-1959.md\n\n# Method in Action: Herzberg's Pittsburgh Study and the Critical Incident Method (1959)\n\n> *Example for the [herzberg-two-factor](../SKILL.md) skill.*\n\nThe primary-source case is the original research itself — 203 accountants and engineers in Pittsburgh, 1844 incidents coded and analyzed. This is not a retrospective pop account; it is the founding empirical event.\n\n**Behavioral specification (Step 1):** Herzberg, Mausner, and Snyderman used the critical incident technique (developed by John Flanagan at the American Institutes for Research): ask people to describe a specific time at work when they felt exceptionally good or bad, what the circumstances were, what led to those feelings, and how long the feeling lasted. This produces behavioral data, not attitude ratings — it forces respondents to name actual events.\n\n**Classification (Step 2):** Across 1,844 coded incidents, the researchers found a systematic asymmetry. Factors cited when people felt *good* were predominantly: achievement (a project completed, a problem solved, a sale made), recognition (being told specifically that they had done something well), the work itself (finding the work engaging, varied, or demanding), responsibility (having real authority over outcomes), and advancement. Factors cited when people felt *bad* were predominantly: company policy and administration (arbitrary or bureaucratic rules), supervision (incompetent or unfair managers), working conditions, salary (not \"too little\" but the *process* — arbitrary raises, opaque criteria), and interpersonal relations.\n\n**Hygiene assessment (Step 3):** Salary appeared in the \"bad feelings\" data as a consistent factor — not the amount per se, but the *unfairness or opacity* of the salary process. When salary was perceived as fairly administered and at or above market, it did not appear as a satisfaction driver; it was simply absent from the \"good feelings\" accounts.\n\n**Motivator gap (Step 4):** The most powerful single predictor of extreme positive feelings was *achievement* — a concrete sense of having accomplished something. The second was *recognition* specifically tied to achievement. What was largely absent from either list: salary increases, benefits improvements, or office upgrades on the positive side; lack of achievement or recognition on the negative side.\n\n**Enrichment prescription (Step 5):** Herzberg's prescriptive conclusion — developed at length in the 1968 HBR article — was that companies systematically over-invested in KITA (Kick In The Ass, his term for hygiene interventions: raises, perks, threats) and under-invested in job enrichment. The practical prescription: increase the vertical complexity of jobs by giving people genuine ownership of outcomes, removing supervisory controls while maintaining accountability, providing direct feedback from the work, and creating visible advancement paths.\n\n**Legacy (Step 6):** The *Motivation to Work* has been cited over 1.4 million times according to Google Scholar. Herzberg's subsequent studies replicated the finding across 12 countries and multiple occupational groups, with consistent core results: the two-factor asymmetry holds across cultural contexts for knowledge workers, though the specific factor weights shift.\n\n**Sources:** Herzberg, Frederick, Mausner, Bernard, & Snyderman, Barbara Bloch. *The Motivation to Work.* Wiley, 1959. Herzberg, Frederick. \"One More Time: How Do You Motivate Employees?\" *Harvard Business Review*, Vol. 46, No. 1 (January–February 1968), pp. 53–62. https://hbr.org/2003/01/one-more-time-how-do-you-motivate-employees\n\nFile v1.0.3:skill-card.md\n\n## Description: <br>\nGuides agents through Herzberg's two-factor diagnosis to separate hygiene problems from motivator gaps and design job-enrichment interventions for engagement and retention. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[deciqai](https://clawhub.ai/user/deciqai) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nEmployees, managers, HR partners, and organizational design advisors use this skill to diagnose motivation, engagement, and retention issues. It helps distinguish hygiene factors from true motivators and produces a structured two-factor diagnosis with job-enrichment actions. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: The framework may be overused in broad HR conversations where motivation is not the primary issue. <br>\nMitigation: Apply the skill only when the conversation includes concrete motivation, engagement, retention, compensation, role design, or performance-system context. <br>\nRisk: Example diagnosis tables could capture confidential personnel details if adapted directly to real employees. <br>\nMitigation: Avoid recording sensitive employee details; keep cases aggregated or anonymized when using the diagnostic tables. <br>\n\n\n## Reference(s): <br>\n- [ClawHub skill page](https://clawhub.ai/deciqai/skills/herzberg-two-factor) <br>\n- [Sources - herzberg-two-factor](references/sources.md) <br>\n- [Herzberg's Pittsburgh Study and the Critical Incident Method (1959)](examples/herzbergs-pittsburgh-study-and-the-critical-incident-method-1959.md) <br>\n- [One More Time: How Do You Motivate Employees?](https://hbr.org/2003/01/one-more-time-how-do-you-motivate-employees) <br>\n- [Motivation Through the Design of Work](https://doi.org/10.1016/0030-5073(76)90016-7) <br>\n- [Self-Determination and Intrinsic Motivation in Human Behavior](https://doi.org/10.1037/0033-295X.87.1.1) <br>\n- [The Critical Incident Technique](https://doi.org/10.1037/h0061470) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [guidance, markdown, text] <br>\n**Output Format:** [Markdown with structured tables, checklists, and stepwise coaching prompts] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [Coach mode uses explicit wait points before advancing; normal mode produces a two-factor diagnosis for a team or role.] <br>\n\n## Skill Version(s): <br>\n1.0.3 (source: server release evidence) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>\n\nArchive v1.0.2: 5 files, 9823 bytes\n\nFiles: examples/herzbergs-pittsburgh-study-and-the-critical-incident-method-1959.md (3610b), references/sources.md (2348b), skill-card.md (2951b), SKILL.md (9927b), _meta.json (138b)\n\nFile v1.0.2:SKILL.md\n\n---\nname: herzberg-two-factor\ndescription: \"Activate when: someone says 'why isn't the team motivated,' 'we raised salaries but morale didn't improve,' 'people keep leaving for better opportunities,' 'employee engagement is low,' 'how do I retain engineers,' or when designing compensation, job roles, or performance systems.\n  Do NOT activate when: the problem is a skill gap (people lack capability, not motivation); or the worker is in extreme economic precarity where basic survival income is the issue.\"\n---\n\n# Herzberg Two-Factor Theory\n\n## Overview\n\nHerzberg's 1959 Pittsburgh study found satisfaction and dissatisfaction are **two independent axes**. **Hygiene factors** (salary, working conditions, job security) only remove dissatisfaction — never create motivation. **Motivators** (achievement, recognition, responsibility, growth, the work itself) create genuine engagement. More hygiene spending never produces motivation; only **job enrichment** — redesigning work for higher responsibility and autonomy — does.\n\n**Composition with neighbors:** Use principal-agent when incentive structures keep failing (designers mistake hygiene for motivators). Use nudge-theory after Herzberg to design low-friction paths to the motivating actions identified.\n\n## When to Use\n\n- Team shows **adequate performance but low energy** — people meet the minimum but go no further\n- Talent **leaving for \"better opportunities\"** and exit interviews are uninformative\n- **Compensation recently increased** but morale didn't improve, or reset within months\n- **Designing** compensation structure, job role, or performance review system\n- Someone says: *\"motivation,\" \"engagement,\" \"retention,\" \"why isn't the team energized\"*\n\n**When NOT to use:** Clear hygiene gap exists (salary below market, unsafe conditions) — fix those first. Skill gap, not motivation gap. Very short time horizon (72-hour sprint).\n\n## Coaching Novices (Adaptive Front Door)\n\n- **Engine mode:** specific team/role described → run The Process directly.\n- **Coach mode:** unfamiliar or no concrete case → guide step by step.\n\nIn Coach mode, respond one step at a time. Each [WAIT] is a hard stop — output only that step's question, then stop.\n\n1. One-line what-it-is: salary/benefits can only *remove unhappiness* — only challenging work, real responsibility, and recognition for achievement create genuine motivation.\n2. Check fit against When to Use / When NOT to use. If clear hygiene gap exists, redirect to fixing hygiene first.\n3. Elicit their real case — \"people aren't motivated\" is not a case; get the specific behavioral signal.\n> **[WAIT — do not advance until user responds]**\n4. Classify each complaint/satisfaction item as hygiene or motivator one at a time before prescribing.\n> **[WAIT — do not advance until user responds]**\n5. Close: \"The reason raising salary didn't fix this is ___. The one motivator intervention most likely to move engagement here is ___.\"\n> **[WAIT — do not advance until user responds]**\n\n## The Process\n\nRun the **Two-Factor Diagnosis**. **Stop-rule:** if Step 2 reveals clear hygiene gaps (pay below market, unsafe environment), stop and address those before any motivator work.\n\n1. **Collect complaint/satisfaction inventory** via exit interviews, stay interviews, 1:1s, or surveys — specific behavioral events, not abstract ratings.\n2. **Classify each item:** Hygiene (context of work: salary, benefits, security, working conditions, policy, supervision, peer relationships) vs. Motivator (content of work: achievement, recognition for achievement, work itself, responsibility/autonomy, growth/advancement). Classification test: if removing it causes active unhappiness but adding more habituates quickly → hygiene.\n3. **Assess hygiene baseline** vs. market standard. Set a \"hygiene floor\" — the threshold where it no longer drives active dissatisfaction. Prioritize: salary → job security → working conditions → interpersonal environment.\n4. **Diagnose motivator gaps** across five core motivators: Achievement (challenging, completable goals?), Recognition (specific, prompt, tied to achievement?), Work itself (varied, challenging?), Responsibility (real ownership?), Growth (visible path forward?).\n5. **Design job enrichment (vertical loading):** remove procedural controls while keeping accountability; give direct feedback from the work; assign whole units of work; add direct client/user contact; increase technical scope. Not horizontal loading (more same-type tasks).\n6. **Monitor and iterate** quarterly — hygiene satisfaction habituates in weeks; motivator satisfaction is durable but evolves as people grow.\n\n### Output: Two-Factor Diagnosis\n\n```\n# Two-Factor Diagnosis: <team / role>\nHygiene floor status: <below / at / above floor> | Required fixes: <>\n| Hygiene Factor | Current | Market std | Gap | Priority |\n| Motivator | Signal (strong/weak/absent) | Evidence |\nPrimary motivator gap: <>\n| Enrichment Intervention | Motivator targeted | What changes | Owner |\nMonitoring: hygiene cadence <> | motivator cadence <> | lead indicator <>\n```\n\n*→ Method in Action: [Herzberg's Pittsburgh Study and the Critical Incident Method (1959)](examples/herzbergs-pittsburgh-study-and-the-critical-incident-method-1959.md)*\n\n## Motivation Packs\n\n- **Software engineering:** hygiene failures = opaque promotion, inconsistent code review. Motivators: full-feature ownership, tech decision authority, open-source/conference recognition.\n- **Early-stage startups:** fix hygiene (salary at living-cost threshold, equity clarity) before mission rhetoric — narrative doesn't motivate someone who can't pay rent.\n- **Sales:** commission is hygiene when expected at market; becomes motivator only tied to specific achievement. Recognize wins publicly; give territory/account ownership.\n- **Product management:** dominant gap = work fragmentation (PMs as request-gatherers). Enrichment: direct user access, full problem-space ownership, visible path to measurable outcomes.\n\n## Applying It Well\n\n- Fix hygiene to the floor, not best-in-class — above-market hygiene costs more with zero retention advantage.\n- Salary raises decay in weeks; design for motivators, not raises.\n- Recognition must be specific, proximate, and tied to a named achievement — not generic and annual.\n- Vertical loading only: more authority, accountability, direct feedback, complete ownership — not more tasks of the same type.\n- Motivators habituate upward; job enrichment is continuous design, not a one-time fix.\n\n*→ Primary sources: [references/sources.md](references/sources.md)*\n\n## Common Rationalizations\n\n**[D] = designed upfront | [O] = observed in real use. [O] entries are more valuable.**\n\n| Fake move | Reality |\n|---|---|\n| [D] **\"We gave everyone a 15% raise and retention improved, so salary is a motivator.\"** | Short-term retention = hygiene restoration. Track the same cohort 6–12 months: discretionary effort returns to pre-raise baseline. |\n| [D] **\"Our employees say they care most about compensation in surveys.\"** | Surveys skew toward hygiene factors (legible, discussable). Critical incident data consistently surfaces achievement and recognition as primary. |\n| [D] **\"We added flexible hours and a gym benefit — that should help motivation.\"** | Both are hygiene factors. Neither creates engagement when work is unchallenging and responsibility is absent. |\n| [D] **\"If we give people more autonomy, they'll make mistakes.\"** | Studies show increased autonomy improves both performance and retention when paired with clear accountability structures. |\n| [D] **\"We recognize people with annual awards.\"** | Annual generic awards sever the motivational connection. Recognition must be specific, proximate, and tied to a named achievement. |\n| [D] **\"Our engineers leave for Google salaries — this is a hygiene problem.\"** | When they leave for similar-level roles at similar salaries, it's almost always a motivator failure wearing hygiene language in the exit interview. |\n| [D] **\"We enriched jobs by adding more projects.\"** | Horizontal loading. Enrichment = vertical loading: higher-scope responsibility, direct accountability, genuine decision authority. |\n| *→ Add [O] entries here after each real use — paste the actual failure pattern* | *What went wrong and why* |\n\n## Red Flags\n\n- Retention interventions default to compensation without a two-factor diagnosis\n- Exit interview data not classified by hygiene vs. motivator before designing intervention\n- Recognition is non-specific, annual, disconnected from observed achievement\n- Job enrichment operationalized as more work (horizontal) rather than more responsibility (vertical)\n- \"Culture\" used as substitute for diagnosing whether motivators are present in the actual role\n\n## Verification\n\n- [ ] Problem classified: hygiene-domain (dissatisfaction) vs. motivator-domain (low engagement despite adequate hygiene)\n- [ ] Hygiene baseline assessed against market standards before any motivator intervention\n- [ ] Motivator gaps identified through behavioral data, not attitude ratings\n- [ ] Interventions are vertical loading (responsibility, autonomy, scope) not horizontal loading\n- [ ] Recognition is specific and proximate (close in time to the achievement)\n- [ ] Monitoring plan defined with cadence for both axes\n- [ ] Two-factor asymmetry stated explicitly: fixing hygiene will not create motivation\n\n---\n\n*Part of **deciqAI Knowledge Skills** — 163 open-source thinking skills that make rigor executable for AI agents. The same skills power every deciqAI agent, which runs them autonomously to operate your company. **See it run → https://www.deciqai.com/skills/herzberg-two-factor?utm_source=clawhub&utm_medium=marketplace&utm_campaign=knowledge-skills&utm_content=herzberg-two-factor** · ⭐ Star the repo → https://github.com/deciqAI/knowledge-skills · Contributions welcome.*\n\nFile v1.0.2:_meta.json\n\n{\n  \"ownerId\": \"kn754b8sk22s8c6gjxt02bftbn88q7ye\",\n  \"slug\": \"herzberg-two-factor\",\n  \"version\": \"1.0.2\",\n  \"publishedAt\": 1783471790970\n}\n\nFile v1.0.2:references/sources.md\n\n# Sources — herzberg-two-factor\n\n> *Primary sources for the [herzberg-two-factor](../SKILL.md) skill.*\n\n- **Herzberg, Frederick, Mausner, Bernard, & Snyderman, Barbara Bloch.** *The Motivation to Work.* Wiley, 1959. **Primary source** for the two-factor theory; presents the Pittsburgh study methodology and findings. Verbatim quote above from p. 113.\n- **Herzberg, Frederick.** \"One More Time: How Do You Motivate Employees?\" *Harvard Business Review*, Vol. 46, No. 1 (January–February 1968), pp. 53–62. The practitioner account; introduces KITA and job enrichment as the prescriptive response. Verbatim quote above from p. 59. Cited approximately 1.4 million times per Google Scholar. https://hbr.org/2003/01/one-more-time-how-do-you-motivate-employees\n- **Hackman, J. Richard & Oldham, Greg R.** \"Motivation Through the Design of Work: Test of a Theory.\" *Organizational Behavior and Human Performance*, Vol. 16, No. 2 (August 1976), pp. 250–279. The empirical follow-on that operationalized job enrichment into the Job Characteristics Model (skill variety, task identity, task significance, autonomy, feedback). https://doi.org/10.1016/0030-5073(76)90016-7\n- **Deci, Edward L. & Ryan, Richard M.** \"Self-Determination and Intrinsic Motivation in Human Behavior.\" *Psychological Review*, Vol. 87, No. 1 (January 1980), pp. 1–41. The self-determination theory framework that provides the underlying mechanism for why Herzberg's motivators work — autonomy, competence, and relatedness as basic psychological needs. https://doi.org/10.1037/0033-295X.87.1.1\n- **Flanagan, John C.** \"The Critical Incident Technique.\" *Psychological Bulletin*, Vol. 51, No. 4 (July 1954), pp. 327–358. The methodological source for the data collection technique Herzberg used; establishes what critical incident data actually measures and its limitations. https://doi.org/10.1037/h0061470\n- **Not cited as evidence:** Generic management consulting surveys (\"% of employees are disengaged\") that do not distinguish hygiene and motivator dimensions are not cited here. They measure aggregate satisfaction without the two-factor decomposition, making them unsuitable for prescriptive use in this framework. Gallup Q12 scores, for example, conflate hygiene and motivator items. Use the framework to design data collection that separates the two dimensions.\n\nFile v1.0.2:examples/herzbergs-pittsburgh-study-and-the-critical-incident-method-1959.md\n\n# Method in Action: Herzberg's Pittsburgh Study and the Critical Incident Method (1959)\n\n> *Example for the [herzberg-two-factor](../SKILL.md) skill.*\n\nThe primary-source case is the original research itself — 203 accountants and engineers in Pittsburgh, 1844 incidents coded and analyzed. This is not a retrospective pop account; it is the founding empirical event.\n\n**Behavioral specification (Step 1):** Herzberg, Mausner, and Snyderman used the critical incident technique (developed by John Flanagan at the American Institutes for Research): ask people to describe a specific time at work when they felt exceptionally good or bad, what the circumstances were, what led to those feelings, and how long the feeling lasted. This produces behavioral data, not attitude ratings — it forces respondents to name actual events.\n\n**Classification (Step 2):** Across 1,844 coded incidents, the researchers found a systematic asymmetry. Factors cited when people felt *good* were predominantly: achievement (a project completed, a problem solved, a sale made), recognition (being told specifically that they had done something well), the work itself (finding the work engaging, varied, or demanding), responsibility (having real authority over outcomes), and advancement. Factors cited when people felt *bad* were predominantly: company policy and administration (arbitrary or bureaucratic rules), supervision (incompetent or unfair managers), working conditions, salary (not \"too little\" but the *process* — arbitrary raises, opaque criteria), and interpersonal relations.\n\n**Hygiene assessment (Step 3):** Salary appeared in the \"bad feelings\" data as a consistent factor — not the amount per se, but the *unfairness or opacity* of the salary process. When salary was perceived as fairly administered and at or above market, it did not appear as a satisfaction driver; it was simply absent from the \"good feelings\" accounts.\n\n**Motivator gap (Step 4):** The most powerful single predictor of extreme positive feelings was *achievement* — a concrete sense of having accomplished something. The second was *recognition* specifically tied to achievement. What was largely absent from either list: salary increases, benefits improvements, or office upgrades on the positive side; lack of achievement or recognition on the negative side.\n\n**Enrichment prescription (Step 5):** Herzberg's prescriptive conclusion — developed at length in the 1968 HBR article — was that companies systematically over-invested in KITA (Kick In The Ass, his term for hygiene interventions: raises, perks, threats) and under-invested in job enrichment. The practical prescription: increase the vertical complexity of jobs by giving people genuine ownership of outcomes, removing supervisory controls while maintaining accountability, providing direct feedback from the work, and creating visible advancement paths.\n\n**Legacy (Step 6):** The *Motivation to Work* has been cited over 1.4 million times according to Google Scholar. Herzberg's subsequent studies replicated the finding across 12 countries and multiple occupational groups, with consistent core results: the two-factor asymmetry holds across cultural contexts for knowledge workers, though the specific factor weights shift.\n\n**Sources:** Herzberg, Frederick, Mausner, Bernard, & Snyderman, Barbara Bloch. *The Motivation to Work.* Wiley, 1959. Herzberg, Frederick. \"One More Time: How Do You Motivate Employees?\" *Harvard Business Review*, Vol. 46, No. 1 (January–February 1968), pp. 53–62. https://hbr.org/2003/01/one-more-time-how-do-you-motivate-employees\n\nFile v1.0.2:skill-card.md\n\n## Description: <br>\nHelps agents diagnose workplace motivation and retention issues using Herzberg's two-factor theory, separating hygiene factors from true motivators before recommending job-enrichment interventions. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[deciqai](https://clawhub.ai/user/deciqai) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nManagers, founders, HR partners, and team leads use this skill to structure conversations about low engagement, retention, compensation design, role design, and performance systems. It produces a two-factor diagnosis that distinguishes hygiene fixes from motivator interventions such as recognition, ownership, autonomy, and growth. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: The skill may activate on broad motivation-related language that is unrelated to workplace motivation or retention. <br>\nMitigation: Ignore or disable the skill when the user's discussion only happens to use motivation-related words outside the skill's intended HR and management context. <br>\nRisk: Compensation, retention, and workplace-design recommendations can affect employees and organizations if treated as final decisions. <br>\nMitigation: Use the output as an advisory framework and review proposed changes with appropriate human judgment before applying them. <br>\n\n\n## Reference(s): <br>\n- [ClawHub Skill Page](https://clawhub.ai/deciqai/skills/herzberg-two-factor) <br>\n- [Publisher Profile](https://clawhub.ai/user/deciqai) <br>\n- [Sources - herzberg-two-factor](references/sources.md) <br>\n- [Method in Action: Herzberg's Pittsburgh Study and the Critical Incident Method (1959)](examples/herzbergs-pittsburgh-study-and-the-critical-incident-method-1959.md) <br>\n- [One More Time: How Do You Motivate Employees?](https://hbr.org/2003/01/one-more-time-how-do-you-motivate-employees) <br>\n- [Motivation Through the Design of Work](https://doi.org/10.1016/0030-5073(76)90016-7) <br>\n- [Self-Determination and Intrinsic Motivation in Human Behavior](https://doi.org/10.1037/0033-295X.87.1.1) <br>\n- [The Critical Incident Technique](https://doi.org/10.1037/h0061470) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [text, markdown, guidance] <br>\n**Output Format:** [Markdown with a structured Two-Factor Diagnosis table and coaching prompts] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [Markdown-only advisory output; no tool calls, credential handling, persistence, or executable behavior.] <br>\n\n## Skill Version(s): <br>\n1.0.2 (source: server-resolved release metadata) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>\n\nArchive v1.0.1: 5 files, 9456 bytes\n\nFiles: examples/herzbergs-pittsburgh-study-and-the-critical-incident-method-1959.md (3610b), references/sources.md (2348b), skill-card.md (2358b), SKILL.md (9720b), _meta.json (138b)\n\nFile v1.0.1:SKILL.md\n\n---\nname: herzberg-two-factor\ndescription: \"Activate when: someone says 'why isn't the team motivated,' 'we raised salaries but morale didn't improve,' 'people keep leaving for better opportunities,' 'employee engagement is low,' 'how do I retain engineers,' or when designing compensation, job roles, or performance systems.\n  Do NOT activate when: the problem is a skill gap (people lack capability, not motivation); or the worker is in extreme economic precarity where basic survival income is the issue.\"\n---\n\n# Herzberg Two-Factor Theory\n\n## Overview\n\nHerzberg's 1959 Pittsburgh study found satisfaction and dissatisfaction are **two independent axes**. **Hygiene factors** (salary, working conditions, job security) only remove dissatisfaction — never create motivation. **Motivators** (achievement, recognition, responsibility, growth, the work itself) create genuine engagement. More hygiene spending never produces motivation; only **job enrichment** — redesigning work for higher responsibility and autonomy — does.\n\n**Composition with neighbors:** Use [principal-agent](../principal-agent/SKILL.md) when incentive structures keep failing (designers mistake hygiene for motivators). Use [nudge-theory](../nudge-theory/SKILL.md) after Herzberg to design low-friction paths to the motivating actions identified.\n\n## When to Use\n\n- Team shows **adequate performance but low energy** — people meet the minimum but go no further\n- Talent **leaving for \"better opportunities\"** and exit interviews are uninformative\n- **Compensation recently increased** but morale didn't improve, or reset within months\n- **Designing** compensation structure, job role, or performance review system\n- Someone says: *\"motivation,\" \"engagement,\" \"retention,\" \"why isn't the team energized\"*\n\n**When NOT to use:** Clear hygiene gap exists (salary below market, unsafe conditions) — fix those first. Skill gap, not motivation gap. Very short time horizon (72-hour sprint).\n\n## Coaching Novices (Adaptive Front Door)\n\n- **Engine mode:** specific team/role described → run The Process directly.\n- **Coach mode:** unfamiliar or no concrete case → guide step by step.\n\nIn Coach mode, respond one step at a time. Each [WAIT] is a hard stop — output only that step's question, then stop.\n\n1. One-line what-it-is: salary/benefits can only *remove unhappiness* — only challenging work, real responsibility, and recognition for achievement create genuine motivation.\n2. Check fit against When to Use / When NOT to use. If clear hygiene gap exists, redirect to fixing hygiene first.\n3. Elicit their real case — \"people aren't motivated\" is not a case; get the specific behavioral signal.\n> **[WAIT — do not advance until user responds]**\n4. Classify each complaint/satisfaction item as hygiene or motivator one at a time before prescribing.\n> **[WAIT — do not advance until user responds]**\n5. Close: \"The reason raising salary didn't fix this is ___. The one motivator intervention most likely to move engagement here is ___.\"\n> **[WAIT — do not advance until user responds]**\n\n## The Process\n\nRun the **Two-Factor Diagnosis**. **Stop-rule:** if Step 2 reveals clear hygiene gaps (pay below market, unsafe environment), stop and address those before any motivator work.\n\n1. **Collect complaint/satisfaction inventory** via exit interviews, stay interviews, 1:1s, or surveys — specific behavioral events, not abstract ratings.\n2. **Classify each item:** Hygiene (context of work: salary, benefits, security, working conditions, policy, supervision, peer relationships) vs. Motivator (content of work: achievement, recognition for achievement, work itself, responsibility/autonomy, growth/advancement). Classification test: if removing it causes active unhappiness but adding more habituates quickly → hygiene.\n3. **Assess hygiene baseline** vs. market standard. Set a \"hygiene floor\" — the threshold where it no longer drives active dissatisfaction. Prioritize: salary → job security → working conditions → interpersonal environment.\n4. **Diagnose motivator gaps** across five core motivators: Achievement (challenging, completable goals?), Recognition (specific, prompt, tied to achievement?), Work itself (varied, challenging?), Responsibility (real ownership?), Growth (visible path forward?).\n5. **Design job enrichment (vertical loading):** remove procedural controls while keeping accountability; give direct feedback from the work; assign whole units of work; add direct client/user contact; increase technical scope. Not horizontal loading (more same-type tasks).\n6. **Monitor and iterate** quarterly — hygiene satisfaction habituates in weeks; motivator satisfaction is durable but evolves as people grow.\n\n### Output: Two-Factor Diagnosis\n\n```\n# Two-Factor Diagnosis: <team / role>\nHygiene floor status: <below / at / above floor> | Required fixes: <>\n| Hygiene Factor | Current | Market std | Gap | Priority |\n| Motivator | Signal (strong/weak/absent) | Evidence |\nPrimary motivator gap: <>\n| Enrichment Intervention | Motivator targeted | What changes | Owner |\nMonitoring: hygiene cadence <> | motivator cadence <> | lead indicator <>\n```\n\n*→ Method in Action: [Herzberg's Pittsburgh Study and the Critical Incident Method (1959)](examples/herzbergs-pittsburgh-study-and-the-critical-incident-method-1959.md)*\n\n## Motivation Packs\n\n- **Software engineering:** hygiene failures = opaque promotion, inconsistent code review. Motivators: full-feature ownership, tech decision authority, open-source/conference recognition.\n- **Early-stage startups:** fix hygiene (salary at living-cost threshold, equity clarity) before mission rhetoric — narrative doesn't motivate someone who can't pay rent.\n- **Sales:** commission is hygiene when expected at market; becomes motivator only tied to specific achievement. Recognize wins publicly; give territory/account ownership.\n- **Product management:** dominant gap = work fragmentation (PMs as request-gatherers). Enrichment: direct user access, full problem-space ownership, visible path to measurable outcomes.\n\n## Applying It Well\n\n- Fix hygiene to the floor, not best-in-class — above-market hygiene costs more with zero retention advantage.\n- Salary raises decay in weeks; design for motivators, not raises.\n- Recognition must be specific, proximate, and tied to a named achievement — not generic and annual.\n- Vertical loading only: more authority, accountability, direct feedback, complete ownership — not more tasks of the same type.\n- Motivators habituate upward; job enrichment is continuous design, not a one-time fix.\n\n*→ Primary sources: [references/sources.md](references/sources.md)*\n\n## Common Rationalizations\n\n**[D] = designed upfront | [O] = observed in real use. [O] entries are more valuable.**\n\n| Fake move | Reality |\n|---|---|\n| [D] **\"We gave everyone a 15% raise and retention improved, so salary is a motivator.\"** | Short-term retention = hygiene restoration. Track the same cohort 6–12 months: discretionary effort returns to pre-raise baseline. |\n| [D] **\"Our employees say they care most about compensation in surveys.\"** | Surveys skew toward hygiene factors (legible, discussable). Critical incident data consistently surfaces achievement and recognition as primary. |\n| [D] **\"We added flexible hours and a gym benefit — that should help motivation.\"** | Both are hygiene factors. Neither creates engagement when work is unchallenging and responsibility is absent. |\n| [D] **\"If we give people more autonomy, they'll make mistakes.\"** | Studies show increased autonomy improves both performance and retention when paired with clear accountability structures. |\n| [D] **\"We recognize people with annual awards.\"** | Annual generic awards sever the motivational connection. Recognition must be specific, proximate, and tied to a named achievement. |\n| [D] **\"Our engineers leave for Google salaries — this is a hygiene problem.\"** | When they leave for similar-level roles at similar salaries, it's almost always a motivator failure wearing hygiene language in the exit interview. |\n| [D] **\"We enriched jobs by adding more projects.\"** | Horizontal loading. Enrichment = vertical loading: higher-scope responsibility, direct accountability, genuine decision authority. |\n| *→ Add [O] entries here after each real use — paste the actual failure pattern* | *What went wrong and why* |\n\n## Red Flags\n\n- Retention interventions default to compensation without a two-factor diagnosis\n- Exit interview data not classified by hygiene vs. motivator before designing intervention\n- Recognition is non-specific, annual, disconnected from observed achievement\n- Job enrichment operationalized as more work (horizontal) rather than more responsibility (vertical)\n- \"Culture\" used as substitute for diagnosing whether motivators are present in the actual role\n\n## Verification\n\n- [ ] Problem classified: hygiene-domain (dissatisfaction) vs. motivator-domain (low engagement despite adequate hygiene)\n- [ ] Hygiene baseline assessed against market standards before any motivator intervention\n- [ ] Motivator gaps identified through behavioral data, not attitude ratings\n- [ ] Interventions are vertical loading (responsibility, autonomy, scope) not horizontal loading\n- [ ] Recognition is specific and proximate (close in time to the achievement)\n- [ ] Monitoring plan defined with cadence for both axes\n- [ ] Two-factor asymmetry stated explicitly: fixing hygiene will not create motivation\n\n---\n\n*Part of **deciqAI Knowledge Skills** — open-source thinking skills that make rigor executable for AI agents. Built by deciqAI · https://deciqai.com · Contributions welcome — see the template at the repo root.*\n\nFile v1.0.1:_meta.json\n\n{\n  \"ownerId\": \"kn754b8sk22s8c6gjxt02bftbn88q7ye\",\n  \"slug\": \"herzberg-two-factor\",\n  \"version\": \"1.0.1\",\n  \"publishedAt\": 1783456430330\n}\n\nFile v1.0.1:references/sources.md\n\n# Sources — herzberg-two-factor\n\n> *Primary sources for the [herzberg-two-factor](../SKILL.md) skill.*\n\n- **Herzberg, Frederick, Mausner, Bernard, & Snyderman, Barbara Bloch.** *The Motivation to Work.* Wiley, 1959. **Primary source** for the two-factor theory; presents the Pittsburgh study methodology and findings. Verbatim quote above from p. 113.\n- **Herzberg, Frederick.** \"One More Time: How Do You Motivate Employees?\" *Harvard Business Review*, Vol. 46, No. 1 (January–February 1968), pp. 53–62. The practitioner account; introduces KITA and job enrichment as the prescriptive response. Verbatim quote above from p. 59. Cited approximately 1.4 million times per Google Scholar. https://hbr.org/2003/01/one-more-time-how-do-you-motivate-employees\n- **Hackman, J. Richard & Oldham, Greg R.** \"Motivation Through the Design of Work: Test of a Theory.\" *Organizational Behavior and Human Performance*, Vol. 16, No. 2 (August 1976), pp. 250–279. The empirical follow-on that operationalized job enrichment into the Job Characteristics Model (skill variety, task identity, task significance, autonomy, feedback). https://doi.org/10.1016/0030-5073(76)90016-7\n- **Deci, Edward L. & Ryan, Richard M.** \"Self-Determination and Intrinsic Motivation in Human Behavior.\" *Psychological Review*, Vol. 87, No. 1 (January 1980), pp. 1–41. The self-determination theory framework that provides the underlying mechanism for why Herzberg's motivators work — autonomy, competence, and relatedness as basic psychological needs. https://doi.org/10.1037/0033-295X.87.1.1\n- **Flanagan, John C.** \"The Critical Incident Technique.\" *Psychological Bulletin*, Vol. 51, No. 4 (July 1954), pp. 327–358. The methodological source for the data collection technique Herzberg used; establishes what critical incident data actually measures and its limitations. https://doi.org/10.1037/h0061470\n- **Not cited as evidence:** Generic management consulting surveys (\"% of employees are disengaged\") that do not distinguish hygiene and motivator dimensions are not cited here. They measure aggregate satisfaction without the two-factor decomposition, making them unsuitable for prescriptive use in this framework. Gallup Q12 scores, for example, conflate hygiene and motivator items. Use the framework to design data collection that separates the two dimensions.\n\nFile v1.0.1:examples/herzbergs-pittsburgh-study-and-the-critical-incident-method-1959.md\n\n# Method in Action: Herzberg's Pittsburgh Study and the Critical Incident Method (1959)\n\n> *Example for the [herzberg-two-factor](../SKILL.md) skill.*\n\nThe primary-source case is the original research itself — 203 accountants and engineers in Pittsburgh, 1844 incidents coded and analyzed. This is not a retrospective pop account; it is the founding empirical event.\n\n**Behavioral specification (Step 1):** Herzberg, Mausner, and Snyderman used the critical incident technique (developed by John Flanagan at the American Institutes for Research): ask people to describe a specific time at work when they felt exceptionally good or bad, what the circumstances were, what led to those feelings, and how long the feeling lasted. This produces behavioral data, not attitude ratings — it forces respondents to name actual events.\n\n**Classification (Step 2):** Across 1,844 coded incidents, the researchers found a systematic asymmetry. Factors cited when people felt *good* were predominantly: achievement (a project completed, a problem solved, a sale made), recognition (being told specifically that they had done something well), the work itself (finding the work engaging, varied, or demanding), responsibility (having real authority over outcomes), and advancement. Factors cited when people felt *bad* were predominantly: company policy and administration (arbitrary or bureaucratic rules), supervision (incompetent or unfair managers), working conditions, salary (not \"too little\" but the *process* — arbitrary raises, opaque criteria), and interpersonal relations.\n\n**Hygiene assessment (Step 3):** Salary appeared in the \"bad feelings\" data as a consistent factor — not the amount per se, but the *unfairness or opacity* of the salary process. When salary was perceived as fairly administered and at or above market, it did not appear as a satisfaction driver; it was simply absent from the \"good feelings\" accounts.\n\n**Motivator gap (Step 4):** The most powerful single predictor of extreme positive feelings was *achievement* — a concrete sense of having accomplished something. The second was *recognition* specifically tied to achievement. What was largely absent from either list: salary increases, benefits improvements, or office upgrades on the positive side; lack of achievement or recognition on the negative side.\n\n**Enrichment prescription (Step 5):** Herzberg's prescriptive conclusion — developed at length in the 1968 HBR article — was that companies systematically over-invested in KITA (Kick In The Ass, his term for hygiene interventions: raises, perks, threats) and under-invested in job enrichment. The practical prescription: increase the vertical complexity of jobs by giving people genuine ownership of outcomes, removing supervisory controls while maintaining accountability, providing direct feedback from the work, and creating visible advancement paths.\n\n**Legacy (Step 6):** The *Motivation to Work* has been cited over 1.4 million times according to Google Scholar. Herzberg's subsequent studies replicated the finding across 12 countries and multiple occupational groups, with consistent core results: the two-factor asymmetry holds across cultural contexts for knowledge workers, though the specific factor weights shift.\n\n**Sources:** Herzberg, Frederick, Mausner, Bernard, & Snyderman, Barbara Bloch. *The Motivation to Work.* Wiley, 1959. Herzberg, Frederick. \"One More Time: How Do You Motivate Employees?\" *Harvard Business Review*, Vol. 46, No. 1 (January–February 1968), pp. 53–62. https://hbr.org/2003/01/one-more-time-how-do-you-motivate-employees\n\nFile v1.0.1:skill-card.md\n\n## Description: <br>\nProvides a Herzberg two-factor diagnosis for workplace motivation, engagement, retention, compensation, and job-role design by separating hygiene factors from motivators. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[deciqai](https://clawhub.ai/user/deciqai) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nManagers, HR partners, and organizational designers use this skill to diagnose low motivation, retention, and engagement problems, then choose hygiene fixes or job-enrichment interventions based on Herzberg's two-factor model. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: Broad activation wording may cause the skill to respond during ordinary workplace motivation or retention conversations. <br>\nMitigation: Review the trigger description before installation and use the skill when a concrete motivation, engagement, retention, compensation, or job-design question is intended. <br>\n\n\n## Reference(s): <br>\n- [Sources - herzberg-two-factor](references/sources.md) <br>\n- [Herzberg's Pittsburgh Study and the Critical Incident Method (1959)](examples/herzbergs-pittsburgh-study-and-the-critical-incident-method-1959.md) <br>\n- [One More Time: How Do You Motivate Employees?](https://hbr.org/2003/01/one-more-time-how-do-you-motivate-employees) <br>\n- [Motivation Through the Design of Work: Test of a Theory](https://doi.org/10.1016/0030-5073(76)90016-7) <br>\n- [Self-Determination and Intrinsic Motivation in Human Behavior](https://doi.org/10.1037/0033-295X.87.1.1) <br>\n- [The Critical Incident Technique](https://doi.org/10.1037/h0061470) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [Analysis, Markdown, Guidance] <br>\n**Output Format:** [Markdown diagnosis, tables, and step-by-step coaching prompts] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [May stop for user input during coach mode before completing the diagnosis.] <br>\n\n## Skill Version(s): <br>\n1.0.1 (source: release evidence) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>\n\nArchive v1.0.0: 5 files, 9575 bytes\n\nFiles: examples/herzbergs-pittsburgh-study-and-the-critical-incident-method-1959.md (3610b), references/sources.md (2348b), skill-card.md (2584b), SKILL.md (9720b), _meta.json (138b)\n\nFile v1.0.0:SKILL.md\n\n---\nname: herzberg-two-factor\ndescription: \"Activate when: someone says 'why isn't the team motivated,' 'we raised salaries but morale didn't improve,' 'people keep leaving for better opportunities,' 'employee engagement is low,' 'how do I retain engineers,' or when designing compensation, job roles, or performance systems.\n  Do NOT activate when: the problem is a skill gap (people lack capability, not motivation); or the worker is in extreme economic precarity where basic survival income is the issue.\"\n---\n\n# Herzberg Two-Factor Theory\n\n## Overview\n\nHerzberg's 1959 Pittsburgh study found satisfaction and dissatisfaction are **two independent axes**. **Hygiene factors** (salary, working conditions, job security) only remove dissatisfaction — never create motivation. **Motivators** (achievement, recognition, responsibility, growth, the work itself) create genuine engagement. More hygiene spending never produces motivation; only **job enrichment** — redesigning work for higher responsibility and autonomy — does.\n\n**Composition with neighbors:** Use [principal-agent](../principal-agent/SKILL.md) when incentive structures keep failing (designers mistake hygiene for motivators). Use [nudge-theory](../nudge-theory/SKILL.md) after Herzberg to design low-friction paths to the motivating actions identified.\n\n## When to Use\n\n- Team shows **adequate performance but low energy** — people meet the minimum but go no further\n- Talent **leaving for \"better opportunities\"** and exit interviews are uninformative\n- **Compensation recently increased** but morale didn't improve, or reset within months\n- **Designing** compensation structure, job role, or performance review system\n- Someone says: *\"motivation,\" \"engagement,\" \"retention,\" \"why isn't the team energized\"*\n\n**When NOT to use:** Clear hygiene gap exists (salary below market, unsafe conditions) — fix those first. Skill gap, not motivation gap. Very short time horizon (72-hour sprint).\n\n## Coaching Novices (Adaptive Front Door)\n\n- **Engine mode:** specific team/role described → run The Process directly.\n- **Coach mode:** unfamiliar or no concrete case → guide step by step.\n\nIn Coach mode, respond one step at a time. Each [WAIT] is a hard stop — output only that step's question, then stop.\n\n1. One-line what-it-is: salary/benefits can only *remove unhappiness* — only challenging work, real responsibility, and recognition for achievement create genuine motivation.\n2. Check fit against When to Use / When NOT to use. If clear hygiene gap exists, redirect to fixing hygiene first.\n3. Elicit their real case — \"people aren't motivated\" is not a case; get the specific behavioral signal.\n> **[WAIT — do not advance until user responds]**\n4. Classify each complaint/satisfaction item as hygiene or motivator one at a time before prescribing.\n> **[WAIT — do not advance until user responds]**\n5. Close: \"The reason raising salary didn't fix this is ___. The one motivator intervention most likely to move engagement here is ___.\"\n> **[WAIT — do not advance until user responds]**\n\n## The Process\n\nRun the **Two-Factor Diagnosis**. **Stop-rule:** if Step 2 reveals clear hygiene gaps (pay below market, unsafe environment), stop and address those before any motivator work.\n\n1. **Collect complaint/satisfaction inventory** via exit interviews, stay interviews, 1:1s, or surveys — specific behavioral events, not abstract ratings.\n2. **Classify each item:** Hygiene (context of work: salary, benefits, security, working conditions, policy, supervision, peer relationships) vs. Motivator (content of work: achievement, recognition for achievement, work itself, responsibility/autonomy, growth/advancement). Classification test: if removing it causes active unhappiness but adding more habituates quickly → hygiene.\n3. **Assess hygiene baseline** vs. market standard. Set a \"hygiene floor\" — the threshold where it no longer drives active dissatisfaction. Prioritize: salary → job security → working conditions → interpersonal environment.\n4. **Diagnose motivator gaps** across five core motivators: Achievement (challenging, completable goals?), Recognition (specific, prompt, tied to achievement?), Work itself (varied, challenging?), Responsibility (real ownership?), Growth (visible path forward?).\n5. **Design job enrichment (vertical loading):** remove procedural controls while keeping accountability; give direct feedback from the work; assign whole units of work; add direct client/user contact; increase technical scope. Not horizontal loading (more same-type tasks).\n6. **Monitor and iterate** quarterly — hygiene satisfaction habituates in weeks; motivator satisfaction is durable but evolves as people grow.\n\n### Output: Two-Factor Diagnosis\n\n```\n# Two-Factor Diagnosis: <team / role>\nHygiene floor status: <below / at / above floor> | Required fixes: <>\n| Hygiene Factor | Current | Market std | Gap | Priority |\n| Motivator | Signal (strong/weak/absent) | Evidence |\nPrimary motivator gap: <>\n| Enrichment Intervention | Motivator targeted | What changes | Owner |\nMonitoring: hygiene cadence <> | motivator cadence <> | lead indicator <>\n```\n\n*→ Method in Action: [Herzberg's Pittsburgh Study and the Critical Incident Method (1959)](examples/herzbergs-pittsburgh-study-and-the-critical-incident-method-1959.md)*\n\n## Motivation Packs\n\n- **Software engineering:** hygiene failures = opaque promotion, inconsistent code review. Motivators: full-feature ownership, tech decision authority, open-source/conference recognition.\n- **Early-stage startups:** fix hygiene (salary at living-cost threshold, equity clarity) before mission rhetoric — narrative doesn't motivate someone who can't pay rent.\n- **Sales:** commission is hygiene when expected at market; becomes motivator only tied to specific achievement. Recognize wins publicly; give territory/account ownership.\n- **Product management:** dominant gap = work fragmentation (PMs as request-gatherers). Enrichment: direct user access, full problem-space ownership, visible path to measurable outcomes.\n\n## Applying It Well\n\n- Fix hygiene to the floor, not best-in-class — above-market hygiene costs more with zero retention advantage.\n- Salary raises decay in weeks; design for motivators, not raises.\n- Recognition must be specific, proximate, and tied to a named achievement — not generic and annual.\n- Vertical loading only: more authority, accountability, direct feedback, complete ownership — not more tasks of the same type.\n- Motivators habituate upward; job enrichment is continuous design, not a one-time fix.\n\n*→ Primary sources: [references/sources.md](references/sources.md)*\n\n## Common Rationalizations\n\n**[D] = designed upfront | [O] = observed in real use. [O] entries are more valuable.**\n\n| Fake move | Reality |\n|---|---|\n| [D] **\"We gave everyone a 15% raise and retention improved, so salary is a motivator.\"** | Short-term retention = hygiene restoration. Track the same cohort 6–12 months: discretionary effort returns to pre-raise baseline. |\n| [D] **\"Our employees say they care most about compensation in surveys.\"** | Surveys skew toward hygiene factors (legible, discussable). Critical incident data consistently surfaces achievement and recognition as primary. |\n| [D] **\"We added flexible hours and a gym benefit — that should help motivation.\"** | Both are hygiene factors. Neither creates engagement when work is unchallenging and responsibility is absent. |\n| [D] **\"If we give people more autonomy, they'll make mistakes.\"** | Studies show increased autonomy improves both performance and retention when paired with clear accountability structures. |\n| [D] **\"We recognize people with annual awards.\"** | Annual generic awards sever the motivational connection. Recognition must be specific, proximate, and tied to a named achievement. |\n| [D] **\"Our engineers leave for Google salaries — this is a hygiene problem.\"** | When they leave for similar-level roles at similar salaries, it's almost always a motivator failure wearing hygiene language in the exit interview. |\n| [D] **\"We enriched jobs by adding more projects.\"** | Horizontal loading. Enrichment = vertical loading: higher-scope responsibility, direct accountability, genuine decision authority. |\n| *→ Add [O] entries here after each real use — paste the actual failure pattern* | *What went wrong and why* |\n\n## Red Flags\n\n- Retention interventions default to compensation without a two-factor diagnosis\n- Exit interview data not classified by hygiene vs. motivator before designing intervention\n- Recognition is non-specific, annual, disconnected from observed achievement\n- Job enrichment operationalized as more work (horizontal) rather than more responsibility (vertical)\n- \"Culture\" used as substitute for diagnosing whether motivators are present in the actual role\n\n## Verification\n\n- [ ] Problem classified: hygiene-domain (dissatisfaction) vs. motivator-domain (low engagement despite adequate hygiene)\n- [ ] Hygiene baseline assessed against market standards before any motivator intervention\n- [ ] Motivator gaps identified through behavioral data, not attitude ratings\n- [ ] Interventions are vertical loading (responsibility, autonomy, scope) not horizontal loading\n- [ ] Recognition is specific and proximate (close in time to the achievement)\n- [ ] Monitoring plan defined with cadence for both axes\n- [ ] Two-factor asymmetry stated explicitly: fixing hygiene will not create motivation\n\n---\n\n*Part of **deciqAI Knowledge Skills** — open-source thinking skills that make rigor executable for AI agents. Built by deciqAI · https://deciqai.com · Contributions welcome — see the template at the repo root.*\n\nFile v1.0.0:_meta.json\n\n{\n  \"ownerId\": \"kn754b8sk22s8c6gjxt02bftbn88q7ye\",\n  \"slug\": \"herzberg-two-factor\",\n  \"version\": \"1.0.0\",\n  \"publishedAt\": 1782713857514\n}\n\nFile v1.0.0:references/sources.md\n\n# Sources — herzberg-two-factor\n\n> *Primary sources for the [herzberg-two-factor](../SKILL.md) skill.*\n\n- **Herzberg, Frederick, Mausner, Bernard, & Snyderman, Barbara Bloch.** *The Motivation to Work.* Wiley, 1959. **Primary source** for the two-factor theory; presents the Pittsburgh study methodology and findings. Verbatim quote above from p. 113.\n- **Herzberg, Frederick.** \"One More Time: How Do You Motivate Employees?\" *Harvard Business Review*, Vol. 46, No. 1 (January–February 1968), pp. 53–62. The practitioner account; introduces KITA and job enrichment as the prescriptive response. Verbatim quote above from p. 59. Cited approximately 1.4 million times per Google Scholar. https://hbr.org/2003/01/one-more-time-how-do-you-motivate-employees\n- **Hackman, J. Richard & Oldham, Greg R.** \"Motivation Through the Design of Work: Test of a Theory.\" *Organizational Behavior and Human Performance*, Vol. 16, No. 2 (August 1976), pp. 250–279. The empirical follow-on that operationalized job enrichment into the Job Characteristics Model (skill variety, task identity, task significance, autonomy, feedback). https://doi.org/10.1016/0030-5073(76)90016-7\n- **Deci, Edward L. & Ryan, Richard M.** \"Self-Determination and Intrinsic Motivation in Human Behavior.\" *Psychological Review*, Vol. 87, No. 1 (January 1980), pp. 1–41. The self-determination theory framework that provides the underlying mechanism for why Herzberg's motivators work — autonomy, competence, and relatedness as basic psychological needs. https://doi.org/10.1037/0033-295X.87.1.1\n- **Flanagan, John C.** \"The Critical Incident Technique.\" *Psychological Bulletin*, Vol. 51, No. 4 (July 1954), pp. 327–358. The methodological source for the data collection technique Herzberg used; establishes what critical incident data actually measures and its limitations. https://doi.org/10.1037/h0061470\n- **Not cited as evidence:** Generic management consulting surveys (\"% of employees are disengaged\") that do not distinguish hygiene and motivator dimensions are not cited here. They measure aggregate satisfaction without the two-factor decomposition, making them unsuitable for prescriptive use in this framework. Gallup Q12 scores, for example, conflate hygiene and motivator items. Use the framework to design data collection that separates the two dimensions.\n\nFile v1.0.0:examples/herzbergs-pittsburgh-study-and-the-critical-incident-method-1959.md\n\n# Method in Action: Herzberg's Pittsburgh Study and the Critical Incident Method (1959)\n\n> *Example for the [herzberg-two-factor](../SKILL.md) skill.*\n\nThe primary-source case is the original research itself — 203 accountants and engineers in Pittsburgh, 1844 incidents coded and analyzed. This is not a retrospective pop account; it is the founding empirical event.\n\n**Behavioral specification (Step 1):** Herzberg, Mausner, and Snyderman used the critical incident technique (developed by John Flanagan at the American Institutes for Research): ask people to describe a specific time at work when they felt exceptionally good or bad, what the circumstances were, what led to those feelings, and how long the feeling lasted. This produces behavioral data, not attitude ratings — it forces respondents to name actual events.\n\n**Classification (Step 2):** Across 1,844 coded incidents, the researchers found a systematic asymmetry. Factors cited when people felt *good* were predominantly: achievement (a project completed, a problem solved, a sale made), recognition (being told specifically that they had done something well), the work itself (finding the work engaging, varied, or demanding), responsibility (having real authority over outcomes), and advancement. Factors cited when people felt *bad* were predominantly: company policy and administration (arbitrary or bureaucratic rules), supervision (incompetent or unfair managers), working conditions, salary (not \"too little\" but the *process* — arbitrary raises, opaque criteria), and interpersonal relations.\n\n**Hygiene assessment (Step 3):** Salary appeared in the \"bad feelings\" data as a consistent factor — not the amount per se, but the *unfairness or opacity* of the salary process. When salary was perceived as fairly administered and at or above market, it did not appear as a satisfaction driver; it was simply absent from the \"good feelings\" accounts.\n\n**Motivator gap (Step 4):** The most powerful single predictor of extreme positive feelings was *achievement* — a concrete sense of having accomplished something. The second was *recognition* specifically tied to achievement. What was largely absent from either list: salary increases, benefits improvements, or office upgrades on the positive side; lack of achievement or recognition on the negative side.\n\n**Enrichment prescription (Step 5):** Herzberg's prescriptive conclusion — developed at length in the 1968 HBR article — was that companies systematically over-invested in KITA (Kick In The Ass, his term for hygiene interventions: raises, perks, threats) and under-invested in job enrichment. The practical prescription: increase the vertical complexity of jobs by giving people genuine ownership of outcomes, removing supervisory controls while maintaining accountability, providing direct feedback from the work, and creating visible advancement paths.\n\n**Legacy (Step 6):** The *Motivation to Work* has been cited over 1.4 million times according to Google Scholar. Herzberg's subsequent studies replicated the finding across 12 countries and multiple occupational groups, with consistent core results: the two-factor asymmetry holds across cultural contexts for knowledge workers, though the specific factor weights shift.\n\n**Sources:** Herzberg, Frederick, Mausner, Bernard, & Snyderman, Barbara Bloch. *The Motivation to Work.* Wiley, 1959. Herzberg, Frederick. \"One More Time: How Do You Motivate Employees?\" *Harvard Business Review*, Vol. 46, No. 1 (January–February 1968), pp. 53–62. https://hbr.org/2003/01/one-more-time-how-do-you-motivate-employees\n\nFile v1.0.0:skill-card.md\n\n## Description: <br>\nHelps an agent use Herzberg's two-factor theory to diagnose motivation, engagement, and retention issues by separating hygiene gaps from motivator gaps and recommending job enrichment. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[deciqai](https://clawhub.ai/user/deciqai) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nEmployees, managers, and HR or people-operations practitioners use this skill to diagnose low motivation, engagement, and retention problems. It helps distinguish hygiene issues such as pay, safety, and working conditions from motivators such as achievement, recognition, responsibility, growth, and meaningful work. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: The skill's recommendations can be overused as a complete management diagnosis when issues involve pay inequity, unsafe conditions, burnout, harassment, or skill gaps. <br>\nMitigation: Use it as one management lens, first address clear hygiene or safety problems, and route legal, HR, safety, or capability concerns to the appropriate process. <br>\n\n\n## Reference(s): <br>\n- [ClawHub skill page](https://clawhub.ai/deciqai/skills/herzberg-two-factor) <br>\n- [Sources - herzberg-two-factor](references/sources.md) <br>\n- [Herzberg's Pittsburgh Study and the Critical Incident Method (1959)](examples/herzbergs-pittsburgh-study-and-the-critical-incident-method-1959.md) <br>\n- [One More Time: How Do You Motivate Employees?](https://hbr.org/2003/01/one-more-time-how-do-you-motivate-employees) <br>\n- [Motivation Through the Design of Work: Test of a Theory](https://doi.org/10.1016/0030-5073(76)90016-7) <br>\n- [Self-Determination and Intrinsic Motivation in Human Behavior](https://doi.org/10.1037/0033-295X.87.1.1) <br>\n- [The Critical Incident Technique](https://doi.org/10.1037/h0061470) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [Text, Markdown, Guidance] <br>\n**Output Format:** [Markdown diagnosis template and conversational guidance] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [No executable behavior, credential use, network access, or hidden data handling.] <br>\n\n## Skill Version(s): <br>\n1.0.0 (source: server release evidence) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>","readmeExcerpt":"Skill: Herzberg Two-Factor Theory Owner: deciqai Summary: Activate when: someone says 'why isn't the team motivated,' 'we raised salaries but morale didn't improve,' 'people keep leaving for better opportunities,' '... Tags: latest:1.0.5 Version history: v1.0.5 | 2026-07-16T18:02:04.371Z | user Description tail link + agents machine-readable metadata line (deciqai.com/s/herzberg-two-factor.json) v1.0.4 | 2026-07-09T1","codeSnippets":[],"executableExamples":[{"language":"text","snippet":"# Two-Factor Diagnosis: <team / role>\nHygiene floor status: <below / at / above floor> | Required fixes: <>\n| Hygiene Factor | Current | Market std | Gap | Priority |\n| Motivator | Signal (strong/weak/absent) | Evidence |\nPrimary motivator gap: <>\n| Enrichment Intervention | Motivator targeted | What changes | Owner |\nMonitoring: hygiene cadence <> | motivator cadence <> | lead indicator <>"},{"language":"text","snippet":"# Two-Factor Diagnosis: <team / role>\nHygiene floor status: <below / at / above floor> | Required fixes: <>\n| Hygiene Factor | Current | Market std | Gap | Priority |\n| Motivator | Signal (strong/weak/absent) | Evidence |\nPrimary motivator gap: <>\n| Enrichment Intervention | Motivator targeted | What changes | Owner |\nMonitoring: hygiene cadence <> | motivator cadence <> | lead indicator <>"},{"language":"text","snippet":"# Two-Factor Diagnosis: <team / role>\nHygiene floor status: <below / at / above floor> | Required fixes: <>\n| Hygiene Factor | Current | Market std | Gap | Priority |\n| Motivator | Signal (strong/weak/absent) | Evidence |\nPrimary motivator gap: <>\n| Enrichment Intervention | Motivator targeted | What changes | Owner |\nMonitoring: hygiene cadence <> | motivator cadence <> | lead indicator <>"},{"language":"text","snippet":"# Two-Factor Diagnosis: <team / role>\nHygiene floor status: <below / at / above floor> | Required fixes: <>\n| Hygiene Factor | Current | Market std | Gap | Priority |\n| Motivator | Signal (strong/weak/absent) | Evidence |\nPrimary motivator gap: <>\n| Enrichment Intervention | Motivator targeted | What changes | Owner |\nMonitoring: hygiene cadence <> | motivator cadence <> | lead indicator <>"},{"language":"text","snippet":"# Two-Factor Diagnosis: <team / role>\nHygiene floor status: <below / at / above floor> | Required fixes: <>\n| Hygiene Factor | Current | Market std | Gap | Priority |\n| Motivator | Signal (strong/weak/absent) | Evidence |\nPrimary motivator gap: <>\n| Enrichment Intervention | Motivator targeted | What changes | Owner |\nMonitoring: hygiene cadence <> | motivator cadence <> | lead indicator <>"},{"language":"text","snippet":"# Two-Factor Diagnosis: <team / role>\nHygiene floor status: <below / at / above floor> | Required fixes: <>\n| Hygiene Factor | Current | Market std | Gap | Priority |\n| Motivator | Signal (strong/weak/absent) | Evidence |\nPrimary motivator gap: <>\n| Enrichment Intervention | Motivator targeted | What changes | Owner |\nMonitoring: hygiene cadence <> | motivator cadence <> | lead indicator <>"}],"parameters":null,"dependencies":[],"permissions":[],"extractedFiles":[{"path":"SKILL.md","content":"---\nname: herzberg-two-factor\ndescription: \"Activate when: someone says 'why isn't the team motivated,' 'we raised salaries but morale didn't improve,' 'people keep leaving for better opportunities,' 'employee engagement is low,' 'how do I retain engineers,' or when designing compensation, job roles, or performance systems.\n  Do NOT activate when: the problem is a skill gap (people lack capability, not motivation); or the worker is in extreme economic precarity where basic survival income is the issue. More: deciqai.com/c/herzberg-two-factor\"\n---\n\n# Herzberg Two-Factor Theory\n\n## Overview\n\nHerzberg's 1959 Pittsburgh study found satisfaction and dissatisfaction are **two independent axes**. **Hygiene factors** (salary, working conditions, job security) only remove dissatisfaction — never create motivation. **Motivators** (achievement, recognition, responsibility, growth, the work itself) create genuine engagement. More hygiene spending never produces motivation; only **job enrichment** — redesigning work for higher responsibility and autonomy — does.\n\n**Composition with neighbors:** Use principal-agent when incentive structures keep failing (designers mistake hygiene for motivators). Use nudge-theory after Herzberg to design low-friction paths to the motivating actions identified.\n\n## When to Use\n\n- Team shows **adequate performance but low energy** — people meet the minimum but go no further\n- Talent **leaving for \"better opportunities\"** and exit interviews are uninformative\n- **Compensation recently increased** but morale didn't improve, or reset within months\n- **Designing** compensation structure, job role, or performance review system\n- **Bidding wars for scarce AI/ML talent** — matched counter-offers still lose people; AI-capex-driven pay bands keep rising but engagement doesn't follow (an AI-native competitor is out-motivating, not just out-paying, you)\n- Someone says: *\"motivation,\" \"engagement,\" \"retention,\" \"why isn't the team energized\"*\n\n**When NOT to use:** Clear hygiene gap exists (salary below market, unsafe conditions) — fix those first. Skill gap, not motivation gap. Very short time horizon (72-hour sprint).\n\n## Coaching Novices (Adaptive Front Door)\n\n- **Engine mode:** specific team/role described → run The Process directly.\n- **Coach mode:** unfamiliar or no concrete case → guide step by step.\n\nIn Coach mode, respond one step at a time. Each [WAIT] is a hard stop — output only that step's question, then stop.\n\n1. One-line what-it-is: salary/benefits can only *remove unhappiness* — only challenging work, real responsibility, and recognition for achievement create genuine motivation.\n2. Check fit against When to Use / When NOT to use. If clear hygiene gap exists, redirect to fixing hygiene first.\n3. Elicit their real case — \"people aren't motivated\" is not a case; get the specific behavioral signal.\n> **[WAIT — do not advance until user responds]**\n4. Classify each complaint/satisfaction item as hygiene or motivator one at a time"},{"path":"_meta.json","content":"{\n  \"ownerId\": \"kn754b8sk22s8c6gjxt02bftbn88q7ye\",\n  \"slug\": \"herzberg-two-factor\",\n  \"version\": \"1.0.5\",\n  \"publishedAt\": 1784224924371\n}"},{"path":"references/sources.md","content":"# Sources — herzberg-two-factor\n\n> *Primary sources for the [herzberg-two-factor](../SKILL.md) skill.*\n\n- **Herzberg, Frederick, Mausner, Bernard, & Snyderman, Barbara Bloch.** *The Motivation to Work.* Wiley, 1959. **Primary source** for the two-factor theory; presents the Pittsburgh study methodology and findings. Verbatim quote above from p. 113.\n- **Herzberg, Frederick.** \"One More Time: How Do You Motivate Employees?\" *Harvard Business Review*, Vol. 46, No. 1 (January–February 1968), pp. 53–62. The practitioner account; introduces KITA and job enrichment as the prescriptive response. Verbatim quote above from p. 59. One of HBR's most-requested reprints of all time (reported to have sold well over a million reprints by the late 1980s). https://hbr.org/2003/01/one-more-time-how-do-you-motivate-employees\n- **Hackman, J. Richard & Oldham, Greg R.** \"Motivation Through the Design of Work: Test of a Theory.\" *Organizational Behavior and Human Performance*, Vol. 16, No. 2 (August 1976), pp. 250–279. The empirical follow-on that operationalized job enrichment into the Job Characteristics Model (skill variety, task identity, task significance, autonomy, feedback). https://doi.org/10.1016/0030-5073(76)90016-7\n- **Deci, Edward L. & Ryan, Richard M.** \"The Empirical Exploration of Intrinsic Motivational Processes.\" In L. Berkowitz (ed.), *Advances in Experimental Social Psychology*, Vol. 13 (Academic Press, 1980), pp. 39–80. An early statement of the self-determination framework that provides the underlying mechanism for why Herzberg's motivators work — autonomy, competence, and relatedness as basic psychological needs. https://doi.org/10.1016/S0065-2601(08)60130-6\n- **Flanagan, John C.** \"The Critical Incident Technique.\" *Psychological Bulletin*, Vol. 51, No. 4 (July 1954), pp. 327–358. The methodological source for the data collection technique Herzberg used; establishes what critical incident data actually measures and its limitations. https://doi.org/10.1037/h0061470\n- **Ryan, Richard M. & Deci, Edward L.** *Self-Determination Theory: Basic Psychological Needs in Motivation, Development, and Wellness.* Guilford Press, 2017. The consolidated modern statement of SDT — autonomy, competence, and relatedness — which supplies the mechanism for why Herzberg's motivators (responsibility, achievement, growth) durably drive engagement while hygiene (pay, conditions) does not. Used to ground the 2024–2026 AI-talent example.\n- **Contemporary AI-talent market context (2024–2026):** Public business reporting through 2024–2025 broadly documented (a) record capital-expenditure commitments to AI infrastructure by major AI labs and hyperscalers, and (b) sharply elevated compensation and aggressive cross-lab recruiting for scarce frontier AI/ML researchers and engineers. These are widely-reported, durable market facts used as *setting* for the example; no single proprietary figure or specific dollar amount is asserted as evidence here. Confirm current specifics again"},{"path":"examples/herzbergs-pittsburgh-study-and-the-critical-incident-method-1959.md","content":"# Method in Action: Herzberg's Pittsburgh Study and the Critical Incident Method (1959)\n\n> *Example for the [herzberg-two-factor](../SKILL.md) skill.*\n\nThe primary-source case is the original research itself — 203 accountants and engineers in Pittsburgh, 1844 incidents coded and analyzed. This is not a retrospective pop account; it is the founding empirical event.\n\n**Behavioral specification (Step 1):** Herzberg, Mausner, and Snyderman used the critical incident technique (developed by John Flanagan at the American Institutes for Research): ask people to describe a specific time at work when they felt exceptionally good or bad, what the circumstances were, what led to those feelings, and how long the feeling lasted. This produces behavioral data, not attitude ratings — it forces respondents to name actual events.\n\n**Classification (Step 2):** Across 1,844 coded incidents, the researchers found a systematic asymmetry. Factors cited when people felt *good* were predominantly: achievement (a project completed, a problem solved, a sale made), recognition (being told specifically that they had done something well), the work itself (finding the work engaging, varied, or demanding), responsibility (having real authority over outcomes), and advancement. Factors cited when people felt *bad* were predominantly: company policy and administration (arbitrary or bureaucratic rules), supervision (incompetent or unfair managers), working conditions, salary (not \"too little\" but the *process* — arbitrary raises, opaque criteria), and interpersonal relations.\n\n**Hygiene assessment (Step 3):** Salary appeared in the \"bad feelings\" data as a consistent factor — not the amount per se, but the *unfairness or opacity* of the salary process. When salary was perceived as fairly administered and at or above market, it did not appear as a satisfaction driver; it was simply absent from the \"good feelings\" accounts.\n\n**Motivator gap (Step 4):** The most powerful single predictor of extreme positive feelings was *achievement* — a concrete sense of having accomplished something. The second was *recognition* specifically tied to achievement. What was largely absent from either list: salary increases, benefits improvements, or office upgrades on the positive side; lack of achievement or recognition on the negative side.\n\n**Enrichment prescription (Step 5):** Herzberg's prescriptive conclusion — developed at length in the 1968 HBR article — was that companies systematically over-invested in KITA (Kick In The Ass, his term for hygiene interventions: raises, perks, threats) and under-invested in job enrichment. The practical prescription: increase the vertical complexity of jobs by giving people genuine ownership of outcomes, removing supervisory controls while maintaining accountability, providing direct feedback from the work, and creating visible advancement paths.\n\n**Legacy (Step 6):** The *Motivation to Work* has been cited over 1.4 million times according to Google Scholar. H"},{"path":"examples/retaining-scarce-ai-ml-talent-2024-2026.md","content":"# Method in Action: Retaining Scarce AI/ML Talent in a Red-Hot Market (2024–2026)\n\n> *Example for the [herzberg-two-factor](../SKILL.md) skill.*\n\nBetween 2024 and 2026 the market for frontier AI/ML researchers and engineers became one of the most extreme talent markets in the history of the technology industry. Multiple large AI labs and hyperscalers publicly committed to unprecedented capital spending on AI infrastructure, and compensation for scarce senior AI talent reached widely reported levels far above typical software-engineering pay. Press reporting through late 2025 documented aggressive cross-lab poaching, headline-grabbing offers, and public statements from lab leaders about retention pressure. This is a textbook setting for the two-factor asymmetry: a market where *pay is table-stakes hygiene*, so throwing more money at retention often fails to move engagement — yet leaders keep reaching for it because it is the most legible lever.\n\nThe anchor case: a well-funded AI product company (Series B+, ~40 ML/research staff) sees its most valuable researchers being recruited away, and its instinct is to counter every offer with cash. This example runs that situation through the skill's Process.\n\n**Step 1 — Collect complaint/satisfaction inventory (specific behavioral events, not ratings).** Instead of an engagement survey, run stay interviews and code recent departures as critical incidents. Illustrative events the company surfaces: a departing researcher who left despite a matched counter-offer said the deciding factor was that a competitor let her own a research direction end-to-end rather than service a product roadmap; an engineer who stayed cited a specific week where he shipped a model improvement directly to production and saw the metric move; a complaint recurring in 1:1s is that model-launch decisions are made two layers up and researchers learn of them after the fact; another complaint is that GPU allocation and experiment approval require slow, opaque sign-off. These are events, not opinions.\n\n**Step 2 — Classify each item as hygiene or motivator.** Cash compensation and equity: hygiene (in this market, absence below the top-lab band drives active dissatisfaction, but matching it produces no durable engagement — the classic \"we matched the offer and they left anyway\"). Compute access being throttled by slow approval: hygiene (a *working-conditions* failure — the tooling of the job). Owning a research direction end-to-end: motivator (responsibility + the work itself). Shipping to production and seeing the metric move: motivator (achievement + direct feedback from the work). Being excluded from launch decisions: a motivator gap (responsibility withheld). The classification test from the skill applies: matched pay habituates within weeks; direction-ownership does not.\n\n**Step 3 — Assess hygiene baseline vs. market and set the floor.** In the 2024–2026 market the hygiene floor for scarce AI talent moved sharply upward, so the floor must"}],"languages":[],"docsSourceLabel":"CLAWHUB","editorialOverview":"Activate when: someone says 'why isn't the team motivated,' 'we raised salaries but morale didn't improve,' 'people keep leaving for better opportunities,' '... Skill: Herzberg Two-Factor Theory Owner: deciqai Summary: Activate when: someone says 'why isn't the team motivated,' 'we raised salaries but morale didn't improve,' 'people keep leaving for better opportunities,' '... Tags: latest:1.0.5 Version history: v1.0.5 | 2026-07-16T18:02:04.371Z | user Description tail link + agents machine-readable metadata line (deciqai.com/s/herzberg-two-factor.json) v1.0.4 | 2026-07-09T1","editorialQuality":{"score":100,"threshold":65,"status":"ready","wordCount":2152,"uniquenessScore":50,"reasons":[]}},"media":{"evidence":{"source":"no-media","verified":false,"confidence":"low","updatedAt":"2026-10-11T05:39:05.352Z","emptyReason":"No screenshots, media assets, or demo links are available."},"primaryImageUrl":null,"mediaAssetCount":0,"assets":[],"demoUrl":null},"ownerResources":{"evidence":{"source":"unclaimed","verified":false,"confidence":"low","updatedAt":"2026-10-11T05:39:05.352Z","emptyReason":"This page has not been claimed by the agent owner."},"hasCustomPage":false,"customPageUpdatedAt":null,"customLinks":[],"structuredLinks":{"docsUrl":null,"demoUrl":null,"supportUrl":null,"pricingUrl":null,"statusUrl":null},"customPage":null},"relatedAgents":{"evidence":{"source":"protocol-neighbors","verified":false,"confidence":"medium","updatedAt":"2026-10-11T07:41:14.236Z","emptyReason":null},"items":[{"id":"8ebccd8e-3863-4187-8355-c3f14e1f9edf","entityType":"agent","canonicalPath":"/agent/iofficeai-aionui","slug":"iofficeai-aionui","name":"AionUi","description":"Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!","url":"https://github.com/iOfficeAI/AionUi","homepage":"https://www.aionui.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-10-09T19:11:12.944Z","createdAt":"2026-02-25T03:38:16.584Z","downloads":null},{"id":"b917f68a-ebff-438e-84f8-3f4b2494c0bc","entityType":"agent","canonicalPath":"/agent/activepieces-activepieces","slug":"activepieces-activepieces","name":"activepieces","description":"AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents","url":"https://github.com/activepieces/activepieces","homepage":"https://www.activepieces.com","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-15T02:22:12.426Z","createdAt":"2026-02-25T03:38:12.412Z","downloads":null},{"id":"5cb26759-3a39-483f-94cf-276a98c13bb8","entityType":"agent","canonicalPath":"/agent/cherryhq-cherry-studio","slug":"cherryhq-cherry-studio","name":"cherry-studio","description":"AI productivity studio with smart chat, autonomous agents, and 300+ assistants. Unified access to frontier LLMs","url":"https://github.com/CherryHQ/cherry-studio","homepage":"https://cherry-ai.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-11T14:38:40.986Z","createdAt":"2026-02-25T03:38:19.379Z","downloads":null},{"id":"6f6582d0-5d76-4f0f-b81d-86520247950b","entityType":"agent","canonicalPath":"/agent/copilotkit-copilotkit","slug":"copilotkit-copilotkit","name":"CopilotKit","description":"The Frontend for Agents & Generative UI. React + Angular","url":"https://github.com/CopilotKit/CopilotKit","homepage":"https://docs.copilotkit.ai","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-03-25T09:50:57.846Z","createdAt":"2026-02-25T03:39:14.617Z","downloads":null}],"links":{"hub":"/agent","source":"/agent/source/clawhub","protocols":[{"label":"OpenClaw","href":"/agent/protocol/openclew"}]}}}